sz-chrome-remote-cdp.git/src/cdp/errors.ts, branch masterpi-browser-harness, patched to drive a Chrome on another host over CDP, with castle_cdp_search web search
https://git.soarez.net/sz/sz-chrome-remote-cdp.git/atom?h=master2026-08-02T13:42:46+00:00refactor: one CDP transport, not two2026-08-02T13:42:46+00:00amankumarsingh77amankumarsingh7702@gmail.com2026-07-28T16:20:38+00:00urn:sha1:893a9d338ceb5d37aefece1df637c9a5888a120e
createCdpTransport was a second full WebSocket-to-Chrome implementation
reachable only through client.ts's `?? createCdpTransport()` fallback,
which production never took — every session and every automated test
passes the daemon transport. transport.ts now holds only the CdpTransport
interface, and the client requires a transport instead of inventing one.
The "Session with given id not found" match that both transports carried
becomes classifyRemoteError in cdp/errors.ts, next to the error kind it
produces.
test/manual/profile-concurrency-test.ts was the sole caller of the
fallback: it drives its own Chrome on a private port. It now spawns a
daemon per scenario with BU_CDP_WS set, and refuses to run when a daemon
is already up, since that one is bound to a different browser.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
feat(cdp): add types and error model for new transport layer2026-05-02T10:10:27+00:00amankumarsingh77amankumarsingh7702@gmal.com2026-05-02T10:10:27+00:00urn:sha1:ede4b89e675aebecc226fdd9e095e3d096ddf15a