fix(server): make bootstrap turn starts idempotent - #240
Merged
Conversation
- Join retries to an in-flight bootstrap run instead of creating duplicate threads - Preserve bootstrap results after dropped WebSocket connections and replay command receipts - Update orchestration test doubles for command receipt lookups
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
badcuban
enabled auto-merge
September 6, 2026 07:32
github-actions
Bot
added
vouch:trusted
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.
What Changed
Bootstrap turn starts are now idempotent under their command ID. Retries join an in-flight bootstrap run, while later retries use the stored command receipt instead of creating the thread and worktree again.
Why
A dropped WebSocket or slow response could cause the client to retry after part of the bootstrap had already completed, leading to duplicate work or a failed
thread.create. A server-wide in-flight run registry and receipt lookup make retries return the original result safely.Checklist