Tasks:
- •Locate all files/modules affected by the issue. List paths and why each is implicated.
- •Explain the root cause(s): what changed, how it propagates to the failure, and any environmental factors.
- •Propose the minimal, safe fix. Include code-level steps, side effects, and tests to add/update.
- •Flag any missing or outdated documentation/configs/schemas that should be updated or added (especially if code appears outdated vs. current behavior). Specify exact docs/sections to create or amend.
Output format:
- •Affected files:
- •<path>: <reason>
- •Root cause:
- • <concise explanation>
- •Proposed fix:
- •<steps/patch outline>
- •Tests:
- •Documentation gaps:
- •<doc_section_what_to_update_add>
- •Open questions/assumptions:
- • <items>