fixlisted

# fix Run a direct diagnose → patch → verify loop. ## Workflow 1. Capture the symptom and reproduction. Use `scout --diagnose` only when the cause, recent delta, or blast radius is unclear. 2. Form and test a root-cause hypothesis; make the smallest repair that fixes the cause rather than only the symptom. 3. Run focused verification and inspect the diff. Request independent review only for security, data, migration, public-contract, production-incident, or explicitly requested work. Handle `APPROVE`, `REQUEST CHANGES`, or `BLOCK` before claiming completion. 4. Write `fixed.md`: use the active work item when one exists; otherwise create `plans/YYMMDD-fix-{slug}/fixed.md`. Record symptom, root cause, changed files, verification, any prevention guard, review verdict when present, and residual risk. This is the only fix artifact. Stop and ask for direction after repeated failed hypotheses or when the repair would change an accepted design. Do not create a fix directory tree, duplicate evidence, auto-commit, or automatically invoke ship.