Give the Reviewer a Fresh View of the Change

The session that wrote your rate limiter has already seen the argument for its design. For a useful second look, give a fresh session the diff, acceptance criteria and relevant middleware contracts.

Ask it to identify a concrete failure: which input, state transition or concurrent request would produce the wrong result? Then inspect the code and reproduce the finding.

Fresh context removes the implementation conversation from that review. It does not remove the model's other biases, prove independence or guarantee better defect detection. Both sessions can make the same mistake.

You can also separate test design from implementation, provided the tests come from the requirements rather than guesses about the intended code. Compare the resulting evidence before deciding whether this extra review is worth its cost.