fix

# Fix Use the same durable workflow as feature work. Diagnose the defect first. Then reconcile specifications and create the fix plan and work orders before you change production code. ## Core flow ```text Evidence -> Root cause -> Requirement conformance -> System-design check -> Fix plan + work orders -> Handoff -> Explicit implementation request -> TDD -> PR review ``` Do not patch production code before the planning checkpoint unless the user explicitly opts out. ## Phase 0: Evidence and root cause When a bug comes from an issue tracker, read the canonical issue and each image attachment. Reproduce the behavior with existing tests, a read-only trace, or a minimal temporary reproduction. State: - The incorrect behavior and its conditions. - The root cause. - The smallest reliable reproduction. - The intended regression-test level and path. If the cause remains uncertain, stop and ask the user. ## Phase 1: Reconcile specifications Run the `/interview-me` assumption check for intended behavior and repair scope. Reuse active acceptance criteria for clear regressions. Ask only about material choices that evidence and prior instructions do not settle. Read `docs/specs/README.md`, the owning system index, and the relevant requirement and system-design documents. Use the legacy catalog only when the system has not migrated. Read the owning system `README.md` and use this command for discovery: python3 scripts/list-docs.py specs --format paths Add `--kind legacy`...