feat: add BLOCKED + DIAGNOSE default rule + blocker report template (closes #552) #554
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#554
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 the canonical
BLOCKED + DIAGNOSEdefault rule for Gitea-Tools when an LLM cannot perform any required workflow step.Closes #552.
Changes
branches/issue-552-blocked-diagnose(no root checkout mutation).Tests / proof
git diff --check prgs/master...HEAD: clean.Canonical handoff details (see separate comment)
Branch: issue-552-blocked-diagnose
Head:
e11deb8(after push)Next
Fresh review requested on this PR. Verify the rule is now the single default, template is complete, docs cover all listed blocker classes, and no unsafe fallbacks are suggested.
e11deb8218todaf9910e83Canonical PR handoff — Issue #552
Issue: #552
PR: #554
Branch: issue-552-blocked-diagnose
Old head (pre-amend):
e11deb8218New head:
daf9910e83Files changed:
Exact tests run and results:
Where the rule was added:
Where the blocker report template was added:
Proof that missing required workflow steps stop before mutation:
Confirmation no unsafe fallback was used:
Any remaining follow-up issues:
Request for fresh review:
Please review PR #554. Confirm the rule is the single default everywhere, template matches the spec exactly, all 10 blocker classes are covered, docs prohibit unsafe fallbacks, proof of stop-before-mutation is present, and no disallowed techniques were used. Work was done strictly per gitea-workflow skill in isolated worktree.
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #554
issue: #552
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 8170-e9e634ee6ed5
worktree: branches/review-pr554
phase: claimed
candidate_head:
daf9910e83target_branch: master
target_branch_sha: none
last_activity: 2026-07-08T19:59:57Z
expires_at: 2026-07-08T21:59:57Z
blocker: none
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #554
issue: #552
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 8170-e9e634ee6ed5
worktree: branches/review-pr554
phase: claimed
candidate_head:
daf9910e83target_branch: master
target_branch_sha: none
last_activity: 2026-07-08T20:01:04Z
expires_at: 2026-07-08T22:01:04Z
blocker: none
pr: #554
branch: issue-552-blocked-diagnose
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/issue-552-blocked-diagnose
profile: prgs-author
session_id: unknown
phase: claimed
head_before:
daf9910e83expires_at: 2026-07-09T04:31:53Z
reviewer_active: no
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #554
issue: #552
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 65181-838f8c155c4a
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-pr-554
phase: claimed
candidate_head:
7c3699ce2dtarget_branch: master
target_branch_sha: none
last_activity: 2026-07-09T02:39:52Z
expires_at: 2026-07-09T04:39:52Z
blocker: none
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #554
issue: #552
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 65181-838f8c155c4a
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-pr-554
phase: released
candidate_head:
7c3699ce2dtarget_branch: master
target_branch_sha: none
last_activity: 2026-07-09T02:41:53Z
expires_at: 2026-07-09T04:41:53Z
blocker: manual-release
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #554
issue: #552
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: continue-prgs-554-252c95f2
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/issue-552-blocked-diagnose
phase: claimed
candidate_head:
cf130ed0fctarget_branch: master
target_branch_sha: none
last_activity: 2026-07-09T13:30:03Z
expires_at: 2026-07-09T15:30:03Z
blocker: none
Review APPROVE — PR #554
BLOCKED + DIAGNOSE default rule and standard blocker report template for #552.
Evidence
_preflight_resolved_rolewith capability statetest_mcp_servermerge/review failures also fail on clean master (baseline, not introduced here)Head pin
cf130ed0fc1b47846fd81c505e2bd3c8f2d570afCanonical PR State
STATE: APPROVED at current head; awaiting merge
WHO_IS_NEXT: merger
NEXT_ACTION: merge PR #554 with expected_head_sha pin and expected_changed_files
NEXT_PROMPT:
WHAT_HAPPENED: Reviewer approved after reviewing skill/template/docs and re-running focused tests after master merge
WHY: Implements #552 with clear stop+diagnose template; code delta is small and justified
ISSUE: #552
HEAD_SHA:
cf130ed0fcREVIEW_STATUS: APPROVE
MERGE_READY: yes
BLOCKERS: none
VALIDATION: focused pytest 50 passed after local master merge; mcp_server suite failures match master baseline
LAST_UPDATED_BY: sysadmin (prgs-reviewer)
adopted_at: 2026-07-09T13:30:30Z
adopted_by_identity: sysadmin
adopted_by_profile: prgs-merger
adopted_from_session_id: continue-prgs-554-252c95f2
adopted_from_profile: prgs-reviewer
adopted_from_reviewer_identity: sysadmin
adopted_from_comment_id: 8044
adoption_reason: merger-handoff-approved-head
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #554
issue: #552
reviewer_identity: sysadmin
profile: prgs-merger
session_id: continue-prgs-merger-554-011745a1
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/issue-552-blocked-diagnose
phase: adopted
candidate_head:
cf130ed0fctarget_branch: master
target_branch_sha: none
last_activity: 2026-07-09T13:30:30Z
expires_at: 2026-07-09T15:30:30Z
blocker: none