I review agent patches as an auditor, not a reader. A reader asks whether the code is readable. An auditor asks what the patch promised and how a violation would be noticed. This gate is three small pieces long: property checks, fixture locks, and a flaky freeze. Run the pieces in that order. If any piece fails, the diff goes back to the agent before a human spends a minute on it.
A green test suite is a report about examples. A property check is a report about a law. When the law holds, the diff can be ugly in a hundred small ways and the important structure still stands.
Why example tests are not enough
Example tests are written for the code that exists. That makes them exactly the wrong oracle for a patch written by an agent that tried to change that code. The test says "two records merge into two" and the agent writes a merge that drops the third record because the test never created a third record. The suite stays green. The product breaks.
Property checks do not care about the current shape of the function. They care about what is always true. That is the property a reviewer actually needs.
