feat: add dedicated reconciliation controller-handoff schema (Closes #303) #373
Labels
Clear labels
allocator
anti-stomp
architecture
bug
chore
codex
concurrency
contamination
control-plane
dashboard
database
design
documentation
enhancement
gitea
glitchtip
important
incident
incident-bridge
integration
jenkins
labels
leases
mcp
mcp-health
mcp-menu
multi-project
mutating
nice-to-have
observability
portability
preflight
protected-branch
queue
read-only
reconnect
recovery
refactor
release
reliability
resumable-review
reviewer
roadmap
safety
security
self-hosted
sentry
stale-runtime
status:blocked
status:in-progress
status:pr-open
status:ready
terminal-lock
testing
tracker
type:bug
type:feature
type:feature
type:guardrail
visibility
workflow
workflow-hardening
workflow-hardening
Controller-owned work allocator
Prevent concurrent LLM session stomping
Architecture / structural design
OpenAI Codex client / workflow session surface
Concurrent session safety
Workflow or session contamination incident
MCP control-plane coordination and allocation authority
MCP operational dashboard/queue view
Internal coordination storage (SQLite/Postgres)
Design / investigation, no implementation
Docs / runbooks
New feature or improvement
Gitea MCP workflow
GlitchTip integration
Operational or process incident requiring durable audit trail
Sentry-to-Gitea incident bridging
Integration testing
Jenkins integration
Label taxonomy management
Lease adopt/release/expire lifecycle
MCP server / tooling
MCP namespace and runtime health
MCP menu surface
Work spanning multiple monitoring projects or Gitea repos
Mutating action; requires gating
Observability, metrics, traces, error reporting
Cross-platform / portability
Shared preflight gates before mutation
Protected branch / stable-branch policy concern
Work queue visibility and allocation
Read-only, no mutation
MCP client reconnect/reload recovery path
Recovery paths for stale/foreign leases
Code refactor / restructure
Release / versioning
Reliability / failure handling
Persist and resume prepared review verdicts across sessions
Reviewer workflow tooling
Roadmap / umbrella issue
Safety rails and fail-closed mutation guards
Security / trust boundary
Self-hosted infrastructure integration
Sentry error monitoring integration
Stale backend daemon / runtime-vs-master parity failures
Issue is blocked
Issue is being worked on
Issue has an open pull request
Issue is ready for work
Terminal review lock (#332) path
Tests / test coverage
Issue tracker hygiene / meta
Bug or defect
Feature or enhancement
Feature or enhancement
Safety gate or guardrail
Workflow state visibility for LLMs/operators
Cross-tool workflow
LLM workflow coordination hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Scaled-Tech-Consulting/Gitea-Tools#373
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Implements #303: controller handoff schema must support already-landed PR reconciliation.
Adds
assess_reconciliation_handoff(report_text, observed_commands=None)toreview_proofs.py, plus theRECONCILIATION_HANDOFF_FIELDSschema andRECONCILIATION_FORBIDDEN_FIELDSlist:Eligibility class: ALREADY_LANDED_RECONCILE_REQUIRED, Capabilities proven / Missing capabilities, PR/Issue comments posted, PRs/Issues closed, Git ref / Worktree / MCP-Gitea / External-state mutations, Read-only diagnostics, Blocker, Safe next action, No review/merge confirmation. Any missing field fails.PR number opened,Pinned reviewed head,Scratch worktree used,Workspace mutations,Issue lock proof,Claim/comment statuseach fail validation (the exact stale fields observed in the issue).git fetch/pullin the command log must appear underGit ref mutations; claimingnonefails (acceptance criterion 3).{complete, downgraded, reasons}matching sibling verifiers.Tests
tests/test_reconciliation_handoff.py: 13 tests — blocked reconciliation, successful PR close, comment-only reconciliation, no-op already-closed state, missing linked-issue proof, wrong eligibility class, missing handoff section, each stale field (five cases), and observed-fetch-claimed-none (acceptance criteria of #303).1237 passed, 6 skipped, 20 subtests, 2 failed— both failures are the known pre-existing master breakages, proven earlier on cleanfa0cb12(this branch's exact base):TestIssueLockArtifactWarning(#359, fix pending in PR #364) andtest_final_report_validator::test_clean_reviewer_report_passes(#320/#327 fixture interaction, reported in the PR #367 handoff). Neither is introduced by this branch.Closes #303
🤖 Generated with Claude Code
All tests pass successfully after merging master (1359 passed, 1 failed [pre-existing]). Reviewed the implementation of
assess_reconciliation_handoffinreview_proofs.pyand the test coverage intests/test_reconciliation_handoff.py. It correctly introduces a dedicated handoff schema for already-landed PR reconciliation, enforcing presence of necessary fields and rejection of stale reviewer/author fields. Verified that the remaining failure is pre-existing on master.