Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 73 Pull Requests 9 Actions Packages Projects Releases Wiki Activity

Already-landed reconciliation reports must include PR inventory pagination proof #308

New Issue
Closed
opened 2026-07-07 00:50:54 -05:00 by jcwalker3 · 1 comment
jcwalker3 commented 2026-07-07 00:50:54 -05:00
Owner
Copy Link
Copy Source

Already-landed PR reconciliation workflows list open PRs and classify candidates, but final reports do not always include pagination/final-page proof.

Problem:

If reconciliation claims it inspected open PRs or found all already-landed blockers, it must prove the PR inventory was complete. Otherwise, agents may miss additional already-landed PRs or incorrectly report queue state.

Required behavior:

  1. Reconciliation workflows must list open PRs with pagination proof.

  2. Pagination proof must include one of:

    • explicit no-next-page / final-page evidence from the MCP response
    • traversal until an empty or final page is returned
    • explicit requested page size and response count proving the page limit was not hit

  3. Final reconciliation reports must include:

    • requested page size
    • page count fetched
    • returned PR count per page
    • final-page/no-next-page proof

  4. Do not claim all already-landed PRs were found unless inventory completeness is proven.

Acceptance criteria:

  • Reconciliation reports fail validation if inventory proof is missing.
  • Reports cannot claim complete queue scan without pagination proof.
  • Tests cover first page below limit, first page exactly at limit, multiple pages, and missing pagination metadata.
Already-landed PR reconciliation workflows list open PRs and classify candidates, but final reports do not always include pagination/final-page proof. Problem: If reconciliation claims it inspected open PRs or found all already-landed blockers, it must prove the PR inventory was complete. Otherwise, agents may miss additional already-landed PRs or incorrectly report queue state. Required behavior: 1. Reconciliation workflows must list open PRs with pagination proof. 2. Pagination proof must include one of: * explicit no-next-page / final-page evidence from the MCP response * traversal until an empty or final page is returned * explicit requested page size and response count proving the page limit was not hit 3. Final reconciliation reports must include: * requested page size * page count fetched * returned PR count per page * final-page/no-next-page proof 4. Do not claim all already-landed PRs were found unless inventory completeness is proven. Acceptance criteria: * Reconciliation reports fail validation if inventory proof is missing. * Reports cannot claim complete queue scan without pagination proof. * Tests cover first page below limit, first page exactly at limit, multiple pages, and missing pagination metadata.
jcwalker3 added the status:in-progress label 2026-07-07 08:07:54 -05:00
jcwalker3 commented 2026-07-07 08:08:55 -05:00
Author
Owner
Copy Link
Copy Source

Implementation ready for review in PR #376.

Adds assess_reconcile_inventory_report() to require pagination metadata and final-page proof before reconciliation reports claim a complete open-PR scan.

Implementation ready for review in PR #376. Adds `assess_reconcile_inventory_report()` to require pagination metadata and final-page proof before reconciliation reports claim a complete open-PR scan.
sysadmin removed the status:in-progress label 2026-07-07 09:26:06 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#308