fix(website): pin the stage hold one millisecond inside it so the frame reports pause - #1034
Merged
Conversation
…me reports pause Verified against production after #1032 deployed: the frame went ready, applied exactly through the interrupt (stream:930), but reported phase `stream` at the hold because the website pinned t at hold.startMs and the frame's phaseReachedAt treats a boundary instant as the outgoing run's. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
blove
enabled auto-merge (squash)
September 6, 2026 05:43
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
…seam is continuous Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
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.
Verified against production after #1032 deployed: the frame went ready,
applied exactly through the interrupt (stream:930), but reported phase
streamat the hold because the website pinned t at hold.startMs and theframe's phaseReachedAt treats a boundary instant as the outgoing run's.
Follow-up to #1032 from the first live-frame run against production (
STAGE_LIVE_FRAME=true): two of three verify-state assertions passed; the hold one reportedstreamfor the reason above.🤖 Generated with Claude Code