feat: build step 2 — the home page; close Q35, Q37, Q39; Q39's answer corrected the register

Pouya's rulings and the page are one commit, not two, because they are not
separable: Q37 changed the credential label the page renders, Q39 scoped the
arbitration copy, and Q35 gave Med-Arb the row that lets the footer link stand.
Splitting them would produce a commit where the register says one thing and the
page says another.

RULINGS

Q39 — ANSWERED, and my assertion was FALSE as a universal. Pouya checked
rather than defended. Family arbitration in Ontario is gated: prescribed
training, 14h on screening for domestic violence and power imbalances, 30h of
Ontario family law for arbitrators outside the bar, 10h ongoing per two years.
claims-auditor produced that counter-example from inside the repo on 2026-08-26
and it was right. The source is now IN the repo per R14 —
docs/reference/ontario-family-arbitration-training.md, retrieved with its
provenance — and §4 states which half it establishes: the family gate directly,
the commercial half only by absence. So "commercial arbitration in Ontario
requires no licence and no designation" is recorded as Pouya's stated position,
unstamped. What disposes of the question is the scope exclusion: he does not do
family arbitration, so it is NOT OFFERED and the gate never bears on the
practice.

The false universal survived in three more live places, found by grep, not
recall: §4's NOT-NEGOTIABLE boundary bullet (the boundary paragraph breaching
its own boundary), §9's Q33 closure row, and a comment in SiteHeader.astro.

Q35 — ANSWERED, all four items, and the answer supplied a gate that was
missing. Med-Arb gets an Offerings row and stays in the footer sitemap. The six
subject-matter labels pass test 1. §4 gains "Subject-matter areas — the
publication gate": competence to accept an appointment, AND a page that frames
it as positioning without claiming history. Nothing in the nav or footer is
unrowed any more.

Q37 — ANSWERED. "Law and engineering" becomes "Legal training and engineering
practice". A degree is not a practice; the parallel was doing the implying.

Q38/R13 — the committed SVG does not close it; the walk-back went too far. It
renders faithfully BECAUSE it is the raster. R13 stays open.

R1 — surfaced and acknowledged; the interim licensure framing is now carried by
a shipped page rather than a spec, which raises the stakes.

BUILD STEP 2

Seven of docs/01's eight home sections, six new components, zero JavaScript.
Section 7 (Latest insights) ships at step 7 with the collection it lists —
recorded in docs/01 and in the page, not just here. Four credential slots, not
three: §4's paired-disclosure condition requires the Q.Arb stage on any page
that offers arbitration. No booking link (R6). The masthead tagline is
suppressed on / (it duplicated the hero eyebrow). The step-1 proof sheet is
deleted, and five live references to it were found by grep.

WHAT THE REVIEWS FOUND — 24 findings across the two passes

claims-auditor FAILED it on ten, every one implication or scope rather than
fabrication, which is where D13 says the risk lives. The four that mattered:
"I mediate and arbitrate" asserted a track record §4 does not hold for
arbitration; the JSON-LD asserted arbitration twice and stated the stage
nowhere (a crawler-only claim is still a claim); "at one published rate with
preparation time included" misdescribed money against docs/07's two day rates
and capped prep allowance; and "Law and engineering are not blended here" was
Q37's struck parallel relocated into prose one day after Pouya struck it.
It also found the Canadian Tax Foundation missing from §9 Q8 — a stale second
copy of a fact that would have bitten at step 3.

adversarial-reviewer found fourteen, three blocking. The first was
class="section-head" on <SectionHeading> never matching — the parent-cannot-
style-a-child defect for the FOURTH time, written into a diff where I had just
added fresh warnings about it to two other components. Measured: 0px margin,
0px gap, headings over the card edges, with astro check and eslint both clean.
I had looked at a screenshot of that section and passed over it. Fixed with a
page-owned wrapper (48px, measured) and the prop is deleted from six components
so it is now a build error. Also: the credential row was never "two up on a
phone" and its comment said it was; PROCESS was hardcoded in the page against
the reason written in site.ts; 83px of residual overflow at a 200% default font
size, now 3px.

Seven more I found myself first, including <Picture widths> declaring the
untouched 1600px master as the <img src> fallback (254,626 B for a 476px slot,
and the build log said "before: 349kB" either way), and a prop named `as`
silently turning off type-checking for a whole component.

