auto-devlisted

# auto-dev — a continuous fleet that implements and merges issues ## What this does `implement-issue` makes one planned issue into a ready PR; `merge-pr` lands one PR. **auto-dev supervises them at scale**: N background workers each own one issue end-to-end (`implement-issue <N>` → `merge-pr <PR>`); the moment a worker's PR merges it's retired and a fresh worker is dispatched onto the next queued issue — so N issues stay in flight without you babysitting. The value is the orchestration a naive "run them in a loop" lacks: - **Conflict avoidance** — each concurrent worker gets an issue in a *different* code area, so branches rarely collide. - **Ordering** — small self-contained issues first (fast wins, fewer conflicts), then medium. L/XL and manual-QA excluded by default. - **Mandatory merge** — workers love to stop at "PR ready" (half a job). auto-dev verifies the *real* merge state from GitHub on every signal and re-drives any worker that stalled. - **Off-scope capture** — a worker that trips over an unrelated bug fixes it inline only under `implement-issue`'s carve-out (local to a file its PR already modifies *and* small, in its own commit) and otherwise files it via `create-issue` rather than dropping it, against the shared filing bar ([`../_shared/filing-bar.md`](../_shared/filing-bar.md)) so a fleet of N workers doesn't file at N different standards. The backlog stays truthful *and* drainable (#410). - **Lifecycle hygiene** — finished agents are shut down; a state fil