Conclusion first: a patch gate is only as trustworthy as the working tree it inspects. When two jobs share one directory, the gate can validate a tree that no single job produced, and still report green.
The scenario below is an illustrative drill, not a report of a real incident. It is written for teams that gate AI-generated patches before they touch main. No measurements or test outcomes are claimed here.
The failure shape (illustrative)
Two patch jobs run against the same checkout on one host. Job A edits src/a.py and starts a slow test. Job B edits src/b.py in the same directory one second later. The gate then runs the full suite once, on one tree, and reports green.
No single patch caused that tree. Job A's tests exercised Job B's file.…