bug-killerlisted

# Bug Killer -- Hypothesis-Driven Debugging Workflow Execute a systematic debugging workflow that enforces investigation before fixes. Every bug gets a hypothesis journal, evidence gathering, and root cause confirmation before any code changes. ## Phase Overview 1. **Triage & Reproduction** -- Understand, reproduce, route to quick or deep track 2. **Investigation** -- Gather evidence with language-specific techniques 3. **Root Cause Analysis** -- Confirm root cause through hypothesis testing 4. **Fix & Verify** -- Fix with proof, regression test, quality check 5. **Wrap-up & Report** -- Document trail, capture learnings --- ## Phase 1: Triage & Reproduction **Goal:** Understand the bug, reproduce it, and decide the investigation track. ### 1.1 Parse Context Extract from `$ARGUMENTS` and conversation context: - **Bug description**: What's failing? Error messages, symptoms - **Reproduction steps**: How to trigger the bug (test command, user action, etc.) - **Environment**: Language, framework, test runner, relevant config - **Prior attempts**: Has the user already tried fixes? What didn't work? - **Deep flag**: If `--deep` is present, skip triage and go directly to deep track (jump to Phase 2 deep track) ### 1.2 Reproduce the Bug Attempt to reproduce before investigating: 1. If a failing test was mentioned, run it: ```bash # Run the specific test to confirm the failure <test-runner> <test-file>::<test-name> ``` 2. If an error was described, find and trigg