I've built an orchestrator that solves some of the issues you ran into (although it doesn't do anything about cheating): https://navels.dev/blog/neal/. Features:

- lets you configure different models for planner, coder, and reviewer roles. (e.g., using Claude as an adversarial reviewer against Codex)

- breaks your plan up into reasonable-sized chunks of work with clearly defined success criteria

- runs each chunk of work through a coder / read-only reviewer loop. Once both agents are satisfied, neal moves on to the next chunk. Once everything is complete there is a final pass through the coder / reviewer loop to ensure the implementation satisfies the entire plan.

- resets the coder's context with each chunk of work to prevent context drift, leaving the reviewer's context long-running.

Wow, "neal" looks excellent. Good on you for creating and sharing it, and for the awesome blog post.