Public: anyone can read this; the crew can change it.
The waves page fits a 390 px phone: no sideways scroll, long names wrap #9325
Reviewed pull #9339 at its head: ticked A test renders the repository's waves page with seeded long content: a 300-character unbroken word, a long title, many rows. It asserts that no inline width/min-width and no rule the page ships fixes a width over 390 px, and that the long-text containers carry overflow-wrap: anywhere (or break-word). It fails without the fix, or, if the page already fits, it pins that.; Anything it finds is fixed in src/web/pages/waves.ts. Any new class is named in docs/design/areas/waves.md (create it if absent), not docs/DESIGN.md.; bun scripts/design-lint.ts passes. Run the new test file and the page's existing tests; the forge runs the rest.. left open: The pull description links the preview's phone look of /preview-admin/sample/waves, and says in one line whether it scrolls sideways. — The description is the builder's final message and the last text said the sideways scroll was not checked; it must link the 9339 preview and state the result..
Left open after pull #9339 landed: 1 unticked item remains (The pull description links the preview's phone look of /preview-admin/sample/waves, and says in one line whether it scrolls sideways.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
The owner opens /preview-admin/sample/waves on a 390 px phone. The page must not scroll sideways, and no single row or card should be taller than the screen. Follow the pattern of test/bets-card-fit.test.ts (#9286).
Done looks like:
width/min-widthand no rule the page ships fixes a width over 390 px, and that the long-text containers carryoverflow-wrap: anywhere(orbreak-word). It fails without the fix, or, if the page already fits, it pins that./preview-admin/sample/waves, and says in one line whether it scrolls sideways.bun scripts/design-lint.tspasses. Run the new test file and the page's existing tests; the forge runs the rest.Files: src/web/pages/waves.ts, docs/design/areas/waves.md (create it if absent), one new test file. Risks: change no route and no data read. Don't touch src/http/api.ts.