Enforce proof wording for pagination and live blocker claims #330

New Issue

2026-07-07T02:16:06-05:00

jcwalker3 commented

2026-07-07 02:16:06 -05:00

Problem

Reviewer reports have claimed inventory completion from default Gitea page-size assumptions and claimed "live proof" for blockers that were not actually revalidated in the current run.

Required behavior

Proof language must be tied to evidence from the current session.

Acceptance criteria

PR inventory completeness may not be proven by assuming the default Gitea API page size.
Pagination proof must include explicit final-page/no-next-page evidence, total-count evidence, or actual traversal until an empty/final page is returned.
If page-size/count proof is allowed, the requested page size must be explicit in the tool call and the response must prove the server honored it.
Reports may not claim "live blocker proof" unless the command/tool proving the blocker ran in the current session.
If relying on prior review feedback at unchanged head SHA, the report must say "prior blocker reused" or "prior request-changes still applies," not "live proof."
Final-report verifier should reject unsupported phrases like "inventory complete," "same as master," "live proof," and "file edits none" unless matching evidence is present.

## Problem Reviewer reports have claimed inventory completion from default Gitea page-size assumptions and claimed "live proof" for blockers that were not actually revalidated in the current run. ## Required behavior Proof language must be tied to evidence from the current session. ## Acceptance criteria - [ ] PR inventory completeness may not be proven by assuming the default Gitea API page size. - [ ] Pagination proof must include explicit final-page/no-next-page evidence, total-count evidence, or actual traversal until an empty/final page is returned. - [ ] If page-size/count proof is allowed, the requested page size must be explicit in the tool call and the response must prove the server honored it. - [ ] Reports may not claim "live blocker proof" unless the command/tool proving the blocker ran in the current session. - [ ] If relying on prior review feedback at unchanged head SHA, the report must say "prior blocker reused" or "prior request-changes still applies," not "live proof." - [ ] Final-report verifier should reject unsupported phrases like "inventory complete," "same as master," "live proof," and "file edits none" unless matching evidence is present.

jcwalker3 referenced this issue

2026-07-07 02:25:31 -05:00

Extract review-merge-pr workflow from monolithic LLM project skill #334

jcwalker3 referenced this issue

2026-07-07 03:16:44 -05:00

Reject reviewer queue-status reports that violate loaded workflow proof gates #339

jcwalker3 added the status:in-progress label 2026-07-07 03:45:43 -05:00

jcwalker3 referenced this issue from a commit

2026-07-07 03:46:51 -05:00

feat: enforce proof wording for pagination and live claims (#330)

jcwalker3 referenced a pull request that will close this issue

2026-07-07 03:47:17 -05:00