bts-recipe-fixlisted

# Recipe: Fix Fix a bug through document-first diagnosis and verified implementation: $ARGUMENTS ## Context Briefing Before starting, build situational awareness: 1. List `.bts/specs/recipes/` → find related recipes (especially completed ones) 2. Set `ref_recipe` in recipe.json to the most relevant recipe ID 3. For each related recipe, read its final.md → understand design intent 4. Check deviation.md → known issues that may be relevant 5. Check review.md from related recipes → known quality/security issues 6. Scan codebase for files mentioned in the bug report ## Resume Check ```bash bts recipe status ``` If active fix recipe found, read diagnosis.md and fix-spec.md to resume. **Autonomous execution**: This recipe runs without stopping between steps. Do NOT pause to summarize or ask the user. Only stop for [CONVERGENCE FAILED] or when experts disagree on root cause (user decision needed). If no active recipe, create one: ```bash bts recipe create --type fix --topic "$ARGUMENTS" ``` Use the output as recipe ID for all subsequent commands. ## Step 1: Diagnose Investigate the bug and create `.bts/specs/recipes/{id}/diagnosis.md`: ```markdown # Diagnosis: {bug description} ## Symptom [What the user observed — exact error, unexpected behavior] ## Reproduction [Steps to reproduce the bug] ## Root Cause [Code location, logic error, why it happens] [Include file path, function name, line context] ## Affected Files - [file 1]: [how it's involved] - [file 2]: [how it's i