Bug Fix

You have identified a bug in your system and want Blitzy to autonomously diagnose and fix it. This template will help you provide the detailed problem statement and context needed for effective bug resolution.

**PROBLEM STATEMENT**

- **What specific bug or issue are you experiencing?** *Describe the exact problem, error, or unexpected behavior you've observed.*
- **When does this bug occur?** *Detail the specific conditions, user actions, or system states that trigger the issue.*
- **What is the expected vs. actual behavior?** *Clearly contrast what should happen with what is actually happening.*
- **How frequently does this bug occur?** *Is it consistent, intermittent, or only under specific conditions?*

**BUG REPRODUCTION & EVIDENCE**

- **What error messages, logs, or stack traces are associated with this bug?** *Include any diagnostic information, error codes, or system outputs.*
- **Which specific files, functions, or components do you suspect are involved?** *Identify any areas of the codebase where you believe the bug might originate.*
- **Are there specific input parameters, request payloads, or data formats that cause the failure?** *Include example JSON, XML, form data, or API request bodies.*
- **Are there any recent changes that might have introduced this bug?** *List recent commits, deployments, or configuration changes that could be related.*

**SYSTEM BOUNDARIES**

- **What boundaries should we set for Blitzy during this bug fix?** *Define the limits within which Blitzy should operate (e.g., "only modify files in the /src/payment directory" or "limit changes to the authentication module only").*
- **What functionality must remain completely untouched during the bug fix?** *Identify critical features, workflows, and capabilities that must continue working exactly as they do today.*
- **What existing interfaces, APIs, or contracts must remain unchanged?** *List any external or internal interfaces that cannot be modified during bug resolution.*
- **Are there specific areas of the codebase that should be avoided?** *Identify any sensitive, legacy, or high-risk components that should not be modified unless absolutely necessary.*