feat: require true pre-merge baseline proof for non-zero validation exits (Closes #533) #574
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#574
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
Closes #533.
A non-zero validation exit reproduced on current (post-merge) master proves the failure exists on master now — it does NOT prove the failure pre-existed the PR under review. Reports could mislabel such a failure "baseline" and weaken validation gates.
Changes
premerge_baseline_proof.py—assess_premerge_baseline_proofclassifies four outcomes:clean pass,current-master failure reproduced,pre-merge baseline-proven failure,unresolved regression risk. A failure may be called baseline/pre-existing only with pre-merge proof: reproduced on the PR pre-merge base commit, or a documented known-failure record predating the PR. Current-master reproduction alone is rejected.final_report_validator.py—reviewer.premerge_baseline_proofrule onreview_prandreconcile_already_landedtasks.skills/llm-project-workflow/templates/review-pr.md— baseline-proof section requiring base commit, tested commit, command, exit status, failure signature.tests/test_premerge_baseline_proof.py— rejects current-master-only proof; accepts pre-merge base proof and documented known-failure records; validator integration.Validation
Worktree only:
branches/issue-533-premerge-baseline-proof@7fb8134.venv/bin/python -m pytest tests/test_premerge_baseline_proof.py tests/test_final_report_validator.py tests/test_llm_workflow_split.py -q→ 88 passedgit diff --check→ cleanprgs/masterwithout this diff reproduced all five identically. They are the #475 root-checkout-guard tests (gitea_mcp_server.pyRuntimeError) tripping on a dirty shared root checkout — environmental, and this diff touches none of those files.webui/lease_loaderimport ofISSUE_LOCK_FILE), since fixed upstream by #570; not caused by this diff.Self-review
Not allowed (author = jcwalker3).
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #574
issue: #533
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 38902-27b717ce5a6f
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-feat-issue-533-premerge-baseline-proof
phase: claimed
candidate_head:
7fb813446ftarget_branch: master
target_branch_sha: none
last_activity: 2026-07-09T03:14:57Z
expires_at: 2026-07-09T05:14:57Z
blocker: none
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #574
issue: #533
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 38902-27b717ce5a6f
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-feat-issue-533-premerge-baseline-proof
phase: claimed
candidate_head:
7fb813446ftarget_branch: master
target_branch_sha: none
last_activity: 2026-07-09T03:20:29Z
expires_at: 2026-07-09T05:20:29Z
blocker: none
The review of PR #574 (feat: require true pre-merge baseline proof for non-zero validation exits) has completed successfully.
premerge_baseline_proof.pyimplements the four pre-merge/reproduction classifications correctly.final_report_validator.pyintegrates thereviewer.premerge_baseline_proofrule as expected.skills/llm-project-workflow/templates/review-pr.mddocuments the baseline proof fields and labels.tests/test_premerge_baseline_proof.pycover all outcomes and pass cleanly.All acceptance criteria are fully met. Approved!
adopted_at: 2026-07-09T03:21:20Z
adopted_by_identity: sysadmin
adopted_by_profile: prgs-merger
adopted_from_session_id: 38902-27b717ce5a6f
adopted_from_profile: prgs-reviewer
adopted_from_reviewer_identity: sysadmin
adopted_from_comment_id: 7696
adoption_reason: merger-handoff-approved-head
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #574
issue: #533
reviewer_identity: sysadmin
profile: prgs-merger
session_id: 38902-27b717ce5a6f
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-feat-issue-533-premerge-baseline-proof
phase: adopted
candidate_head:
7fb813446ftarget_branch: master
target_branch_sha: none
last_activity: 2026-07-09T03:21:20Z
expires_at: 2026-07-09T05:21:20Z
blocker: none