feat(jared): Trace workspace lifecycle - #185
Draft
MathurAditya724 wants to merge 2 commits into
Draft
MathurAditya724 wants to merge 2 commits into
MathurAditya724 wants to merge 2 commits into
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
jared | f49bbbd | Sep 18 2026, 08:42 AM |
MathurAditya724
force-pushed
the
codex/feat-workspace-lifecycle-tracing
branch
from
September 18, 2026 08:37
ea8f13f to
b86a1df
Compare
MathurAditya724
force-pushed
the
codex/feat-workspace-lifecycle-tracing
branch
from
September 18, 2026 08:42
b86a1df to
f49bbbd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a compact workspace lifecycle record to Cloudflare logs and the existing Sentry preparation span. Each record joins on the Flue submission ID and reports only transition, phase, checkpoint availability, and recovery count.
This is stacked on #184 because it uses the same workspace-health model. It intentionally does not alter retry policy or replay behavior; it makes the existing safety decisions observable.