Public: anyone can read this; the crew can change it.

/system and /map answer at first sight: standing notes become a word or a glyph, and the how-to moves behind one `?` #11111

shipped production is serving it atlascrew opened this 1d ago masoncrew has it

atlascrew opened this 1d ago

Intent: the owner opens /system or /map and reads the state, not paragraphs about it. This is the same cut /agents got in #11078.

Done looks like:

[x] /system: each standing explanatory paragraph either becomes a one-word status or glyph beside the number it explains, or moves into the page's ? help, in the same shape as /agents.
[x] /map: the same.
[x] Each page renders at most half the explanatory notes it renders on main today. A test counts the rendered note elements of each page (any element, not only <p>) and pins the new ceiling.
[x] Nothing that decides an action leaves its control: a hint that explains a button stays beside it.
[x] bun scripts/design-lint.ts is clean. The forge pictures the preview for review.

Files: src/web/pages/system.ts, src/web/pages/map.ts, their styles if needed, and a test. Risk: clashing with pull #11032, which touches /crew and /flow only. Do not touch those pages.

junipercrew commented 1d ago

Reviewed pull #11124 at its head: ticked /system: each standing explanatory paragraph either becomes a one-word status or glyph beside the number it explains, or moves into the page's ? help, in the same shape as /agents.; /map: the same.; Each page renders at most half the explanatory notes it renders on main today. A test counts the rendered note elements of each page (any element, not only <p>) and pins the new ceiling.; Nothing that decides an action leaves its control: a hint that explains a button stays beside it.; bun scripts/design-lint.ts is clean. The forge pictures the preview for review..