neutralizelisted

# Fix Issue Find the root cause, not just the symptom. Apply the smallest safe fix, then scan nearby code for the same mistake pattern. ## Scope Gate Use this workflow when at least one is true: - root cause is unknown or spans multiple components - the defect recurs or suggests a repeated mistake pattern - build/runtime evidence, logs, stack traces, or screenshots must be reconciled - the fix needs an auditable reproduction/rerun record For a small, obvious local correction, fix and validate directly. Do not create `.agent-state/neutralize-gate.json` merely because the user used the word "fix". ## Workflow 1. Extract evidence: exception type, file paths, line numbers, error text. For screenshots, read visible error text and identifiers first. 2. Define the observable target: current failure evidence, expected result, and fastest rerun command. Reproduce if practical; otherwise record why reproduction is unavailable. 3. Identify root cause. 4. Apply the minimum safe correction as one verifiable slice. 5. Verify the exact symptom first, then the smallest relevant regression scope. 6. Search adjacent files and similar call sites for the same error shape. 7. If a public interface changed, record whether it expanded, stayed stable, or shrank and what complexity remains hidden behind it. 8. Write gate evidence file — `failure_observation`, `reproduction_command` or `reproduction_skipped_reason`, `rerun_command`, `rerun_exit_code`, `adjacent_searches`, `adjacent_findings`