reticle hunt is arithmetic, not driving. You point it at a directory of crawl reports (one JSON file per checkout, each produced by reticle_crawl) and it turns the pile into the one number the core claim needs: across N already-merged, already-green changes, how many carried a candidate false green?
Arguments
Each input file is read for
label (falling back to the filename), anomalies[], and stepsRun.
What it prints
Onereticle_hunt line with the summary:
Exit codes
Always0. A read failure is logged as reticle_hunt_failed. Omitting the directory is a usage error:
1.