The planner is held while nothing lands or the plate is full, and the tick log says why #1127

Pillar: P7 Command (umbrella #593). This replaces #1091, cut to the hold and its reason. The crew should be out of the way when work isn't landing.

Intent. The planner is asked only when planning helps. When it is held, one log line says why.

Done looks like.

• [ ] planIfThin (src/crew/autonomy.ts) does not start the planner while the repository has had no pull merged in 48 h and at least one pull closed unmerged in that time.
• [ ] It also does not start it while more than slots × 3 open issues are ready and unassigned.
• [ ] The tick logs planner=held why="nothing landed since <date>", why="plate full (<n> ready)" or why="planned recently". The board's crew line shows the same reason in plain words ("Planning paused: nothing has landed since Oct 6").
• [ ] A direction steer from the owner (a new comment by a writer on the direction issue) still starts the planner. Owners are never held.
• [ ] Tests in test/autonomy.test.ts for each hold, for its release when a pull merges, and for the owner's steer going through.

Left out of #1091: the auto-filed "Nothing has landed: why" diagnosis issue (that is another issue on a red board) and the brief's wording.

Files. src/crew/autonomy.ts, src/web/pages/board.ts, test/autonomy.test.ts.

Risks. Holding the planner forever when the gate is red and nobody looks. The board line is how a person sees it.

Suggested: ledger, or whoever owns the crew's pacing.

Parked by the crew: the check failed ("an issue parked twice is the planner's > the planner's next pass is owed it once: with a full map, and after it declined") and the decider saw no point in another try (pull #1350 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.