A finding you can't reproduce is a rumor. Replay re-executes a behavior inside the exact environment captured when it was observed, then proves the result is stable by running it twice.

how it works

Every observation records the full environment variable map. Replay spawns your command as a child process with a cleared environment containing only the recorded variables. No process-global mutation, no unsafe code: the pin lives entirely in the child. The command runs twice & the outputs are compared byte for byte.

pinned world: code=e71d4265756eefdd env=7b2ae6a286cd9586 (64 vars)
repro deterministic: yes

the verdict

yes means the behavior is a property of the recorded world. no means something outside the recording participates: wall clock, network, ports, randomness. The divergence byte offset is printed so you can see how deep the instability runs. A non-deterministic finding isn't discarded, but it's labeled, because a flaky reproduction can't anchor a blame.

limits

The pin covers environment variables, the working directory & the command. It doesn't cover filesystem state outside the repository, containers, or system state. Honest ceilings for a single 2mib binary.