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.
Formal #117 G2 evidence showed slot 1 park successfully, then slot 2 hit the 60-second OpenCLI command deadline; the fail-fast guard correctly prevented slot 3 from being created. The current provision operation has a longer lifecycle lease, but the exact ChatGPT conversation handle was only persisted after the peer-identity probe finished, so a late probe failure could leave an unknown operation without the carrier handle needed for deterministic reconciliation.
This change persists the exact transport conversation URL/fingerprint as soon as OpenCLI returns it, before waiting for peer identity, while keeping authenticated peer identity as the bootstrap authority. The intermediate transport-observed phase is now durable: if execution restarts before peer identity is verified, replay fails closed into reconciliation instead of provisioning again or advancing to bootstrap. It also adds an 8-second stagger between new external carrier creations in one ensure; healthy/replayed slots are not delayed. The stagger matches the proven multi-worker bootstrap pattern in devspace-ultra and reduces burst pressure without adding retry authority.
Dual-identity admission and no-blind-retry semantics are unchanged. Local dependency sync was blocked by the current paired-carrier safety gate, so integration requires exact-head CI plus independent review. Candidate: 3057f1d.