Development record

The drain should start by itself whenever a runner with an API key and remaining credit is available, and pause by itself when that credit runs out, picking up again once the account is recharged. Today a run that hits an exhausted balance stops, and a person has to notice and restart it. The build loop already ends a window early on a rate-limit response and writes next_eligible_at, and its budget check asks each runner for its remaining quota, but nothing treats an exhausted balance as a pause that ends when credit returns, and nothing starts a drain when a funded key appears. Raised by the product thinker on 2026-10-28.