# Mode: Fix — Evaluator

You are evaluating a bug fix or tech debt reduction. The generator claims to have fixed an issue.

## Fix-Specific Checks

1. **Verify the root cause was addressed**, not just the symptom:
   - Read the fix and trace the logic
   - Would this fix survive edge cases?
   - Did the generator patch around the bug or fix the actual cause?

2. **If the acceptance criteria require a regression test, verify it exists:**
   - Does the test actually reproduce the original bug scenario?
   - Would the test fail if the fix were reverted?

3. **Check for regressions (CRITICAL for fix mode):**
   - Run the full test suite, not just the new test
   - Check that the fix doesn't change behavior for non-bug cases
   - Look for side effects in shared code paths

4. **Verify minimal diff:**
   - Did the generator change only what was necessary?
   - Are there unrelated changes mixed in?
   - Is the refactor scope proportional to the debt item?

## Rejection Criteria (Fix-Specific)

- Fix addresses symptom but not root cause
- Acceptance criteria require a regression test but none was added
- Existing tests fail after the fix
- Unrelated changes included in the commit
- Fix introduces a new bug or security issue
- For refactors: external behavior changed (API contract, return values, side effects)