Next up says why a ready issue is not started (#8924)
- A lift places the issue. Taking an issue from behind the Later gate (the Lift button, the
wait_fortool withstop, the pacer's release) leaves it under a pillar: the one it already serves, else the first, whose umbrella then waits for it. The one place isstopWaiting(src/actions/gate.ts), whichliftHoldandwait_forstop share, viaservePillar(src/core/pillar_pick.ts), so neither route skips it; taking theLaterlabel off by hand is not a lift, for the label puts the gate back. - No silent case. Every ready issue a builder will not start carries one reason on Next up (web, terminal, MCP
next_upaswhy): whatheld.tsholds (a run, a pull, a cap, a hot file, a stall), or what the picker passes over (src/crew/pick_filter.ts):polish_share,no_bet,no_builder. The tick line counts the passes. - Not explained, because they need git: issues retired as already done on the base are closed with a note on the tick, not listed.
notStartable (src/crew/not_startable.ts) joins the two; the page reads the scope once. Tested in test/not-startable.test.ts and test/lift-startable.test.ts.