Duplicate script files with same name caused two AI agents to contradict each other accurately

Two AI coding assistants reviewing the same project reached opposite conclusions about whether a render script contained a safety guard — and both were correct. One agent had edited and tested a guarded version of the file, while the other independently opened an older, unguarded copy with the identical filename sitting in a different directory. The render pipeline's actual call path used the guarded copy, so no immediate harm occurred, but the dormant duplicate posed a silent risk to any future process resolving the file from a different working directory. The contradiction was only caught because the second agent independently verified the claim rather than deferring to the first. The recommended fix was to rename the obsolete file with a clear marker and adopt a policy requiring any claim about a file's contents to cite its exact path and a reproducible, verifiable command.