VERIFICATION — run, not asserted. Full figures in AGENTS.md entry (w).

npx tsc 6.0.3 · check 0/0/0 · lint clean · build clean · audit 0
1 <script> and it is JSON-LD; non-JSON-LD scripts 0; no JS bundle; identical
page with script execution disabled (444 nodes, 6,578 chars)
Phase 5 minifier check: no `animation` shorthand beside animation-timeline
overflow 0 at 14 widths, AND every mark measured at 1.5654-1.5657 vs 1.5657
one h1, no heading skips, focus order == DOM order across 44 focusables
31 painted contrast pairs at 3 widths, 0 failures
72/72 hit-test points across 8 cards resolve to the card's link
print 0 hidden, reduced-motion 0 hidden
Lighthouse NOT RUN — tool unavailable until step 7 (R11)
HTML validator NOT RUN, and 4 of 12 srcsets carry a duplicate 1x descriptor

Opened for Pouya: Q40 (one OG image for nineteen pages), Q41 (does Q37 reach
prose; may the comparative be restored; what LAT pre-hearing mediation means),
Q42 (the four "also offered" processes have no row), Q43 (the process timings
are published commitments with no row).

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

CLAUDE.md

@@ -236,6 +236,48 @@ correction reached §7 and never reached it, and the stale copy ended up telling
 an operator to delete the three records that authenticate outbound mail —
 under the heading "Never delete".
 
+**A measurement is a claim about your instrument until you check the
+instrument.** This has now cost five times, and the shape is identical every
+time: a number that looks like a finding, from a probe nobody validated.
+
+- `timeout 60 ls "$DRIVE"` — **the command never ran.** `timeout` is not
+  installed on macOS. Empty output from a command that failed to start looks
+  exactly like empty output from a command that found nothing, and it produced a
+  report that the brand assets were unreachable when the directory was fully
+  readable.
+- **`1.23:1` for the traced mark** — the bounding box of the path's *coordinate
+  hull*, not of the curve. A cubic's control points sit outside it, so the box
+  was 33% too tall while giving the *correct* width — which means the obvious
+  sanity check, "does the width look right?", passes.
+- **"the mark renders at 24px"** — the harness reported the worst-deviating
+  instance on the page, not the instance under discussion, which was exact.
+- **"0 overflow at every width"** — true, and it measured the *document*. A flex
+  child was absorbing the deficit by being crushed to aspect 0.891. **Measure
+  the elements, not only the page.**
+- **`img.naturalWidth` = 64 at DPR 1, 2 and 3** — which reads as *the density
+  ladder is not being generated at all*, a shipped defect on every page. It is
+  **density-corrected by spec**: a 192px file selected at `3x` correctly reports
+  64. The files on disk were 64 / 128 / 192 all along.
+
+So before acting on a number: say what it is a number *of*; confirm the command
+actually ran and read its exit status; and check it against a second method that
+cannot fail the same way — the bytes on disk, a screenshot, a hit test.
+
+**And a grep that matches is not a finding until you read what it matched.**
+A case-insensitive sweep for `LSO` hit `I aLSO practise`; a superlative sweep for
+`leading` hit `the pLEADINGs`. Both on the same page on the same day. Print the
+match with context before you believe it.
+
+**Never name an Astro prop `as`.** `const { as = 'p' } = Astro.props` detaches
+the `Props` interface from the component, and **every call site silently stops
+being type-checked.** `astro check` reports it only as `ts(6196) 'Props' is
+declared but never used`, which reads like lint noise. Measured: with the prop
+named `as`, `<Eyebrow dot as="h9" bogusProp={1} />` compiled with **0 errors**;
+renaming the one identifier to `tag` made the same probe fail correctly. **Do not
+silence a `ts(6196)` with `Astro.props as Props`** — that hides the warning and
+leaves the call sites unchecked, which is strictly worse. If that hint appears on
+any component, pass it a bogus prop before believing its props are checked.
+
 **A sweep is a command, not a claim.** Any statement that a change was applied
 across files — a phrase removed everywhere, a path updated everywhere, a
 decision swept through the docs — must cite the command that proves it, and be