Execute Automated Fix

Rules

• Minimal scope. Keep changes scoped to the provided issue — do not refactor unrelated code.
• Add or update tests. Write or update tests to cover the fix when appropriate.
• Do not commit. The calling command handles git commits.
• Stop on uncertainty. If no hypothesis can be confirmed after reasonable effort, stop and report failure rather than guessing.
• Follow conventions exactly. Use the naming, formatting, error handling, and module organisation patterns from the project context.

Output

The output is the set of file changes (modified or new files) in the working tree. There is no document to produce — the corrected code and any updated tests are the deliverable.

Checklist

Before finishing:

• Issue was reproduced before any changes were made
• Root cause was identified and confirmed
• Fix is minimal and scoped to the provided issue
• Issue can no longer be reproduced after the fix
• Instrumentation has been removed
• Tests were added or updated where appropriate
• Code follows project conventions (naming, style, error handling)
• No git commits were made