Verify the packed real-Chrome extension-to-MCP composition

[dvcolomban]

Parent

Deliver Chrome Debugger Bridge from authorized MVP to public release

What to build

Prove one complete adoption path from a packed MV3 agent in real Chrome through application-owned authenticated bridge endpoints and the reconnecting Node client facade to CDB tools registered on an application-owned MCP server.

An official MCP client must discover and use one explicitly selected opaque target without relying on repository source aliases or giving MCP ownership of Chrome, the broker, or host lifecycle.

Acceptance criteria

• The verification installs only packed public packages in an isolated consumer workspace with no workspace aliases or source-layout imports.
• Real Chrome 125 or later loads the packed MV3 agent, completes pairing and agent hello, and publishes one explicitly selected tab under an opaque target identity.
• An application-owned host owns the authenticated agent and client endpoints, the Node client facade, and an MCP server that also contains at least one non-CDB tool.
• An official MCP client discovers the combined tool surface, lists the opaque target, and completes one lease-authorized safe inspection through CDB.
• Removing the tab from the selected scope revokes the target and causes subsequent stale MCP access to fail with the stable public error behavior.
• The flow proves deterministic shutdown of the extension connection, Node facade, MCP registration or transport, bridge endpoints, broker, iterators, and pending operations.
• Retained traces and diagnostics contain no credentials, page content, raw Chrome identifiers, or artifact bytes.
• The test is suitable for the supported real-Chrome CI job and retains actionable redacted failure artifacts.
• Lint, type checks, affected unit and browser suites, real-Chrome end-to-end tests, build, and packed-package verification pass.

Blocked by

• Preserve broker frames while storing a newly paired credential
• Keep an idle MV3 agent connected with the negotiated heartbeat
• Provide the complete reconnecting CDB client facade for Node
• Register CDB tools in an application-owned MCP server