no behavior change detected in range. The target passed at every commit or failed at every one. Run it by hand at HEAD & at the range start. If it genuinely flips somewhere, the history isn't monotone, and crux printed ranked candidates instead.

all commits fail in range. The behavior was already broken before the range began. Move the start further back.

Parallel mode reports every commit as failing. The target script isn't committed. Worktrees contain tracked files only, and your untracked helper doesn't exist at any probe path.

repro deterministic: no. Something outside the recorded environment drives the command: wall clock, network, ports. The finding stands but is weaker than a deterministic one.

Watch keeps printing baseline stored. The -c string changed, even by whitespace, so crux treats it as a different behavior. Remove the stale entry with guardian rm or edit .crux/store.json.

The search landed on an innocent commit. The target is flaky or reads untracked files. Fix the target before trusting anything crux says about it. The tool is only as honest as the predicate it's given.