bugfixlisted

# /bugfix Structured bug-fix flow. Lighter than `/proceed` — focused on reproducing, finding root cause, fixing, and preventing recurrence. ## When to use - A bug is reported with a clear-enough description - Production incident triage (with appropriate care) ## Workflow 1. **Phase 1 — Load context.** Read the active feature's `findings.md` (prior research and resolved decisions), existing related bug reports, and recent commits to the affected area. 2. **Phase 2 — Capture the bug.** If a bug report doesn't exist, create one in `docs/bugs/<short-slug>.md` from the bug-report template: - Steps to reproduce (numbered) - Expected vs actual - Environment - Frequency / impact 3. **Phase 3 — Reproduce.** Confirm the bug locally. If you can't reproduce, ask for more info — don't guess. 4. **Phase 4 — Find root cause.** Don't stop at the symptom. Five whys. - Document the cause in the bug report. 5. **Phase 5 — Decide fix scope.** Minimum viable fix vs deeper refactor — note the tradeoff. For now, fix the specific bug; file follow-up if refactor is warranted. 6. **Phase 6 — Write a regression test** that fails without the fix and passes with it. (If you can't write a test, document why.) 7. **Phase 7 — Apply the fix.** 8. **Phase 8 — Run tooling.** Lint, typecheck, tests. 9. **Phase 9 — Update the bug report** with root cause, fix, tests, lessons. Set the report's status to `fixed` (or `closed`) so the registry reflects reality.