Event-driven dispatch: agent-ready label fires thrawn on this machine

Part of the factory trajectory in #16 and the consumer half of #25. Thrawn currently runs only when a human types a command; this makes it event-triggered without touching the gates. Branches appear and the board fills while the ship code still needs a human, so the factory gains an intake without losing its foreman.

Shape

• A trigger on this machine that reacts to an issue gaining the agent-ready label in a configured repo list and runs thrawn swarm <issue> --runner <configured> (or queues a planned dispatch for size M and up) in the right checkout
• Options to evaluate, simplest first: a self-hosted GitHub Actions runner on the Mac, a small poller (gh api on an interval, launchd or a herdr pane) or a webhook receiver; pick the one with the least standing infrastructure
• Concurrency guard: one active run per repo, queue the rest; never dispatch a run for an issue that already has an open thrawn branch or PR
• Notification when a run lands green or fails (the existing herdr toast path), so review attention is pulled rather than polled
• The kill switch matters: a single obvious way to pause all automatic dispatch

Constraints

• The ship gate is untouched: nothing merges without a human typing the code, swarm branches wait for review
• Dispatch failures must be loud and recorded (a comment on the issue), not silent
• Usage still lands in the ledger; automatic runs are phase 2 style data like any other

🤖 Generated with Claude Code

Start with the existing thrawn swarm <issue> --runner <configured> command and the gh api polling path described in the issue. Trace how herdr currently produces toast notifications and how automatic runs enter the usage ledger. Done means a selected trigger dispatches labeled issues safely, queues per repository, honors the kill switch, records failures, notifies on completion, and leaves the ship gate untouched.