fix: exclude epic and child-only containers from allocator selection (Closes #844) #848
Merged
sysadmin
merged 2 commits from 2026-07-23 14:56:53 -05:00
fix/issue-844-exclude-epic-containers into master
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#848
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 #844. The controller/allocator was selecting epic #631 for direct author implementation even though its body delegates work to children and forbids product implementation on the epic itself.
Changes
classify_epic_or_child_only_containerand pre-rank skip reasonepic_or_child_only_container.bodythrough live inventory (_allocator_candidates_from_gitea) andWorkCandidate.Validation
Worktree
fix/issue-844-exclude-epic-containersbranches/fix-issue-844-exclude-epic-containersc3f282ba44a788f24fc281ce39edddbfe0fdea8eRisk
Low. Selection-only change; no mutation path for existing PRs. Over-exclusion only when body/label evidence matches the documented markers.
Next role
needs-reviewer
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #848
issue: #844
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 22106-f0c187147f5f
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-pr848-844
phase: claimed
candidate_head:
79256f9093target_branch: master
target_branch_sha:
1c455b6ec0last_activity: 2026-07-23T19:44:09Z
expires_at: 2026-07-23T19:54:09Z
blocker: none
Independent review — APPROVE (PR #848 / Issue #844)
Reviewed head:
79256f90932c4621a3bc0781e07910e84ed49642Base:
master@1c455b6ec0f9cb761fe6248de68c17e061fb5ecdAuthor:
jcwalker3(≠ reviewersysadmin)Profile:
prgs-reviewer/ rolereviewerAcceptance criteria (#844)
epic_or_child_only_containerScope vs #842 / #843
Selection-only. Does not reimplement #842 conflict-fix lifecycle or #843 cross-role handoff consume.
Files inspected
allocator_service.pygitea_mcp_server.pytests/test_allocator_epic_container_exclusion.pyValidation
Canonical PR State
STATE: approved-awaiting-merge
WHO_IS_NEXT: merger
NEXT_ACTION: Merge PR #848 at the exact approved head; do not re-review unless head moves; stop without merge if head drifts.
NEXT_PROMPT:
WHAT_HAPPENED: Independent reviewer approved PR #848 after full AC and regression validation.
WHY: All #844 acceptance criteria and focused allocator regression tests passed at the pinned head; author ≠ reviewer; merge is intentionally not performed by the reviewer role.
ISSUE: #844
HEAD_SHA:
79256f9093REVIEW_STATUS: approved / approval_at_current_head
MERGE_READY: true
BLOCKERS: none
VALIDATION: pytest passed; 90 passed (epic container + pre-rank + allocator service + cross-role allocation + inventory MCP); reviewer approved at head
79256f9093NATIVE_REVIEW_PROOF: transport=native_mcp; entrypoint=mcp_server; token_fingerprint=c68b14c0c8991481
LAST_UPDATED_BY: sysadmin / prgs-reviewer
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #848
issue: #844
reviewer_identity: sysadmin
profile: prgs-reviewer
session_id: 22106-f0c187147f5f
worktree: /Users/jasonwalker/Development/Gitea-Tools/branches/review-pr848-844
phase: released
candidate_head:
79256f9093target_branch: master
target_branch_sha:
1c455b6ec0last_activity: 2026-07-23T19:47:45Z
expires_at: 2026-07-23T19:57:45Z
blocker: manual-release
repo: Scaled-Tech-Consulting/Gitea-Tools
pr: #848
issue: #844
reviewer_identity: sysadmin
profile: prgs-merger
session_id: 40858-931d75fadace
worktree: branches/fix-issue-844-exclude-epic-containers
phase: claimed
candidate_head:
79256f9093target_branch: master
target_branch_sha:
1c455b6ec0last_activity: 2026-07-23T19:56:33Z
expires_at: 2026-07-23T20:06:33Z
blocker: none
Stale #332 review-decision lock cleanup (#594)
Status: APPLIED
sysadminprgs-merger2026-07-23T19:56:55.661882+00:00approveon PR fix: exclude epic and child-only containers from allocator selection (Closes #844) (#848)closed(merged=True)fa6ba8a162e2006bb2afc55f37b505486fad604f2prgs-reviewerManual deletion of session-state files is not the workflow.
This path only clears a lock when the referenced PR is merged/closed.