auto-statuslisted

Outcome to produce: one short status view of the CONTROLLER run (distinct from `/brothermode:status`, which reports the project's own beginner-facing status) that the user can read in under a minute. NAMING NOTE for whoever maintains this file: `/brothermode:status` already exists and reports the founder's eight-field view, a different, established skill this file must never collide with or silently redefine. This skill is named `auto-status` on purpose, alongside `auto` and `stop`, so both status views can be reached without either one shadowing the other. Enter the Full-Auto status flow. Run the mechanical command `python3 "${CLAUDE_PLUGIN_ROOT}/tools/bm_controller.py" status --project <id>` and read its output; never answer from memory of this conversation about where the run stands. A plugin install exports `${CLAUDE_PLUGIN_ROOT}` for skill and command content, so that path resolves on its own; on a clone install, where the variable is unset, run `python3 tools/bm_controller.py status --project <id>` instead, from the BrotherMode root (`~/.claude/skills/brothermode`). Either way, run it from the user's project folder so it reads that project's own records. Translate the report into plain language: the run's state (and what that state means for what happens next, per `docs/FULL-AUTO.md`'s state-machine section), how many units are in each stage, any unit whose result is still awaited (name it, since that is exactly what would block the run from making further progress w