autolisted

Outcome to produce: the durable Full-Auto controller (`docs/FULL-AUTO.md`) either begins a fresh run or resumes an existing one, and the user sees plainly what it just did and what happens next. Enter the Full-Auto flow. This is a different, more advanced layer than the guided start (`/brothermode:start`): it requires a signed authorisation (the autonomy contract, `docs/AUTONOMY.md`) before any run can begin, and it drives real work through a resumable loop rather than a single conversation. FIRST, check for a live contract by running `python3 tools/bm_autonomy.py show --project <id>`. If none exists, the user has not authorised autonomous work yet: explain in plain language what signing means (the outcome, how done is defined, which folders and actions are allowed, an optional token and minute budget, and that credential entry, payments, account sign-in, permanent deletion, and publishing can never be granted, ever), gather the answers, and run `python3 tools/bm_autonomy.py sign` yourself with the gathered details. Never invent an outcome or a done definition the user did not actually state. ONCE a live contract exists, run `python3 tools/bm_controller.py start --project <id> --outcome "<the same outcome>" --done-definition "<the same done definition>" --controller-id <a stable id for this session> --actor-name <the user's name>`. Read its output rather than answering from memory of this conversation about what state the run is in: - If it reports a fresh run in state `N