erc-statuslisted

# /erc-status, project status report Give a fast, honest snapshot. No fluff. ## Steps 1. Read `.claude/PROJECT_NOTES.md`. The blockers and "Next actions" sections are the source of truth. 2. Read the last entry in `docs/BUILD_LOG.md` for what actually happened most recently. 3. **Compute days remaining to 2026-09-15** from today's date, and state it. This is a fixed external deadline and it should lead the report. 4. Cross-check reality against the notes: - Is registration confirmed yet? This is blocker 1 and it gates everything - Does a container build and does Gazebo render? This is blocker 2 and the critical path - Does `src/` contain a real ROS 2 package with `solution.launch.py`, or just the README? - Does `docs/verified-topics.txt` exist, meaning the day-one verification actually happened? - Does `results/trials.csv` have rows? Without it the report cannot be written - Does `erc_images/` have images from a real run? - Any uncommitted git changes worth mentioning? 5. If the notes and reality disagree, say so explicitly. Stale notes mislead the next session. 6. Check whether the vault is in sync, per `docs/VAULT_SYNC.md`. If the vault project note is older than the last build log entry, flag it. Note that the vault note may not exist yet. ## Output format ``` ## ERC-26: <days> days to Phase 1 (2026-09-15) **Build phase:** <N, name> (<status>) **Done recently:** <1-3 bullets> **In flight:** <what's actually being worked on> **Blocked on:** <regi