How can a review benchmark test stale-state handling?

A supplier-control reviewer opens review REV-0823 and reads supplier record SUP-0467 at version 12. The payment verification is complete, and the review appears ready for closure.

While the reviewer prepares the decision, an accounts administrator updates the supplier's payment details. The supplier record becomes version 13, and the verification state changes to pending. The review policy requires current payment details to be verified before closure.

The reviewer attempts to close the review using version 12. The environment rejects the transition with a stale-state response. A successful agent retrieves the changed record, recognises the verification requirement and leaves the review awaiting verification. Repeating the old request or bypassing the version check would be a failure.

A generated environment could schedule this mutation at a defined action boundary. Evaluation hooks can inspect whether the agent refreshes the material evidence and revises its decision. The case teaches teams to test commitment-time validity: reasoning can be correct when performed and still become unsuitable for action after the underlying business state changes.