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/pages/about.astro

@@ -588,8 +588,48 @@ const CREDENTIAL_GROUPS = [
     </div>
   </section>
 
+  {/* ---- 3b. The one-page PDF ------------------------------------------- */}
+  {
+    /* ✅ **R16 / Q45 DISCHARGED — build step 9.** `docs/01` §`/about/` item 7 has
+      carried a pending note since step 3: the PDF did not exist, and a link to a
+      file that does not exist is a broken link on the page an appointing body
+      reads. It exists now, it is committed, and this is the link.
+      **`/bio/` is the source and the PDF is a rendering of it** — so every line
+      of the document circulated with an appointment proposal is on a page that
+      `check:claims`, the adversarial review and the cutover claims pass all see.
+      That was R16's actual objection: *"a PDF circulated with an appointment
+      proposal is read once, by the reader who matters most, and never seen by a
+      reviewer again."*
+      It carries NOTHING the site does not — R16's second open sub-decision, and
+      the answer that avoids the §4 question it flagged. No matter list, no
+      referees, no figure that is not on `/fees/`. */
+  }
+  <section class="section bio-download reveal">
+    <div class="wrap">
+      <p class="download-line">
+        <a href="/pouya-lajevardi-bio.pdf" download>
+          Download a one-page PDF of this record
+        </a>
+        <span class="download-note">
+          — designations, education, memberships, the processes offered and the
+          rates, on one sheet. The same page is at <a href="/bio/">/bio/</a>.
+        </span>
+      </p>
+    </div>
+  </section>
+
   {/* ---- 3. Credentials, structured ------------------------------------ */}
-  <section class="section section-alt creds reveal">
+  {
+    /* ⚠️ `section-inverse`, NOT `section-alt` — approved by Pouya at build step
+      6 and applied at step 7b. The arc section struck on 2026-08-29 was this
+      page's only dark band, so removing it left `/about/` with four cream
+      sections and the accent contact band, and the alternating rhythm
+      `docs/02` sets went with it.
+      Exactly ONE rule had to change — `.cred-title`. The measured ratios are on
+      that rule below, which is where a future editor changing a colour will be
+      looking. Everything else inherits cream from `.section-inverse`. */
+  }
+  <section class="section section-inverse creds reveal">
     <div class="wrap">
       <div class="section-head">
         <SectionHeading eyebrow="Credentials" level={2}>
@@ -835,6 +875,24 @@ const CREDENTIAL_GROUPS = [
      page. "Provincial Offences Act" is set in roman. If a statute name ever
      needs italics here, load a face for it first. */
 
+  /* --- 3b. The one-page PDF ------------------------------------------- */
+
+  /* A quiet band between the bio and the credentials, not a call to action: the
+     reader an appointing body sends here is looking for the record, and a
+     download button styled like the contact CTA would compete with it. */
+  .bio-download {
+    padding-block: var(--space-7);
+    border-block: 1px solid var(--border);
+  }
+  .download-line {
+    max-inline-size: var(--width-prose);
+    font-size: var(--text-base);
+    line-height: var(--leading-body);
+  }
+  .download-note {
+    color: var(--text-secondary);
+  }
+
   /* --- 3. Credentials -------------------------------------------------- */
 
   .cred-grid {
@@ -860,7 +918,15 @@ const CREDENTIAL_GROUPS = [
     font-size: var(--text-base);
     font-weight: var(--weight-medium);
     letter-spacing: var(--tracking-tight);
-    color: var(--text-secondary);
+    /* THE ONE COLOUR THAT HAD TO MOVE WITH THE BAND. This was
+       `--text-secondary`, which is `--ink-soft` — **1.43:1** on the ink ground
+       this section now has, i.e. worse than the gold-on-cream 2.10:1 this
+       project treats as the defect that must never ship. `--text-inverse-2` is
+       gold-l: 11.09:1 on ink (docs/02). The list items below inherit cream from
+       `.section-inverse` at 16.81:1 and are untouched.
+       The gold border is a 1px divider, which tokens.css sanctions gold for on
+       any ground, and gold on ink measures 8.00:1 regardless. */
+    color: var(--text-inverse-2);
     padding-block-end: var(--space-3);
     border-block-end: 1px solid var(--rule);
   }