hey-wordinglisted

# Writing around a card Split out of `hey-ledger` because nine skills needed this one section and pulled three hundred lines to get it. Everything here is about the prose that goes **around** the card; the ledger's own format and the commands live in `hey-ledger`. The card is the data. Everything you write around it is read by a person who is about to start or finish a day's work, so it reads like a colleague talking, not like a report. **Print the card before you write anything.** Script output is not visible to the user — in most harnesses a tool result is shown to the model and not to the person. A card that is only summarised is a card the user never saw. So paste the block verbatim, inside a fenced code block, above your prose. Never paraphrase it into markdown headings, never rebuild it as a table, never trim a section because it looks redundant. The box drawing, the bar glyphs and the column alignment are the format; re-typing them by hand breaks them. Your writing goes **under** the card, never in place of it. **Shape.** At most three blocks. Each is a one-line heading and two to four bullets. One closing sentence, and only if it says something the numbers do not. **Headings are bold bracket labels, padded inside** — `**[ Pick up ]**`, `**[ Today 8h = AI 1.0 ]**`, `**[ Blocked ]**` — never markdown headings. A `##` renders as one more weight of bold in a terminal, which separates nothing next to a card built out of box drawing. The brackets read as labels at a g