titan-chromedevtoolslisted

# Titan: chromedevtools ## Mandate Embed Chrome DevTools Protocol (CDP) into Claws as a native MCP surface. Workers and the orchestrator gain a `claws_browser_*` tool family: `attach`, `navigate`, `evaluate`, `snapshot`, `network_inspect`, `performance_profile`, `console_collect`, `screenshot`, `detach`. Reference repo: https://github.com/ChromeDevTools/chrome-devtools-mcp — WebFetch this in AUDIT phase before authoring. ## Deliverables | Artifact | Path | Owner | |---|---|---| | Codegen schema entries | `schemas/mcp-tools.json` (via `scripts/gen-mcp-tools.mjs`) | sub-worker | | MCP server dispatch arms | `mcp_server.js` (NEW `claws_browser_*` cases) | sub-worker — SERIALIZED, single owner per FILE-OWNERSHIP | | CDP client module | `lib/cdp/client.js` (NEW) | sub-worker | | Skill family | `.claude/packs/cu-patterns/browser-*.md` (NEW: attach, navigate, evaluate, snapshot) | sub-worker | | Smoke tests | `extension/test/cdp-smoke.test.js` (NEW) | sub-worker | | Tri-platform notes | `docs/cdp-tri-platform.md` (NEW) | sub-worker | | READY-REPORT | `.local/blueprints/v083-titan-chromedevtools/READY-REPORT.md` | titan-LEAD | | Staging changelog | `CHANGELOG_TITAN_CHROMEDEVTOOLS.md` | titan-LEAD | ## Bus topics | Topic | Direction | Purpose | |---|---|---| | `system.titan.chromedevtools.audit.start` / `.complete` | emit | Phase milestone | | `system.titan.chromedevtools.synthesis.complete` | emit | Wave plan ready | | `system.titan.chromedevtools.polish.complete` | emit | Code