Development record

The status line's counts should show what can run autonomously now, not the backlog. Today 'itd 139 · iss 332' counts every intent not yet shipped (drafts plus planned) and every open issue (internal/core/statusline/compose.go:139-160), which the product thinker said is not the number they care about. They want planned intents ready to build, and issues that need no design decision. Both exist already: the board's Now/Next block runs the readiness gate over planned intents (Next: 15 READY at main 22492dbf4, plus the Now rows), and 'abcd drain --dry-run' classifies open issues (64 eligible, 264 handed back, 4 without a remedy). Measured on this machine, the board took 4.9s and the drain dry run 0.55s; the status line's own work stops at 500ms, so neither can be computed on every refresh.