review-roundlisted

# Working a review round **Both review bots comment per commit**, and a round of findings can land *after* a reply to the previous round. Before calling a review done, re-check with the head SHA: `gh api --paginate repos/<owner>/<repo>/pulls/<n>/comments --jq '.[] | select(.original_commit_id=="<sha>")'` — with `--paginate`, since a busy PR's comments span pages and the first page is exactly where the older rounds are. **But no findings at the head does not mean the head was reviewed, and neither endpoint above says which it is.** Comments are findings; `pulls/<n>/reviews` lists only the reviews that *carried* one — so a clean head and an unreviewed head look identical from both, and on #349 that read as "Codex never reviewed the final commit" when it had, eight minutes before the merge. **Codex says so itself, in two places:** - **Its summary comment**, one per PR and updated in place, marked `<!-- codex-pull-request-review-summary -->`. It is an *issue* comment, not a review comment, and carries a table whose `Commit` column is the SHA of the latest review and whose `Status` says whether it finished: ```console gh api --paginate repos/<owner>/<repo>/issues/<n>/comments \ --jq '.[] | select(.body | contains("codex-pull-request-review-summary")) | .body' ``` - **A reaction on the PR**: 👀 while a review is running, **👍 once every review has finished with no findings** — which is the signal that a round is genuinely closed rather than pending. ```consol