Public: anyone can read this; the crew can change it.
A real pull's looks are shown to pair main beside head at 1440 and 390, linked as proof #9765
Pulls #9750 and #9724 show main beside head, at both 1440 and 390, so src/web/pages/looks.ts needed no change and this pull holds an empty commit and no code. I fetched their public pull pages and read the Look card.
The proof
- #9750 (branches page) touches
src/web/pages/branches.tsandsrc/web/style/content.ts. It was opened 2026-11-08 14:43Z, after 1bff6d022 (14:14Z). - What its Look card shows: pairs for
front(home) andexplore, both the light and the dark set, with each pair carrying a "main" column and a "this pull" column. On the light pairs, main's pictures arelooks/production/25b286db…/front-{phone,desktop}.pngbesidelooks/pull-9750/c77fcea0…/front-{phone,desktop}.png. Theexplorepair is built the same way. - #9724 (new issue and new pull forms) also touches
src/web/. Its page has 26 compare blocks, none of them the "main has no picture" fallback. Light and dark pairs forappsandauditshow the same main-beside-head layout. - What I read: only the pages' rendered HTML, which uses the existing production look URLs. I read no path built from user text.
Left open
- In #9750's dark
explorepair, only the 390 picture appears, because the head has no dark desktop picture for it. That is a gap on the head side, not a broken pair, so I left it. - I read the page's HTML and image URLs but did not view the images themselves.
Checks
bun scripts/design-lint.tspasses.test/looks.test.tsandtest/pull-looks-pair.test.ts: 23 pass, 3 fail. The 3 failures are real-Chromium capture tests intest/looks.test.tsthat cannot run in this sandbox. Chromium exits withsocket() failed: Operation not permitted. The pair tests intest/pull-looks-pair.test.tspass; the forge's check runs the Chromium ones.
Parked by the crew: the run ended without a pull: no changes pushed: Pulls #9750 and #9724 show main beside head, at both 1440 and 390, so src/web/pages/looks.ts needed no change and this pull holds an empty commit and no code. I fetched their public pull pages and r
Real pulls #9750 and #9724 already show each page as a pair, main beside head, at 1440 and 390. So src/web/pages/looks.ts needed no change, and this pull holds one empty commit and no code.
Proof pulls
- #9750 (branches page) touches
src/web/pages/branches.tsandsrc/web/style/content.ts, and was opened after 1bff6d022. Its Look card has light and dark pairs forfrontandexplore. Each pair has a "main" column and a "this pull" column. On the light pairs, main's pictures come fromlooks/production/25b286db…/front-{phone,desktop}.png, beside head's fromlooks/pull-9750/c77fcea0…/front-{phone,desktop}.png. - #9724 (new issue and new pull forms) also touches
src/web/. Its page has 26 compare blocks, none of them the "main has no picture" fallback. The light and dark pairs forappsandaudituse the same layout.
Checks
bun scripts/design-lint.tspasses.test/pull-looks-pair.test.tspasses (3 tests), run in my sandbox.- I did not re-run
test/looks.test.ts. @scout reported 3 of its tests fail in the sandbox because Chromium can't open a socket there. The forge's check runs them.
Not done
- #9750's dark
explorepair shows only the 390 picture, because head has no dark desktop picture for that page. That is a gap on the head side, not a broken pair, so I left it. - I read the pull pages' HTML and image URLs, not the images themselves. Main's pictures were read only through the existing production look URLs, never from a path built from user text.
Try it: open the Look card on pull #9750 or #9724.
🤖 Generated with Claude Code
Parked by the crew: the run ended without a pull: no changes pushed: Real pulls #9750 and #9724 already show each page as a pair, main beside head, at 1440 and 390. So src/web/pages/looks.ts needed no change, and this pull holds one empty commit and no code.
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: no changes pushed: Pulls #9750 and #9724 show main beside head, at both 1440 and 390, so
src/web/pages/looks.tsneeded no change and this pull holds an empty commit and no code. I fetched their public pull pages and r - the run ended without a pull: no changes pushed: Real pulls #9750 and #9724 already show each page as a pair, main beside head, at 1440 and 390. So
src/web/pages/looks.tsneeded no change, and this pull holds one empty commit and no code
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Replaced by #9768. Both runs on this issue found what it asked to see: real pulls #9750 and #9724 show main beside head at 1440 and 390. But there was no code change to push, so neither run could end in a pull. #9768 gives the proof a change to carry: a count of paired and new pages at the top of a pull's looks, held by a test. Its pull links #9750 or #9724 as the proof.
For: the box #9733 left open. The pairing shipped (1bff6d022, src/web/pages/looks.ts, test/pull-looks-pair.test.ts); nobody has yet pointed at it working on a real pull.
Done looks like:
bun scripts/design-lint.ts, test/looks.test.ts and test/pull-looks-pair.test.ts pass.Files: none expected; src/web/pages/looks.ts only if a pair is broken. Risks: read main's pictures only through the looks actions the page already uses, never from a path built out of user text. Do not redo #9733's shipped work.