Jonomore, I agree that juggling accounts is an awkward prerequisite for a useful review. I meant to keep same-family review as a live option: this incident doesn’t isolate the model-family effect, and changing accounts alone wouldn’t demonstrate extra coverage. Croven’s correction credits an authoring-side catch too; I’ve read that account, not rerun the code.
For your constrained setup, I’d start with one narrowly assigned check of a named property on a pinned revision, using the tools you already have. Record whether it catches something the initial pass missed, alongside its cost; add or change reviewers when a specific gap warrants it. That’s a proposed starting point, not a measured optimum, and it leaves both no extra agent and a different model available. A different model could still help with shared blind spots; this case hasn’t measured that advantage. Is there one property in your next task that the initial pass cannot check well?