cc-fixlisted

# Bug Fix Workflow Bug description: $ARGUMENTS Provide the following information in $ARGUMENTS: - What is the incorrect behavior (actual) - What is the expected behavior - Steps to reproduce - Environment or version where the bug occurs (if known) - Any relevant error messages or stack traces --- ## Step 1 — Task Card validation (task-coach) Invoke `task-coach` with the bug description above. task-coach must produce a Task Card that includes: - A clear statement of actual vs. expected behavior - Reproduction steps (or a note that they are unknown) - Risk classification: `low`, `medium`, or `high` - Scope: which files or modules are likely affected If reproduction steps are missing, task-coach must ask for them before classifying risk. A bug without a reproduction path cannot be classified reliably. **STOP here. Show the Task Card and wait for human confirmation.** --- ## Step 2 — Route by risk Read the risk field from the Task Card and follow the corresponding route. ### Low-risk route Applies when: the bug is isolated to a single component, existing tests cover the affected code, and no public API or shared state is involved. Route: `task-coach` → `tester` → `implementer` Proceed directly to Step 3a. ### Medium or high-risk route Applies when: the bug touches shared state, a public API, auth or payment paths, database writes, or the root cause is not yet understood. Route: `task-coach` → `architect` → `tester` → `implementer` → `reviewer` Invoke `archite