Skip to content

Move the old chrome.debugger branching into separate class from new main loopback_cdp logic#6

Closed
pirate wants to merge 29 commits into
mainfrom
server-upstream-transport
Closed

Move the old chrome.debugger branching into separate class from new main loopback_cdp logic#6
pirate wants to merge 29 commits into
mainfrom
server-upstream-transport

Conversation

@pirate
Copy link
Copy Markdown
Member

@pirate pirate commented May 22, 2026

Summary

  • Add ServerUpstreamTransport with loopback CDP and chrome.debugger implementations behind one active server upstream interface.
  • Add Mod.getTopology and extend AutoSessionRouter with target/session/context bookkeeping, frame topology, document roots, and pierced shadow root discovery.
  • Add live Vitests for sdk -> ws -> service_worker -> loopback_cdp and sdk -> ws -> service_worker -> chrome_debugger routing.

Validation

  • pnpm run typecheck
  • pnpm exec vitest run js/test/test.AutoSessionRouter.ts js/test/test.ServerUpstreamTransport.ts --fileParallelism=false --maxWorkers=1

@pirate pirate changed the title Add server upstream topology routing Move the old chrome.debugger branching into separate class from new main loopback_cdp logic May 22, 2026
@pirate pirate marked this pull request as ready for review May 22, 2026 00:25
@pirate
Copy link
Copy Markdown
Member Author

pirate commented May 26, 2026

Superseded by #7 and #8. #7 contains the ServerUpstreamTransport / chrome.debugger split and related transport cleanup; #8 stacks on #7 with Mod.getTopology and the advanced AutoSessionRouter topology/session/context work. I verified the final stacked tree matches this PR head exactly.

@pirate pirate closed this May 26, 2026
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