Development record
The bare status board ignores the terminal's width: in an 81-column window the receipts line and every long intent title hard-wrap back to column 0, breaking the board's hanging indent (product thinker's screenshot, 2026-10-03). The same render indents rows at 2, 4, 6 and 10 columns, prints Go's raw true/true/[development work work.local] for the first three rows, and lists the next-up intent under both Now and Next, so it reads as a duplicate.
The bare status board ignores the terminal's width: in an 81-column window the receipts line and every long intent title hard-wrap back to column 0, breaking the board's hanging indent (product thinker's screenshot, 2026-10-03). The same render indents rows at 2, 4, 6 and 10 columns, prints Go's raw true/true/[development work work.local] for the first three rows, and lists the next-up intent under both Now and Next, so it reads as a duplicate.
Note (2026-10-03)
Linked to itd-2610031214560142, the product thinker's board, which is drawn through the same wrap helper and is built after this fix. The duplicated next-up row is owned here, not by the board draft (the technical facilitator's ruling, that draft's decision 9), so the remedy names the brief-chapter edit it needs. The remedy now names internal/textwidth.Wrap as the primitive, and found_at names the renderers that wrap, from the record-discipline review of 2026-10-03 (reports/review-board-records.md in the local tier).
Grounds
- pursued: TestBoardWrapsEveryRowAtTheWindowWidth and TestPipedBoardWrapsAt80WithNoEscape hold every line within the window, never at column 0, with no escape byte off a terminal, and TestTheHeadIsListedOnceUnderNow holds the single listing; a board line wider than the window, a continuation at column 0, or the head under Next would show it wrong.
Frontmatter
| id | iss-2610031207397996 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610031207397996-the-bare-status-board-ignores-the.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610031214560142The board shows a product thinker what waits on them and what comes next, in a few plain linesrelated
mentions6
- dcn-26100300000000022026-10-03 — Ruling of the product thinker, asked by abcd-50 one question at a time, on where the status board lists the intent that starts next (iss-2610031207397996; it was listed under Now marked next up and again under Next), verbatim: "Under Now only". Not chosen: under Next only, at the top (Now would mean building alone, at the cost of reversing criterion 3 of itd-2609212103568351, that Now holds the head without a state file); decide later. Applied: `statusblock.Read` drops the head from Next, so the bare board, `--json` and the site's Status page list it once, and the shipped intent's Audit Notes record the amendment to its criterion 1. Decided without a question in the same change (technical facilitator): the board's width is the terminal's when stdout is one and 80 columns otherwise, whatever COLUMNS says, so piped output is the same on every machine; a wrapped line continues four columns past its own indent; a review row begins at column four with its stale mark at its end, so the levels are indented two, four and six.
- iss-2610262044382852The board intent calls an intent listed under both Now and Next a defect, but the shipped status block lists the pick head in both by construction
- itd-2609212103568351The status board shows Now, Next and Later, computed from the record
- itd-2610031215002409A 'what next?' menu under the board offers the next step, in a Terminal and in a Claude Code session
- spc-2610031844142274when-you-type-abcd-in-a-terminal-or-ask-for-the-board-in-a
- spc-2610031844158884under-the-board-a-short-what-next-menu-offers-the-few-steps