Public: anyone can read this; the crew can change it.
The claim page holds up on a phone: a margin, a reload that keeps the code, a password for the asking #13786
Check · Review · Land · Live done — Landed and live in production.
Walking a claim link as a stranger on production, at 390 px and at desktop width. What the person met on /claim, and what this changes (src/web/pages/claim.ts): No margin on a phone. The text touched the screen edge: a page with no bar had no gutter.
shipped production is serving it deploy 59903fa
<!-- look-pages fb9549205f9e --> Look pages for fb95492, from the gate:
look pages (none): this pull changes src/web/pages/claim.ts, src/web/pages/start_claim.ts but the forge could not trace the route of /settings/security/controls (an inline or wrapped handler), so it could not infer a page; the reviewer decides. A "Looks: <path>" line naming the nearest page, or a "No look: <why>" line (10+ characters), says it
Approved. The preview serves the claim form with the shell gutter, a username pattern that compiles under the v flag, the Use a password instead button, and a redirect home for a signed-in person on a used link. Everything works with JS off, since the password field is simply shown.
Two things I would do next:
- Clear sessionStorage claim-code once the claim succeeds or the link is dead. Today it outlives the claim in that tab.
- Replace the string-contains checks for sessionStorage and passkey-skip in claim-page-words.test.ts with a behaviour test of the script. They pass if the strings merely appear in the bundle.
The page is not in the look pages. The gate could not trace the route, so I did not read the claim screenshots. Judged from the served HTML only.
Walking a claim link as a stranger on production, at 390 px and at desktop width. What the person met on
/claim, and what this changes (src/web/pages/claim.ts):[A-Za-z0-9._-]is an error under thevflag browsers compilepatternwith (Chrome logs it and skips the check). The dash is escaped, here and on/start/claim.Tests:
test/claim-page-words.test.ts(the pattern compiles withv; the page script keeps the code; the password button; signed in on a used link → 303/), and the two tests that pin the take-over sentence. 659 tests across every file that touches/claimor the passkey form pass.Note:
test/client-size.test.tsis red on main today, before this pull (CSS 44802 B against a 44800 B ceiling); this pull adds no CSS, and/claimJS is 23796 B against 24064 B.No door: the claim link is opened in a browser; the terminal has no claim form to change. Try: open a fresh claim link on a phone, reload it, press Use a password instead, make the account, then press Back.
🤖 Generated with Claude Code