Skip to content

feat(chat-swarm-runtime): rebind existing Chrome control to fresh main - #179

Merged
James3014 merged 1 commit into
mainfrom
issue-117-wave3-fresh-main
Sep 16, 2026
Merged

James3014 merged 1 commit into
mainfrom
issue-117-wave3-fresh-main

Conversation

@James3014

Copy link
Copy Markdown
Owner

Rebinds Issue #117 Wave 3 G1 source support onto the current main lineage instead of relying on the older diverged PR #177 branch.

The three Wave 3 files are byte-equivalent to the previously verified source: existing authenticated Chrome control remains explicit existing-session CDP, exact conversation identity stays separate from authenticated peer authority, recovery remains exact-target only, and unknown prompt outcomes never grant blind resend or fallback authority. The Linux portability boundary keeps the physical DevToolsActivePort tests macOS-only without changing their Darwin assertions.

Fresh-main verification on parent 0678354da8ea8f48e6b70b81ad6407c3da04ed72: affected Chat Swarm suites 139/139 PASS, npm run typecheck PASS, npm run build PASS, and git diff --check PASS. Candidate is add678e63311cdcb56e2c04681466ea49269247b; only docs/chat-swarm-runtime-macos.md, src/chat-swarm-runtime.test.ts, and src/chat-swarm-runtime.ts differ.

This PR is still source-level G1 evidence only. Native G0 and G2-G6 on the exact installed macOS build remain separate closure gates for #117.

@James3014
James3014 merged commit c6c3d50 into main Sep 16, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant