BDD Issue Fixer

Hard Rules

These are non-negotiable. Violating any of these means the work is wrong.

1. Never weaken a test. When a test fails, the CODE is wrong. Fix the code, not the test. Never skip, mock, or reduce assertion precision.

2. Test behavior, not implementation. The Gherkin scenario captures what the user expects. Write declarative scenarios from the user's perspective, never imperative UI scripts.

3. Iterate until fixed. Try up to 5 different fix strategies. If approach 1 fails, analyze why and try approach 2. Never give up after one attempt. Escalate only after 5 genuine attempts.