chrome-devtools-mcp installed as Permanent 9 (stdio, npx chrome-devtools-mcp@latest, headless on /us

What

chrome-devtools-mcp installed as Permanent 9 (stdio, npx chrome-devtools-mcp@latest, headless on /usr/bin/google-chrome, telemetry off). New tools mcp__chrome-devtools__* — lighthouse_audit, performance_start_trace, performance_analyze_insight, list_network_requests, take_memory_snapshot, get_memory_snapshot_details, emulate (CPU/network/device), screencast_start/stop, take_screenshot, evaluate_script. Both ~/.claude.json and /root/.claude.json updated. Codex parity ~/.codex/config.toml wired same-session. Stitched into 4 perf skills as PRIMARY engine with AUTH GUARD warning for gated URLs. Closes Layer 6/7 perf-gate gap. Lighthouse-on-demand + CrUX field data + memory profiling + source-mapped stacks now available without shelling to Lighthouse CLI. Tools callable from next session start (config-load is session-start, not mid-session).

Why

Action Required

Update routing knowledge — Layer 6 quality-orchestrator and Layer 7 delivery-orchestrator should auto-route perf/Lighthouse work to chrome-devtools MCP for public URLs. Gated URLs route to Claude_in_Chrome or Playwright with storageState. 6-month review checkpoint 2026-11-16 in evolution-backlog.md.