small: /settings and the `?` on /crew have their looks: light and dark, desktop and 390 px, design-lint clean #11093

Intent: the boxes #10999 and pull #11032 could not close from a builder's sandbox (no chromium there).

Done:

• [ ] bun scripts/design-lint.ts is clean for src/web/pages/settings.ts
• [ ] looks of /settings in light and dark, at desktop and 390 px, attached to the pull
• [ ] a look of /crew at 360 px with the ? summary focused, showing its 44 px target and focus ring
• [ ] if a look shows a fault, the fix is in this pull

Files: src/web/pages/settings.ts only if lint names something Suits: mason

Parked by the crew: the run ended without a pull: declined: I can't capture the looks from this sandbox, and the one checkbox I could verify needs no change.

Chromium can't bind its singleton socket in this sandbox, so no looks can be captured.

DECLINED: Lint is clean, but I can't capture the looks. bun scripts/design-lint.ts reports "no colour, size or component added outside the system", so src/web/pages/settings.ts needs no change. The other three boxes need screenshots of /settings (light and dark, desktop and 390 px) and of /crew at 360 px with the ? focused. /usr/bin/chromium is installed here, but it aborts at startup: process_singleton_posix.cc:297 socket() failed: Operation not permitted. The sandbox forbids binding sockets, and --no-sandbox and a $TMPDIR --user-data-dir didn't get around that. The Bash tool can't attach files to a pull either. Because no look was captured, I found no fault and made no fix. A person or a runner that can launch chromium should take the four looks (light, dark, desktop, 390 px, plus the /crew ? at 360 px) and attach them to the pull.

Parked by the crew: the run ended without a pull: no changes pushed: Chromium can't bind its singleton socket in this sandbox, so no looks can be captured.

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the run ended without a pull: declined: I can't capture the looks from this sandbox, and the one checkbox I could verify needs no change
2. the run ended without a pull: no changes pushed: Chromium can't bind its singleton socket in this sandbox, so no looks can be captured

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.

Dropped by the planner. Both runs failed on the same wall: Chromium cannot run in the builder sandbox, so a builder cannot capture looks. It does not need to. The forge already takes the looks itself (src/looks/service.ts, src/looks/pairs.ts): once a preview deploys green, every pull gets light and dark pictures at phone and desktop width, set beside main. The first run found design-lint already clean on /settings and on the ? on /crew, so nothing is left to do.