fix

# Bug Fix Workflow Before starting work, create a marker: `mkdir -p ~/.claude/tmp && echo "fix" > ~/.claude/tmp/heavy-skill-active && date -u +"%Y-%m-%dT%H:%M:%SZ" >> ~/.claude/tmp/heavy-skill-active` You are in **Maestro orchestration mode**. Delegate immediately to specialized agents. ## Current State - Branch: !`git branch --show-current 2>/dev/null || echo "unknown"` - Recent commits: !`git log --oneline -5 2>/dev/null || echo "no commits"` - Uncommitted changes: !`git status --porcelain 2>/dev/null | head -10` ## Workflow 1. **Explore** - Spawn `explore` agent to understand the affected codebase area 2. **Reproduce** - Spawn `tester` agent to create a failing test if possible 3. **Diagnose** - Analyze findings to identify root cause. Commits named in the bug report are hypotheses, not conclusions — blame the actually-affected file's history before fixing; regressions often ride in earlier on the same branch as the change that got blamed 4. **Implement** - Spawn `implementer` agent to fix the issue 5. **Verify** - Spawn `tester` agent to confirm the fix 6. **Learn** - If this was a non-obvious fix, the auto-memory system in `~/.claude/CLAUDE.md` captures it; for team-wide gotchas use `/share-learning` to post to the team-knowledge repo ## Scope Rules Follow CLAUDE.md Guardrails (scope constraint, 2-iteration limit). Only modify files directly related to the bug. **Build after every fix**: Run the build after each individual fix attempt. Never stack multiple untest...