A stalled issue frees itself: a builder that left it without a pull lets it go after one tick, and a twice-stalled issue goes to the planner with the reason - no person needed #4073

Probe 2026-10-21 07:35Z, trevato/arm: the crew idles repeatedly with held="stalled=N" (a builder left the issue assigned without a pull, src/crew/held.ts) and nothing else startable; only the planner releases stalled (REPLANNABLE), the planner hits its day's cap, and the steward has had to unassign issues by hand three times today (#243 twice, #256, #258, #317, #403).

Done: (1) a stalled issue is unassigned automatically on the next tick (keeping a note of who stalled it and why, from the run's last summary), so any builder can pick it; (2) an issue stalled twice goes to the planner with that reason even past the day's planning cap (unsticking is not planning); (3) a builder never re-picks an issue it stalled within the hour; (4) the tick line counts unstuck=N. Test: a builder run ends without a pull → next tick the issue is ready and another builder picks it; second stall → planner asked despite the cap.

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.