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

.gitea/workflows/deploy.yml

@@ -37,9 +37,16 @@ jobs:
       AWS_DEFAULT_REGION: ${{ vars.AWS_REGION }}
       S3_BUCKET: ${{ vars.S3_BUCKET }}
       CLOUDFRONT_DISTRIBUTION_ID: ${{ vars.CLOUDFRONT_DISTRIBUTION_ID }}
-      # Job-level so the guard can see it. An empty INTAKE_ENDPOINT does not
-      # fail the build - it ships a live contact form posting to nothing.
-      INTAKE_ENDPOINT: ${{ vars.INTAKE_ENDPOINT }}
+      # NO INTAKE_ENDPOINT. Build step 8 moved the intake form to the
+      # same-origin path /api/intake, after which nothing in src/ read this
+      # value - `git grep PUBLIC_INTAKE_ENDPOINT -- src/` returned nothing - and
+      # the guard below was blocking a deploy on it. The comment that stood here
+      # said an empty value "ships a live contact form posting to nothing",
+      # which became false in both directions: the form posts to /api/intake
+      # regardless, and what decides whether it works is the CloudFront /api/*
+      # behaviour, which nothing guarded. See scripts/deploy-local.sh, which
+      # carries the post-deploy route check that replaced it.
+      # Found by `adversarial-reviewer`, 2026-08-31.
 
     steps:
       # Runs first, before checkout and before any AWS call, so a
@@ -66,7 +73,6 @@ jobs:
           [ -n "$AWS_DEFAULT_REGION" ]        || missing="$missing AWS_REGION(var)"
           [ -n "$S3_BUCKET" ]                 || missing="$missing S3_BUCKET(var)"
           [ -n "$CLOUDFRONT_DISTRIBUTION_ID" ] || missing="$missing CLOUDFRONT_DISTRIBUTION_ID(var)"
-          [ -n "$INTAKE_ENDPOINT" ]           || missing="$missing INTAKE_ENDPOINT(var)"
           [ -n "$AWS_ACCESS_KEY_ID" ]         || missing="$missing AWS_ACCESS_KEY_ID(secret)"
           [ -n "$AWS_SECRET_ACCESS_KEY" ]     || missing="$missing AWS_SECRET_ACCESS_KEY(secret)"
           if [ -n "$missing" ]; then
@@ -96,11 +102,11 @@ jobs:
       - name: Build
         run: npm run build
         env:
+          # PUBLIC_SITE_URL only, because it is the one variable
+          # astro.config.mjs reads. PUBLIC_INTAKE_ENDPOINT and
+          # PUBLIC_BOOKING_URL were set here and consumed by nothing;
+          # `CONTACT.bookingUrl` is null in source while R6 keeps booking parked.
           PUBLIC_SITE_URL: https://adr.smlcompany.ca
-          # vars, not env — Gitea expression-context support is the very thing
-          # the guard above exists to not depend on.
-          PUBLIC_INTAKE_ENDPOINT: ${{ vars.INTAKE_ENDPOINT }}
-          PUBLIC_BOOKING_URL: ${{ vars.BOOKING_URL }}
 
       # AGENTS.md §4 Forbidden, enforced on the built output before a single
       # byte is uploaded. Runs here rather than in `npm run check` because it