feat: build steps 7a-10 — the site is complete and reviewable at 22 pages

Steps 7a through 10 as one authorised run. Nothing deployed (D11).

7a  Lighthouse returns as `lighthouse@13.4.1` + `chrome-launcher`, NOT
    `@lhci/cli`. AGENTS.md §7's advisory attribution was wrong: the carriers
    were @lhci/cli's own `tmp` and @puppeteer/browsers' `extract-zip`, not
    Lighthouse, which audits clean. A deliberate deviation from R11's literal
    trigger, recorded with what it costs. Local gate; CI has no Chrome.

7b  OG card generator (satori + sharp) discharges R15 — 20 typed cards plus
    per-article cards; the portrait stays on / and /about/ by Q40. Insights
    plumbing: ArticleCard, Prose, the index, the article route, articleGraph,
    and /'s section 7. Card copy is constrained structurally because text in a
    JPEG cannot be grepped by check:claims: every headline IS its page's <h1>,
    enforced by `npm run og:proof`.

7c  Five drafted launch articles, draft: true / reviewedByPouya: false. An
    independent compliance audit returned 76 findings and 57 unsourced
    assertions; all blocking and should-fix applied.

8   /contact/, the intake form, and backend/intake/ (undeployed). Plain HTML
    POST to a same-origin /api/intake with a 303 redirect, so the form works
    with zero JavaScript. docs/05 records three deliberate deviations.

9   /fees/ on Q59's ruling — overtime runs from the session cap, and the
    reservation point ships adjacent to the rate. One-page PDF bio discharges
    R16; /bio/ is its source, so the circulated artefact stays inside the
    review apparatus.

10  /legal/privacy/ and /legal/terms/, written to the backend as built. Three
    of the policy's statements are derived and cannot drift.

Also: /about/'s inverse credentials band (approved at step 6); Q59 closed;
R15 and R16 discharged; and a fix to shipped copy — /practice/energy/ asserted
the absence of a regulation the source extract says must not be asserted.

Review: adversarial-reviewer, two rounds (D20/D19). Round 1 returned 16
findings including two blocking — an invisible ghost button on /fees/ at
1.00:1 that Lighthouse scored 100, and a privacy policy that named one data
processor when there are two. All 16 acted on.

Lighthouse, 22 pages, mobile: performance 99-100, accessibility 100,
best practices 100, SEO 100 on every indexable page, CLS 0.000.

AGENTS.md entry (ah) has the detail, including four of my own verification
commands that were wrong and what each of them nearly caused.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5

CLAUDE.md

@@ -136,11 +136,32 @@ npm run build      # static build to ./dist
 npm run preview    # serve ./dist locally
 npm run check      # astro check — type and template errors
 npm run check:claims  # §4 Forbidden, enforced on dist/ — run it after a build
+npm run check:intake  # the form's field table vs the Lambda's — they are two on purpose
+npm run og:proof   # every og:image resolves; every card headline IS its page's <h1>
+npm run lighthouse # the performance budget. LOCAL ONLY — needs Chrome, not in CI
+npm run bio:pdf    # re-renders the committed one-page PDF from /bio/. LOCAL ONLY
 npm run lint       # eslint + prettier check
 npm run format     # prettier — rewrite files in place
 npm run deploy     # build + deploy from this machine (see docs/06)
 ```
 
+**Four of those are gates and two of them cannot run in CI.** `check`,
+`check:claims`, `check:intake` and `og:proof` are pure Node and run anywhere.
+`lighthouse` and `bio:pdf` drive an installed browser, and the Gitea runner has
+none — so they are keyboard gates plus blocking items on `docs/06`'s cutover
+checklist, and **they are deliberately not wired into `npm run build` or either
+deploy path.** Do not describe either as gating a deploy: a check described as
+running where it cannot is the defect `AGENTS.md` Q22 turned out to be.
+
+**`og:proof` and `check:intake` exist because two facts in this repo are
+deliberately duplicated**, and a duplicated fact needs a mechanism rather than a
+comment. `og:proof` compares each generated OG card's headline against its page's
+own `<h1>` — **text baked into a JPEG cannot be grepped by `check:claims`**, so
+that comparison is the only thing keeping card copy inside the claim register.
+`check:intake` compares the form's field table against the Lambda's, which are
+independent because a server that validates against a list the client shipped it
+is not validating.
+
 ## Where things live
 
 ```
@@ -456,13 +477,30 @@ actually been provisioned is `AGENTS.md` Q22. It must never reach the repo.
 every page. Under 100 KB of JS on any route. LCP under 2.0 s on a simulated
 Slow 4G connection. Treat a budget breach as a failing build.
 
-**Lighthouse cannot currently be run.** `@lhci/cli` was removed on 2026-08-26
-(it carried 7 high-severity advisories, `0.15.1` is `latest`, and it had no
-pages and no `lighthouserc` to work with). The budget stands; the instrument is
-missing. It is re-added at build step 7 under `AGENTS.md` R11 — with a freshly
-verified pin, not on the assumption that `0.15.1` is still the ceiling. **Say
-"not run — tool unavailable" rather than silently omitting it.** A documented
-control that no longer exists is precisely the defect Q22 turned out to be.
+**Lighthouse runs again as of 2026-08-31 — `npm run lighthouse`, and it is
+`lighthouse` rather than `@lhci/cli`.** It enumerates every `index.html` in
+`dist/`, so the page set cannot go stale; it asserts the four category scores and
+**reports** LCP and CLS without asserting them, because simulated throttling on a
+loopback server is not the Slow 4G field measurement `docs/04` describes.
+
+**It is a LOCAL gate, not a CI check.** Standalone Lighthouse drives an installed
+browser and the Gitea runner has none. So it is `npm run lighthouse` at a
+keyboard plus a blocking item on `docs/06`'s cutover checklist, and it is
+deliberately not wired into `npm run build` or either deploy path. Do not
+describe it as gating a deploy.
+
+**Two things about the numbers, and both have to travel with them.** The
+accessibility category is measured with `prefers-reduced-motion` **forced** —
+otherwise axe's `color-contrast` audit reads the scroll-driven reveal's
+mid-animation opacity and reports 24 false nodes (measured; `#d0cbc4` on
+`#f8f4ed`, neither of which is in this palette). And the reason it is
+`lighthouse` and not `@lhci/cli` is that `AGENTS.md` §7's advisory attribution
+was **wrong**: the carriers were `@lhci/cli`'s own `tmp` and `@puppeteer/browsers`'
+`extract-zip`, not Lighthouse, and `lighthouse@13.4.1` audits clean. The budget
+was unmeasurable for five days on a cause nobody re-derived — which is the same
+lesson from the other side: **a documented control that no longer exists is
+precisely the defect Q22 turned out to be**, and so is one recorded as impossible
+on a reason that was never re-tested.
 
 ## What "done" means for a page
 
@@ -470,7 +508,7 @@ control that no longer exists is precisely the defect Q22 turned out to be.
 - [ ] No `TODO(pouya)` left unlogged in §9
 - [ ] Unique title, meta description, canonical, OG/Twitter tags, JSON-LD
 - [ ] Semantic HTML; keyboard navigable; reduced-motion honoured
-- [ ] Lighthouse ≥ 95 mobile, all four categories — **UNAVAILABLE until step 7**
-      (see the performance budget above). Report it as not run; do not tick it
+- [ ] Lighthouse ≥ 95 mobile, all four categories — `npm run lighthouse` after
+      `npm run build`. Read the exit status, not the table
 - [ ] Renders correctly with JavaScript disabled
 - [ ] `AGENTS.md` Change Log entry appended