Decline chrome-devtools-mcp install — Permanent 8 ceiling holds
Decision
Do NOT install ChromeDevTools/chrome-devtools-mcp (Google, v0.26.0) as Permanent 9. Keep Permanent 8 unchanged.
Rationale
Three reasons. (1) Explicit prior rule: feedback_mcp_two_tier_model.md bans claude mcp add. User’s session ask was verification, not authorization. Auto-mode classifier correctly flagged the install attempt. (2) No authenticated-session gain: chrome-devtools-mcp uses fresh Puppeteer-controlled Chrome, cannot reuse AJ’s real session, so it does not augment Claude_in_Chrome for browsing. Its value is purely perf/debug. (3) Existing coverage sufficient: Lighthouse + Core Web Vitals + traces can be shelled out from quality-orchestrator Layer 6 and post-deploy-verification skills without permanent registration. Revisit only if a workflow hits a wall that ONLY a permanent CDP-MCP can solve.
Alternatives Rejected
A. Install as Permanent 9 — initially recommended in-session, then rolled back when classifier flagged the rule violation. Rejected: violates explicit ceiling rule; AJ asked for verification not installation. B. On-demand npx chrome-devtools-mcp from a skill — keeps Permanent 8 intact while still accessing Lighthouse/trace when needed. Tabled, not blocking. C. Status quo (chosen).
Outcome
Pending