v0.2.0: buggo hunt

buggo hunt: blind correctness-risk triage

New command: buggo hunt --repo <path>. Unlike investigate, it needs no bug report at all — given just a repository, it ranks files by how likely they are to hide an undiscovered bug, using directory structure and a git-derived risk signal (historical fix-commit density, not just raw churn).

Validated before shipping: on 100 real BugsJS bugs, the actually-buggy file fell in the riskiest 10% of candidates 63% of the time by this signal alone (vs. ~10% expected by chance). Showing it to Jev instead of a naive directory-name-only guess raised blind file-level Top-5 triage from 10% to 60% on a 30-bug multi-project sample (McNemar p=0.0007).

Known, disclosed limitation: the signal favors large, frequently-touched "core" files over rarely-touched peripheral files that may still hide a bug. Two correction attempts (size-normalized density, minimum-churn threshold) were tried and measured to be no better — left as an open problem, documented in the README rather than papered over.

hunt stops at file-level triage, same as investigate's suspects — a starting point for you or a coding agent to actually investigate, reproduce, and fix. It does not discover, reproduce, or confirm a bug on its own.

Usage

buggo hunt --repo /path/to/your/repo
buggo hunt --repo /path/to/your/repo --format json

See the README's new "buggo hunt (v0, experimental)" section for the full validation numbers and the known bias.