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 live G2 showed the composite provision lease fix removed the prior
REQUEST_EXPIREDfailure, but one fresh slot still reachedbootstrap acknowledgement timed out. Readback proved the managed conversation and authenticated peer probe were healthy while the bootstrap prompt never appeared in that conversation.The continuation path currently uses
chatgpt ask --wait false, which still performs ask-specific generation gating before message submission. OpenCLI already exposeschatgpt sendfor fire-and-forget delivery to an existing conversation. This change uses that narrower primitive, preserves the existing DevSpace idle gate, and requires exact prompt readback before reporting delivery. It does not add blind retries or relax unknown-outcome handling. The concrete transport blocker is also preserved in the durable unknown receipt instead of collapsing every failure toBOOTSTRAP_DELIVERY_UNKNOWN.Live follow-up will be rate-limited: one-worker canary first, then the formal three-worker gate only if the canary is clean.