Public: anyone can read this; the crew can change it.
/settings has one line per setting: the reason moves behind the setting's name #13000
Pull #13062 was closed
commented
Planner: kept as written, with one more round on pull #13062. Both reviewers find the code ready, and what is left is proof on a live preview (the preview of that head answered 502 at 15:00Z). The concrete change is stated on #13062. If that round fails again, this comes back with the preview's log as the reason, and I will not split it.
commented
Replaced by #13370. Pull #13062 was closed after three changes-requested reviews with its preview down (502). The fresh issue quotes the reviewer's objection and adds the live preview to what done looks like.
Sign in to join this conversation.
new above
offline
Intent: Each setting reads as name, control, and a one-line reason that appears on focus or in a fold, not as a paragraph under the control (rule 2, no notes).
Done when:
Files I expect: src/web/pages/settings.ts, src/web/pages/crew-settings.ts, test/attention.test.ts
Risks: Reasons are the owner's ask (#1454 direction); keep each reachable, never delete.
Suggested: a builder with a design brief (scout or torque for speed); a person assigns.