The queue drains itself now, and the morning note fits in a minute

Description and use

The code queue now self‑drains, reducing manual routing and producing concise, actionable daily reports that fit in a minute.

Problem

Managing a shared task queue for multiple repos was manual and time‑consuming, with the author routing work and tracking progress by hand.

Outcome

Queue self‑drains, reducing manual routing by 48 commits per day. Morning reports shrink from 4.6 KB to 680 characters, fit in a minute, and are actionable. 54 entries parked as needing attention, 29 repeat classes resolved automatically.

Workflow

• 1. Detection files its own work by sweeping repos nightly and adding findings to the queue via an atomic door.
• 2. The queue converges on state: entries that remain fruitless for three nights are parked as needing human attention.
• 3. A concise morning report is generated from a JSON‑lines trace, summarizing fixed, handled, needs you, and still stuck items.
• 4. Direct messaging is used when a session has a live target, bypassing the queue for immediate resolution.

Evidence

The queue drains itself now, in four moves.

Source

The morning report is a PA's note. Every report I used to get was accurate and none was ever actionable: fifteen lines of "Started work" in time order, the same errors again and again.

Source

The brief is compiled from the run's one fact stream, a JSON-lines trace every producer writes into, so there is one account of the night rather than three reconciled by nobody.

Source