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

src/components/Button.astro

@@ -66,18 +66,47 @@ const classes = ['btn', `btn-${variant}`, className];
     color: var(--text-inverse);
   }
 
+  /* ⚠️ THE THREE HOOKS BELOW EXIST BECAUSE THIS BUTTON SHIPPED INVISIBLE.
+     Found 2026-08-31 by `adversarial-reviewer` on `/fees/`, measured in headless
+     Chrome against `dist/`: `{"t":"How an engagement runs →","color":"rgb(26, 22,
+     20)","bg":"rgb(26, 22, 20)","ratio":1}`. `.btn-ghost` sets `color:
+     var(--text)` — ink — and a border of `--border`, which is ink at 10% alpha.
+     On a `.section-inverse` ground both are the background colour. **Ratio
+     1.00:1: a navigation link the same colour as the panel it sits on**, worse
+     than the gold-on-cream 2.10:1 this project treats as unshippable.
+
+     ⚠️ AND LIGHTHOUSE SCORED THAT PAGE ACCESSIBILITY 100. axe's
+     `color-contrast` rule SKIPS a foreground that exactly equals its background
+     as "unable to determine" — so the a11y category cannot be the only contrast
+     control here, and a computed-contrast sweep is not redundant with it.
+
+     THE HOOKS ARE CUSTOM PROPERTIES, NOT A GLOBAL DESCENDANT RULE, and that is
+     the load-bearing part. A parent cannot style a child component's root
+     (CLAUDE.md), and `global.css`'s `.section-inverse .btn-ghost` would compile
+     at specificity (0,2,0) — identical to `.btn-ghost[data-astro-cid]` here — so
+     which one won would depend on injection order. `AGENTS.md` records that
+     exact trap being hit once already, on `.btn-gold`. Custom properties
+     INHERIT, which is the one mechanism that legitimately crosses the boundary;
+     it is what `Pill` and `DefinitionGrid` already use. The fallbacks keep the
+     on-cream appearance byte-identical. */
   .btn-ghost {
     background: transparent;
-    border-color: var(--border);
-    color: var(--text);
+    border-color: var(--btn-ghost-border, var(--border));
+    color: var(--btn-ghost-fg, var(--text));
   }
   .btn-ghost:hover {
-    border-color: var(--accent);
-    color: var(--accent);
+    border-color: var(--btn-ghost-border-hover, var(--accent));
+    color: var(--btn-ghost-fg-hover, var(--accent));
   }
 
+  /* `background: var(--bg-inverse)` is ink, so on an inverse ground the pill has
+     no boundary and reads as bare text — the milder half of the same finding.
+     The label is gold-l at 11.09:1 on ink and stays legible, so this needs an
+     EDGE rather than a new colour scheme: giving it a different ground would be
+     redesigning a button shipped at step 5 rather than fixing a defect. */
   .btn-gold {
     background: var(--bg-inverse);
+    border-color: var(--btn-gold-border, transparent);
     color: var(--text-inverse-2);
   }
   .btn-gold:hover {