2 Commits

Include renames

Author	SHA1	Message	Date
Pouya LajevardiandClaude Opus 5	02739adac9	fix: refute (ar)'s intake finding; fix the D20 gloss class; add X-Robots-Tag on *.pdf ... Pouya's rulings of 2026-09-03, in five parts. 1. THE INTAKE FORM IS NOT BROKEN. (ar) was wrong. docs/09 §7.1 verbatim — POST /api/intake with an Origin header — returns 303 to /contact/could-not-send/ with access-control-allow-origin echoed; the same probe without Origin returns 403. A bare POST 403s BY DESIGN and §7.1 says so three lines below the probe it prescribes: "403 means the Origin header did not arrive". The earlier finding read a status code without reading the document that defines it. Second time in two days. CLAUDE.md's instrument list goes eight to nine. D20 findings 12 and 19 fall with it; §7.2 (that both emails arrive) is still owed. The correction is APPENDED as entry (as); (ar) stands unedited. 2. The privacy retention comment was stale, not a defect — superseded by his decision to publish and confirm after launch, reading from 2026-09-04. Reworded; the TODO(pouya) came off with the gate it enforced. The mechanism finding survives: it was a JSX comment, stripped by Astro, so no build or deploy path could see it. A publication gate that lives only in a stripped comment is not a gate. §9 Q60 corrected. 3. The gloss class is fixed — 15 of the 20 D20 findings, 14 distinct edits across 9 files, under the rule "the gloss may say no more than the extract says; no new claims, no new sources". Swept three unpublished insights drafts too, and corrected the wrong CAA attribution at its source in docs/reference/, which is where a fixed page re-seeds. /bio/ changed, so the committed PDF is regenerated (89,549 B, 1 page asserted). Three findings outstanding: 10 needs a ruling, 11 is ruled and owed via Q60, 13 needs him to have said it. R1 is not one of the twenty. 4. X-Robots-Tag cannot be done with S3 object metadata — --metadata writes user metadata, returned as x-amz-meta-x-robots-tag, which no crawler reads. Built as the CloudFront response-headers policy docs/06 has specified all along: configure.mjs section 4. It needs a --apply run, not a deploy. The policy is cloned from whatever is attached at run time and reconciled on every run, because a response-headers policy replaces rather than merges. 5. Headshot deferred as an open non-defect. The master and the srcset ladder are both fine; Astro passes no quality, so AVIF encodes at sharp's default 50 and is served first. Two review rounds, 29 findings, all resolved, none declined; stopped at two per D19. NINE of round 2's fourteen were defects in round 1's own repairs — including a fix that harmonised both /fees/ rows onto wording that was itself unregistered, publishing an unsourced fee term twice where it had been once. Gates, exit status read for each: check 0 (0 errors, 0 warnings, 0 hints), build 0 (23 pages), check:claims 0, check:intake 0, og:proof 0, lint 0, minifier grep exit 1, router.test.mjs 30/30. Lighthouse NOT run. Nothing deployed and nothing applied to the distribution. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5	2026-09-03 17:23:20 -04:00
Pouya LajevardiandClaude Opus 5	210bc25a26	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	2026-08-31 10:56:54 -04:00