bughunt

# Bug Hunt Conduct an exhaustive bug hunt on this Git repository, enhanced by Draft context when available. ## Primary Deliverable **The bug report is the primary deliverable.** Every verified bug MUST appear in the final report regardless of whether a regression test can be written. Regression tests are a supplementary output — helpful when possible, but never a filter for bug inclusion. ## Relationship to Built-in Bug Hunt Agents Some AI tools (e.g., Claude Code) provide a built-in `bughunt` agent that auto-discovers project structure and runs parallel sweeps. `/draft:bughunt` is **complementary, not competing**: | | `/draft:bughunt` | Built-in bughunt agent | |---|---|---| | **Approach** | Context-driven methodology with 14 analysis dimensions and verification protocol | Auto-discovery with parallel sweep subagents | | **Draft context** | Uses architecture, tech-stack, product, guardrails for false-positive elimination | No Draft context awareness | | **Output** | Severity-ranked report with evidence | Inline fixes + regression tests | | **Modifies code** | No (report + regression tests only) | Yes (finds AND fixes) | **When to use which:** Use `/draft:bughunt` when you need context-aware analysis with structured evidence and false-positive elimination. Use the built-in agent when you want fast parallel sweeps with auto-fix capability. For maximum coverage, run both — `/draft:bughunt` catches context-specific bugs the built-in misses, and vice versa. ## Red Flags -...