fix(coding-agent): prove delayed print continuation - #17
Merged
rikonor merged 1 commit intoJul 18, 2026
Merged
Conversation
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
2 participants
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.
Finding
The delayed faux-provider test reaches the race window on the base commit, but its first failing assertion is
ctx.isIdle() === false. Vitest therefore never reaches the assertions that the extension user turn and second assistant response survived print/JSON disposal.Fix
Assert the completed continuation before the supporting idle-state assertion. Against exact base
f6b7dad2bc787bc8e885128986b4c18b8e8da154, both cases then fail first with only the initial user turn present. At PR head, both pass.Validation
npm run check: passedTargets #15 branch at
4675817ff4c5f4376a20c67668cd75d778111e26.This PR was created by an AI coding agent.