/sumo-status, project status report

Give a fast, honest snapshot. No fluff.

Steps

1. Read .claude/PROJECT_NOTES.md. The phase tracker and "Next actions" section are the source of truth.
2. Read the last entry in docs/BUILD_LOG.md for what actually happened most recently.
3. Cross-check reality against the notes:
   • Has the board been collected? The 2026-08-15 deadline is the nearest hard date.
   • Does cad/ contain real Fusion files yet, or just the README?
   • Does firmware/ contain a real PlatformIO project (platformio.ini, src/), or just the README?
   • Does docs/BOM.md have real parts and prices, or is it still the template?
   • Any uncommitted git changes worth mentioning?
4. If the notes and reality disagree, say so explicitly. Stale notes mislead the next session.
5. 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.

Output format

## Phase: <N, name> (<status>)

**Done recently:** <1-3 bullets>
**In flight:** <what's actually being worked on>
**Blocked on:** <anything waiting, such as parts or machining access, or "nothing">

## Next action (do this literally next)
<one concrete step>

Rules

• One next action, not five. The plan lists everything; this skill picks the next thing.
• Respect phase discipline. Never suggest a Phase N+1 task while Phase N lacks its deliverable.
• Phase 0 (event, class and division confirmation) closed on 2026-08-09, and the rulebook is confirmed. Nothing is waiting on information, so a "blocked on the organizer" answer is now wrong. If something is blocked, it's parts, machining access, or the board collection.
• Never report a rule or event detail as confirmed when docs/RULES.md marks it (assumed).
• If the phase tracker says a phase is done but the deliverable doesn't exist on disk, the phase is not done. Say so.