Deliver Issues

Take the board's eligible tickets to pull requests while the operator is away. Each one goes through the same chain a single ticket gets, in dependency order, and the run ends with one message.

The Iron Law

EVERY TICKET GETS ITS OWN BUILD, REVIEW AND LANDING. A BOARD OF THEM IS NOT A REASON TO SKIP ONE.

Four baseline runs on a four-ticket board, ten approved tasks, without this skill: all four wrote every task in the controller. Across the four there were 0 implementer or reviewer dispatches, 0 inspect-change and 0 land-branch, and one run loaded no skill at all. A haiku run explained: "I built the formatting work inline, test-first, rather than through the execute skills, since the tasks were small." Six PRs went up that nobody but their author had read. The operator reviews tonight on the strength of a review that never ran.