The orchestrator shut down over a state that clears itself
A lock on a branch whose task could not be found ended the whole daemon, when skipping one tick would have done.
What I did
The orchestrator stopped shutting itself down when it cannot find the task behind a locked branch; that state clears on its own, so skipping one tick is enough.
Had three cheap guard workflows merged into one billed job, because I was running out of free GitHub Actions minutes.
Measured the factory’s throughput: 32 unique tasks reached a pull request in 24 hours, 52 in 48.
What the factory did
Split a task that contradicted itself — “empty the whole colour allowlist” against “one screen per pull request” — into four that can be claimed, and split them along 550 measured violations rather than by file count.