5 Commits

Include renames

Author	SHA1	Message	Date
Pouya LajevardiandClaude Opus 5	3c3ba5dc6e	feat: price med-arb by phase, attest the conflicts undertaking, and answer the first real spam ... Pouya's rulings of 2026-09-03 (the last two D20 findings) and 2026-09-04 (the spam observation and four mitigations), in one change set. D20 finding 10 — med-arb is billed BY PHASE, each phase at the rates already published, so /fees/'s "Every figure is on this page" is true as written rather than narrowed. FEES.medArb is the single source; docs/07 §Med-arb carries the rule INTERIM against R5, and R5 now carries it back, because a derived price moves silently when a rate moves. D20 finding 13 — conduct undertaking (g), attested 2026-09-03, published as his wording verbatim on /legal/privacy/ and /contact/. The clause that raised the finding promised to DISCLOSE a conflicts check's outcome, which the attestation does not cover; it is struck. D20 now partitions 17 fixed / 2 refuted / 1 owed. Spam, 2026-09-04 — recorded in docs/05 §Observed abuse with the date and signature. A second honeypot (a decoy checkbox, own class, `hidden`, a label that tells a human not to tick it) and scoring that LABELS and never rejects: nothing is dropped, nothing new is stored, and only the operator notification changes. Q65 opens the WAF cost call. The timing floor could not be built: there is no timing check and never has been. docs/05 carries it struck, and every mechanism that would give a real per-visitor clock breaks zero-JS, handler-and-form-only, or D1. Q66. configure.mjs gains section 5 — a custom origin request policy forwarding CloudFront-Viewer-Address on /api/*. Written, dry-run against the live distribution, NOT applied. It reads the handler's own header reads and refuses to run if the whitelist omits one. And reading the live account to do it found four AGENTS.md §7 rows saying the intake backend was undeployed, two days after it went live — corrected against get-function-configuration, get-routes, get-stage, get-policy and the deployed zip, which was downloaded and read. Review: adversarial-reviewer only (claims-auditor is D20's cutover pass and has run). Round 1 five lenses, 56 findings, 7 blocking, 4 refuted by an independent refuter; round 2 four lenses, 36 findings, 33 of them defects in round 1's own repairs. Stopped at two per D19. Gates, exit status read for each: check 0 · build 0 (23 pages) · check:claims 0 · check:intake 0 · og:proof 0 · lint 0 · spam-score.test 39/39 with 6/6 mutations killed · router.test 30/30 · minifier grep 1 (clean) · lighthouse 0, no category below 95 · configure.mjs dry run 0, nothing written. Nothing deployed and nothing applied. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5	2026-09-04 10:06:37 -04:00
Pouya LajevardiandClaude Opus 5	bd282aa47d	feat: production run — Q61 ramp, /404/, CloudFront router, cutover runbook ... Five items of Pouya's production run, 2026-09-01. Q61 — scroll-padding-top becomes a max() ramp on `10lh - 83px`, with the plain calc() first as the fallback for engines without `lh`. Hidden focus stops under minimumFontSize=32: 290 of 1,455 -> 0, control build still 290. Default settings byte-identical (0 differences over 352 page-widths x 17 fields). The 12 residual cells at minimumFontSize=16/20 are pre-existing and unchanged-or-better; reported, not widened, per instruction. Intake backend + CloudFront — docs/09-cutover-runbook.md is the copy-paste sequence for admin execution: every command followed by its verification and expected output, rollback per part, and Part 10 is Q60's TTL test. infra/cloudfront/router.js is the trailing-slash function (30-case suite; 8 fail against the pre-review version, incl. a protocol-relative open redirect). infra/cloudfront/configure.mjs is dry-run-by-default and idempotent. scripts/intake-env.mjs emits the six Lambda env vars from src/data/site.ts. Four launch blockers found by reading the running system: - handler.mjs wrote pk/sk; the live table's key is submissionId with no sort key, so every submission would have failed validation silently - the Lambda invoke permission is scoped to the old route path - 22 of 23 pages 403 without the router function - there was no 404 page; src/pages/404.astro adds it Claims audit (D20 cutover pass) — five gloss over-reaches corrected on /practice/energy/, /practice/insurance/ (x2), /practice/technology/ and /med-arb/. Three findings left open for Pouya: Q62, the /med-arb/ gloss, and Q60. Q62 — one frozen-tripwire pattern added under the freeze's own breach exception, with a probe and four negative fixtures. check:claims exits 1 until the false /legal/privacy/ sentence is corrected, so both deploy paths are blocked by a mechanism rather than by memory. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5	2026-09-02 06:52:20 -04:00
Pouya LajevardiandClaude Opus 5	64bce105f8	feat: eyebrow 12px → 13px from one definition; confirm and gate the intake TTL ... Two of Pouya's rulings of 2026-08-31, committed as one tree at his instruction ("as-is") because AGENTS.md Change Log entry (ai) covers both and splitting it would mean rewriting the record rather than moving it. This is a deliberate departure from one-logical-change-per-commit, recorded here rather than left to be inferred. THE EYEBROW. `--text-eyebrow: 0.8125rem` added to tokens.css; `.eyebrow` in global.css retargeted to it. One edit site, which is what the design system claimed. 13px is not a rung on the modular ladder — it sits between xs and sm deliberately, because uppercase mono at 0.18em tracking reads smaller than it measures. `--text-2xs`'s comment stopped calling itself the eyebrow floor. The rendered sweep (22 pages × 2 widths, 838 mono elements measured over CDP, not grepped) found exactly one escape and one deliberate override: - h2.footer-heading, 176 instances — an ESCAPED EYEBROW. Five declarations byte-identical to `.eyebrow`, differing only in colour. Consolidated to `class="eyebrow footer-heading"`; the scoped rule is now colour + margin. The colour is load-bearing, not decorative: `.eyebrow`'s own `--text-meta` on ink is 3.07:1 and fails. - span.eyebrow.brand-tagline, 21 instances — HELD at `--text-2xs`. Measured: at 13px the header grows 81 → 83.4px while `--header-h` is pinned at 81 and drives `scroll-padding-top`; and with a seventh nav item the CTA lands past `.header-inner`'s content edge by 42px at 1216, 18px at 1240, 26px at 1280 and 1440. Document overflow is 0 in all of those, so no page-level check can see it. Insights is that seventh item. Everything else mono-uppercase is a genuinely different component and was left: the 0.06em `--tracking-wide` family, the 14px mixed-case designation strip, the /bio/ print sheet, /contact/'s form labels. Measured after: contrast unchanged on all 817 instances (11.09 / 8.11 / 5.47 / 5.01:1, all pass at 13px, which is still normal text and needs 4.5:1). Zero document overflow and identical header geometry at 15 widths. Two eyebrows gain a line below 414px — /'s hero, already wrapping at 320px before this, and /insights/'s empty state at 320px only. Accepted, not re-tuned. docs/02's type spec moved 11–12px → 13px and now enumerates the three 11px carve-outs instead of implying there are none. The /type-scale/ proof sheet (d) asked for no longer exists — deleted at build step 2 — so the spec prose is the proof sheet now. THE TTL. backend/intake/handler.mjs CONFIRMED to match `AttributeName=ttl`: it writes `ttl` as a Number, in epoch seconds, at RETENTION_MONTHS = 24. Nothing needed changing for the enable command. Removed `|| 0` from the TTL computation. DynamoDB does not expire an item whose TTL is more than five years past, so `ttl: 0` meant RETAINED FOREVER while /legal/privacy/ promises deletion — a fallback whose failure mode was the exact inverse of the claim it was protecting. Unreachable in practice, which is why it would never have been noticed. A bad value now fails the write. §7 records TTL as DISABLED at first verification, so the privacy policy's automatic-deletion promise was unbacked from the moment it was written. §7 is the only place that status lives; docs/05 and docs/06 carry the constraint and cite §7, because round 2 of review caught this change set reproducing the SES DKIM defect — five copies of a status that is about to be re-stamped. Added, and these are the gate: `TODO(pouya)` on /legal/privacy/'s retention section, §9 Q60, §12 R19. The page does not publish a period, it asserts a MECHANISM — deleted by the database rather than by someone remembering — and nothing in the toolchain can see that. check:claims is frozen with no pattern for it and deploy does not read docs/06. The copy was NOT softened: it is about to be true, and weakening a privacy commitment to make it defensible is the move the rules forbid. What was missing was the gate, not the caveat. Reviewed by adversarial-reviewer, two rounds (D19 cap), 15 findings, all accepted, none declined. claims-auditor did not run — D20. Round 1's findings were almost entirely in prose written that session, and round 2's blocking finding plus its sharpest should-fix were both defects in round 1's own fixes. public/pouya-lajevardi-bio.pdf is deliberately NOT in this commit. It was regenerated and reverted: /bio/'s eyebrow sits inside `.no-print`, so the sheet has no eyebrow at all, and `cmp -l` showed exactly 10 differing bytes, all in /CreationDate and /ModDate. Gates, every one read as an exit status and none through a pipe: check 0, build 0 (22 pages), check:claims 0, og:proof 0, check:intake 0, lint 0, minifier tripwire clean, TODO in dist 0. Lighthouse run twice with identical output: perf 99 on / and 100 on the other 21, a11y 100, best practices 100, SEO 100 on every indexable page, CLS 0.000, LCP 1.50–2.03s. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5	2026-08-31 13:44:57 -04:00
Pouya LajevardiandClaude Opus 5	9f2d2eeb04	fix: resolve adversarial review round 2 — 9 findings, 8 of them in round 1's fixes ... D19 caps the loop at two rounds, and this is what the second round is for. BLOCKING. Round 1 made NO_RETAINER_NOTICE a requireEnv and added it to no document, while the fix's own comment claimed docs/06 named it. The deployment list said five variables for a handler that needs six, so an operator following the cutover checklist would have deployed a function that throws at cold start on every invocation — 5xx from API Gateway, every inquiry lost from the moment /api/* was wired, loud in CloudWatch and silent to Pouya. docs/05 and docs/06 now name all six, and the comment that asserted the documentation existed is corrected rather than deleted. The intake route check added in round 1 could not fail: curl -w already prints 000 on a failed transfer, so `|| echo 000` double-appended and the failure arm was unreachable, and the pass arm accepted anything that was not literally 404 — including the 403 CloudFront returns when the /api/* behaviour is missing, which is the one distinction the check exists to draw. It now sends the correct Origin and asserts a positive: 303 to /contact/could-not-send/, which the handler returns before any DynamoDB write or email. Probed on refused/501/403/303; the old version passed the first three. Fixed in both deploy paths. Removing priceRange left three statements saying it was present or pending, one of them the stated reason /fees/ emits no Offer node. Deleting overtimeStartsAfterSessionHours left AGENTS.md §9 naming it and left Q59 recorded as open. The Google-as-processor fix was applied to the privacy policy's "Where it is stored" and not to "Who can see it", which still read "Nobody else has access". And the variable removal was justified with a path-scoped git grep — which also cannot see untracked files. The unscoped sweep found docs/06's variable table, the OIDC example, and .env.example still carrying them; .env.example also restates the execute-api hostname, falsifying a live claim in intake.ts that has been corrected. That file is not edited here: this environment denies read access to it, and nothing may edit a file it cannot read. It is in the batched list. Also: og:image:alt was the page title rather than the card's headline on 20 pages; og-card.ts documented the wrong path and invocation for the contact sheet; deploy-local.sh still said Q22's deploy credential "does NOT yet exist"; and the round-1 fix comments were trimmed per D19, though the ratio held at 0.44. Round 2 also confirmed the round-1 fixes by measurement: all 56 .btn instances across 22 pages, the consent checkbox's computed accessible name, the radio labels hit-tested at 44px, and og:proof exercised against synthetic article pages in a sandbox. Verified: check/build/check:claims/og:proof/check:intake/lint/bio:pdf all exit 0 on a clean build; 22 pages; Lighthouse 99-100 / 100 / 100 / 100, CLS 0.000. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Md3GndFqWPzK78xAoebsg5	2026-08-31 11:21:07 -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