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

PR reconciliation handoffs must prove linked issue status before reporting it #300

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

Reviewer reconciliation handoffs may report linked issue status without proving that the issue was fetched live in the current session.

Observed behavior

An already-landed PR reconciliation handoff reported:

  • Linked Issue Status: Issue #263 (open)

However, the visible transcript did not show a live gitea_view_issue call for issue #263 in that session.

Problem

Linked issue state can change. Reconciliation handoffs must not report issue status unless it was fetched live during the current session.

Required behavior

  1. If a PR claims to close or link an issue, reconciliation handoffs must fetch the linked issue live before reporting status.

  2. If the linked issue cannot be fetched, report:

    • Linked issue status: not verified in this session

  3. Any recommended issue close/reopen/comment action must require exact capability proof.

  4. Final-report validation must reject linked issue status claims without a corresponding live issue-fetch proof.

Acceptance criteria

  • Reconciliation handoffs include live linked issue proof or mark issue status as unverified.
  • Reports cannot claim issue open, issue closed, or issue resolved without proof.
  • Tests cover linked issue open, linked issue closed, missing issue, and no linked issue.
Reviewer reconciliation handoffs may report linked issue status without proving that the issue was fetched live in the current session. ## Observed behavior An already-landed PR reconciliation handoff reported: * `Linked Issue Status: Issue #263 (open)` However, the visible transcript did not show a live `gitea_view_issue` call for issue #263 in that session. ## Problem Linked issue state can change. Reconciliation handoffs must not report issue status unless it was fetched live during the current session. ## Required behavior 1. If a PR claims to close or link an issue, reconciliation handoffs must fetch the linked issue live before reporting status. 2. If the linked issue cannot be fetched, report: * `Linked issue status: not verified in this session` 3. Any recommended issue close/reopen/comment action must require exact capability proof. 4. Final-report validation must reject linked issue status claims without a corresponding live issue-fetch proof. ## Acceptance criteria * Reconciliation handoffs include live linked issue proof or mark issue status as unverified. * Reports cannot claim `issue open`, `issue closed`, or `issue resolved` without proof. * Tests cover linked issue open, linked issue closed, missing issue, and no linked issue.
jcwalker3 added the status:in-progress label 2026-07-07 04:44:31 -05:00
jcwalker3 commented 2026-07-07 04:44:34 -05:00
Author
Owner
Copy Link
Copy Source

Implementation ready for review in PR #372.

Adds assess_reconcile_linked_issue_report() to require live gitea_view_issue proof before reporting linked issue open/closed/resolved status in reconciliation handoffs.

Implementation ready for review in PR #372. Adds `assess_reconcile_linked_issue_report()` to require live `gitea_view_issue` proof before reporting linked issue open/closed/resolved status in reconciliation handoffs.
sysadmin removed the status:in-progress label 2026-07-07 09:19:03 -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#300