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.
Fixes the next live Wave 3 blocker from Issue #117. On the exact deployed macOS/Chrome 152 managed carrier, the existing
execCommand('insertText')path left the complete draft text visible in the contenteditable DOM but never updated ChatGPT's real composer state, so no enabled send button appeared andruntime_ensure(3)correctly fenced the slot asRECONCILE_REQUIRED.A causal probe on that same stuck target showed that CDP
Input.dispatchKeyEvent+Input.insertTextimmediately produceddata-testid="send-button"withdisabled=falsewithout sending the message. This repair therefore keeps DOM evaluation for exact-URL/composer guards and the textarea fallback, but routes the contenteditable path through exact-target CDP Input commands. Send-button readiness is polled read-only, then the send click is attempted exactly once so acknowledgement loss cannot cause a blind resend.Candidate
f7900b1f5ca8c008e35422eff0775e60237e2ac0is based directly onmain@0890f77e1f061511b2a48d5cab6aec0b18f735a7and changes onlysrc/chat-swarm-runtime.tsandsrc/chat-swarm-runtime.test.ts. Local dependency-backed tests were not claimed because dependency sync was blocked by the current coordination-carrier gate;git diff --checkand static anti-false-green checks passed. Exact-head CI plus independent Candidate acceptance are required before merge.