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
This commit is contained in:
co-authored by
Claude Opus 5
parent
6cfe69033f
commit
210bc25a26
@@ -19,13 +19,37 @@ npm run dev # http://localhost:4321
|
||||
| Command | Does |
|
||||
|---|---|
|
||||
| `npm run dev` | Development server with hot reload |
|
||||
| `npm run build` | Static build to `./dist` |
|
||||
| `npm run build` | Static build to `./dist` — 22 pages |
|
||||
| `npm run preview` | Serve the built site locally |
|
||||
| `npm run check` | `astro check` — type and template errors |
|
||||
| `npm run check:claims` | `AGENTS.md` §4 Forbidden, enforced on `dist/`. **Runs on every deploy** |
|
||||
| `npm run check:intake` | The intake form's field table against the Lambda's — two on purpose |
|
||||
| `npm run og:proof` | Every `og:image` resolves; every card headline **is** its page's `<h1>` |
|
||||
| `npm run lint` | ESLint + Prettier check |
|
||||
| `npm run format` | Prettier — rewrite files in place |
|
||||
| `npm run lighthouse` | The performance budget, all four categories. **Local only** |
|
||||
| `npm run bio:pdf` | Re-renders the committed one-page PDF from `/bio/`. **Local only** |
|
||||
| `npm run deploy` | Build and deploy from this machine — see Deployment |
|
||||
|
||||
**Two of those cannot run in CI, and that is stated rather than left to be
|
||||
discovered.** `lighthouse` and `bio:pdf` drive an installed browser; the Gitea
|
||||
runner has none. 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 — 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 here are deliberately
|
||||
duplicated**, and a duplicated fact needs a mechanism rather than a comment.
|
||||
Text baked into an OG card cannot be grepped by `check:claims`, so `og:proof`
|
||||
comparing each card's headline to its page's `<h1>` is the only thing keeping
|
||||
card copy inside the claim register. And the Lambda validates against its own
|
||||
field table, because a server that validates against a list the client shipped
|
||||
it is not validating.
|
||||
|
||||
*(`npm run check:claims` was missing from this table before 2026-08-31, along
|
||||
with the four added that day. A table of the project's controls that omits a
|
||||
control is the shape those controls exist to catch.)*
|
||||
|
||||
## Before you contribute
|
||||
|
||||
Read **`AGENTS.md`** first, and maintain it as you work — it is the living
|
||||
|
||||
Reference in New Issue
Block a user