bts-recipe-debuglisted

# Recipe: Debug Debug through multi-perspective analysis: $ARGUMENTS ## Context Briefing Before starting: 1. List `.bts/specs/recipes/` → find related recipes (especially the one that built the affected code) 2. Set `ref_recipe` in recipe.json to the most relevant recipe ID 3. Read related recipe's final.md → original design intent 4. Check deviation.md → known spec-code differences 5. Check review.md from related recipes → quality issues that may be related 6. Scan codebase for files likely related to the symptom 7. If `.bts/specs/roadmap.md` exists, read it for project context (what's been built, what's planned — helps understand system boundaries) ## Resume Check ```bash bts recipe status ``` If active debug recipe found, read perspectives.md and draft.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 debug --topic "$ARGUMENTS" ``` Use the output as recipe ID for all subsequent commands. ## Step 1: Collect Perspectives Read `.bts/config/settings.yaml` for project-specific limits. Investigate the symptom from `debug.perspective_count` (default: 6) angles. Create `.bts/specs/recipes/{id}/perspectives.md`: ### 1.1 Data Flow Map Trace the complete path of the failing operation: - Request/input → processing steps → outp