ripwire-find-bug

# Find the bug with ripwire > Nearest neighbours: > • You already know the symbol and just want to understand it → **ripwire-navigate**. > • You want the blast radius / tests for a *change* (not to find a bug) → **ripwire-change-check**. > • Repo-wide quality once-over, no specific symptom → **ripwire-fresh-eyes**. > • "Why don't I see feature X?" and nothing looks broken — the code may be built but compiled/flagged OFF, > not buggy: `ripwire <dir> --flags[=SUBSTR]` (`--flip=NAME` for the blast radius of turning one ON) — > lives in **ripwire-fresh-eyes**, worth a look before you go hunting for a bug that isn't one. `<dir>` = repo root. Calls are warm after the first parse — chain freely. **Pick the branch that matches what you already know**; each converges on the same evidence trail (relevance × maintenance pain × blast radius), so you can escalate between them. **Evidence-sufficiency stop:** escalate only while the responsible code is still ambiguous. If `--for` ranks one file/symbol clearly and a focused source read explains the symptom with a minimal fix, stop retrieval and implement/validate it. Do not automatically add `--hotspots`, `--impact`, another skill, or a whole-file read after the defect is already proven; those answer different questions and can cost more than the original localization. Resume the ladder only when the source contradicts the candidate, several candidates remain plausible, or the change's blast radius is itself part of the task. ## Bran...