fixlisted

# Fix Systematic bug fixing: reproduce the problem, find the root cause, apply a minimal fix with a regression test. ## Available skills and subagents - **`/tdd`** — Use for implementing the fix with a regression test (Red-Green-Refactor). - **`/e2e`** — Use when the bug is in a user-facing flow and needs a Playwright regression test. - **`/verify`** — Run after fixing to ensure nothing else broke. - **`/record`** — Record architectural decisions or insights discovered during the fix. ## What a fix produces (and what it doesn't) The artifacts for a bug fix are: - A regression test that fails before the fix and passes after. - The minimal code change. - A clear commit message capturing the root cause. - **An ADR (via `/record decision`) IF the fix encoded a new project-wide convention** (e.g., "GC code must fail-closed", "all repo deletes must be transactional"). Most fixes don't need one. - **An update to the related feature spec IF the bug exposed a requirement gap** (see Phase 5). A bug fix does **not** produce a spec. Specs describe product features; bugs are corrections to existing features and are tracked in tests + commits. --- ## Before anything else: create the pipeline Create these tasks immediately (use your task/todo tracking tool if available): 1. **Reproduce the bug** — Write a test or find a reliable reproduction case 2. **Find the root cause** — Trace the code path, narrow the scope, state the cause clearly 3. **Fix with TDD** — Minimal fix with regre