fix(chat-swarm-runtime): drive ChatGPT composer through CDP Input - #185
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 3 live acceptance proved that DOM/execCommand editing can leave ChatGPT's visible contenteditable text populated without updating the internal composer state, so the Send control never becomes enabled. On the same Chrome 152 target, exact-target CDP
Input.dispatchKeyEvent+Input.insertTextproduced the enabled Send control without sending.This keeps the existing browser/carrier, conversation identity guards, textarea fallback, peer authority, and no-blind-resend semantics. Only contenteditable input moves to the CDP Input domain; the final send remains one guarded click. The Candidate is based directly on
main@0890f77e1f061511b2a48d5cab6aec0b18f735a7and changes only the runtime plus its regression tests. It also corrects two hostile-test assertions that still referenced the supersededconst prompt=implementation detail.git diff --checkpasses locally. The isolated managed worktree cannot runnpm cibecause the current MCP session has no paired coordination carrier, so local dependency-based tests were not substituted or bypassed; exact-head Ubuntu/macOS CI must provide Test/Typecheck/Build evidence before merge.