B&J — Lighthouse status (v2): NOT measurable from production host; needs a desktop DevTools session

Why Lighthouse is not in this v2 ingest

Lighthouse cannot be run from the production host. chromium, chromium-browser, google-chrome, chrome, and lighthouse are all absent on CT 104, and CLAUDE.md explicitly forbids installing them. Verbatim:

"No screenshot pipelines. Visual verification is the human's job in a real browser. Don't install playwright, puppeteer, or chromium-for-testing."

Running Lighthouse requires either installing Chromium (forbidden) or running it from a workstation.

Action for the case study: run Lighthouse from a desktop browser DevTools session against https://bjweb.candidcreative.ca/ (and 1–2 representative deep pages: /agriculture, /resources/coloured-diesel-and-ontario-law). Capture Performance / Accessibility / Best Practices / SEO scores. This unblocks the v1 B&J — known unknowns that need a human conversation or a tool query before publication item #1.

What was structurally fixed in commit 3514d02 (2026-05-23 audit-closure)

Two specific Lighthouse failures flagged by a prior third-party audit are now resolved at the HTML/CSS level — a fresh Lighthouse run should reflect these:

• Color contrast. --color-text-tertiary lifted from #8a8884 → #6c6a66 (~5.1:1 contrast on --color-surface-page, clears WCAG 2.1 AA for normal text).
• Link name. Coverage-map polygon anchors now carry aria-label="<county> — service area page". Verified live: aria-label="Waterloo Region — service area page", aria-label="Wellington County — service area page", etc.

The other Lighthouse categories (Performance, Best Practices, SEO) have not been measured on this round. Once a DevTools Lighthouse run happens, update B&J KPI candidates — every defensible metric, with source and confidence and supersede the relevant v1 status lines.