Second self-review defect, again found by probing rather than reading.
`GET /commits/{sha}/status` PAGES, and it pages undetectably: measured on Gitea 1.27.1
(2026-08-29), `?limit=2` against a head carrying 15 contexts returned 2 rows AND
`total_count: 2`. The count reports the PAGE, not the total, so no field in the body
distinguishes a truncated response from a complete one. A head whose context count grew
past the server's default page size would silently stop containing the `review-verdict/h10`
row, and the read-back would refuse a verdict that is actually in force — the deadlock
direction, on the one path that must not deadlock.
The call now asks for `?limit=100` against the ~15 contexts this repo produces.
The not-found refusal no longer states a cause. Two causes reach it — the status is gone,
or the list was truncated — and the response cannot tell them apart, so asserting either
would be the #859 defect: a message that sends the reader hunting something that did not
happen. It now reports how many rows it actually read and names neither, which also makes a
future paging overflow legible instead of mysterious.
Recorded in `docs/remote-state-inventory.md` on the writer's own row, since it is a property
of that read rather than of the tool.
fixes#845
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019zUmJZHhVP7kXg5DV237TW
timothyandClaude Opus 5
785edbe6e6