Launch installed Chrome through a nonzero CDP port

[rishabhraj36]

Summary

• route only the configured chrome runtime through a Webcmd-owned launcher
• allocate an explicit nonzero CDP port bound to loopback and attach with Playwright over CDP
• preserve Cloak, SLAB, and custom executable launch paths
• add exact process/profile/port ownership checks, cleanup, and locked-profile recovery
• document the behavior without claiming general undetectability

Verification

• npm test -- src/browser/runtime/local-cloak/chrome-process.test.ts src/browser/runtime/local-cloak/chrome-launch.test.ts src/browser/runtime/local-cloak/session-manager.test.ts src/browser/runtime/configured-provider.test.ts src/browser/runtime/local-cloak/provider.test.ts — 130 passed
• npm run typecheck — passed
• npm run build — passed
• WEBCMD_LIVE_CHROME=1 npx vitest run --project e2e tests/e2e/chrome-webdriver.test.ts — passed on macOS with native navigator.webdriver === false
• full unit suite after build — 3,408 passed; five unchanged src/fetch/safe-proxy.test.ts failures under Node v26.7.0

Platform note

The production path was live-tested on macOS. Linux and Windows ownership paths have unit/code coverage but still need live release-gate execution on those hosts.

[github-actions]

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

This review is advisory and does not block merging.