fix(chat-swarm-runtime): wait for bootstrap-ready turn - #186
Merged
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
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.
Issue #117 Wave 4 G2 exposed a provisioning handoff race on the exact deployed macOS managed-CDP carrier. The first managed conversation was created and durably bound to an exact conversation URL, but the runtime immediately sent the
@devbootstrap turn without first proving the initialization turn had completed; the slot then timed out withPEER_IDENTITY_UNRESOLVEDand the exact target was no longer present for reconciliation.This Candidate keeps the existing managed Chrome carrier, durable conversation/peer identity split, admission rules, and no-blind-retry semantics. It adds one bounded quiescence gate: after the initialization turn creates the exact conversation identity, provisioning waits until that same exact conversation is no longer generating, still has a composer, and has an assistant
READY_FOR_BOOTSTRAPresponse before returning the identity to the bootstrap phase. Regression coverage fixes the required provision→idle→bootstrap ordering and the exact assistant-selector oracle.Current exact head is
cac3e0c1abd9f7889cc85c33630631206b30d7d0. Its production change remains the Wave 4 quiescence delta frommain@30379ad27c491ee1a93fbed9643fcf5b87809015; the final recovery commit changes onlysrc/chat-swarm-runtime.test.tsafter the prior local commit attempt was physically proven to have produced no commit or push. The PR as a whole changes onlysrc/chat-swarm-runtime.tsandsrc/chat-swarm-runtime.test.ts.git diff --checkpasses locally. Frozen local dependency sync is currently blocked by the paired-carrier prerequisite, so exact-head GitHub CI is the mandatory dependency-backed verifier before merge.