lighthouse

# Lighthouse Optimization Loop Set a product-neutral scratch root once: ```bash LIGHTHOUSE_DIR="${TMPDIR:-/tmp}/cc-settings-lighthouse" mkdir -p "$LIGHTHOUSE_DIR" ``` Use the Chrome DevTools MCP only when the user configured it. Standalone Codex otherwise uses the Lighthouse CLI plus native/manual screenshots; if no visual capture path exists, stop before changing UI and report that visual regression verification is unavailable. This package does not auto-run unpinned registry MCP packages. **Method:** 3 mobile + 3 desktop runs per audit, averaged for reliability. After each code change, re-audit and visually verify the page with the configured MCP or the stated manual fallback. --- ## Setup 1. **Parse URL** from `$ARGUMENTS`. If no URL, ask the user. Default: `http://localhost:3000` 2. **Verify prerequisites:** ```bash lighthouse --version # CLI must be installed for the batched 3x3 protocol ``` If lighthouse is missing: `npm install -g lighthouse` If runs fail with a chrome-launcher error or every metric comes back `NO_LCP`/null, no system Chrome exists — find a real Chrome/Chromium binary (Chrome for Testing, Playwright's `chromium-*` — NOT `chrome-headless-shell`, which produces NO_LCP) and export `CHROME_PATH=<binary>` before the loop. Record which binary was used; a before/after comparison is only clean when both sides ran the same binary. Check whether the user configured the chrome-devtools MCP. Do not install or auto-run...