fix\(pr-pipeline\): align every needs-human path with the owner stop rule - part 4 of 6 #11022

Activity

1. melodic-automation-lanes

   added a parent issue on Oct 29, 2026

   • fix(pr-pipeline): align every needs-human path with the owner stop rule #10517
2. melodic-automation-lanes

   added the

   Task

   issue type on Oct 29, 2026
3. melodic-automation-lanes

   marked this as blocking on Oct 29, 2026

   • fix\(pr-pipeline\): align every needs-human path with the owner stop rule - part 6 of 6 #11024
4. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 29, 2026
5. github-actions commented on Oct 29, 2026

   

   github-actionsBot

   on Oct 29, 2026 – with GitHub Actions

   Last edited by melodic-automation-lanes

   Contributor

   More actions

   Proposed work class: work-class: scoped
   Basis: automated intake triage; the lanes App applied this class.

   Size: Small
   Complexity: Low
   Uncertainty: Known
   Flags: none
   Blocked by: none

   Understood: this is part 4 of 6 of #10517. Two changes are needed. Post-merge demotion, post-merge-failure and suite-quarantine issues get the needs-human label, and a failed red-main auto-revert guard labels its draft revert PR needs-human. The done-when items are specific and lane-checkable. Parts 1-3, 5 and 6 (#11019, #11020, #11021, #11023, #11024) are sibling splits, not duplicates.

   _{Automated triage, applied by the lanes App.}
6. github-actions

   added

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   and removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 29, 2026
7. melodic-automation-lanes

   added

   status: readyTriaged, unblocked, and fully specified; eligible to pick up.Triaged, unblocked, and fully specified; eligible to pick up.

   work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.A briefed fix or small feature; blast radius bounded by the brief, tests exist.

   admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.Admitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.

   agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   and removed

   admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.Admitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.

   agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.Fully specified and briefed; eligible for autonomous pickup from the frontier.

   on Oct 29, 2026
8. melodic-automation-lanes commented on Oct 29, 2026

   

   melodic-automation-lanesBot

   on Oct 29, 2026

   ContributorAuthor

   More actions

   The work-resolve-issue lane did not start this issue: it needs a person to make it clearer first.

   Why, in the run's own words:

   The issue leaves the decision open for each path. The parent ＃10517 says "Each needs a decision: align it, or record why it is a trust control the rule keeps." It picks neither option, it names no lane, and no recorded decision answers it. For each path below, decide: (A) align it, and name the lane it routes to and the label it gets instead of needs-human, or (B) keep it, and give the reason that goes into docs/conventions/loop-lane/README.md "When work stops for the owner". (1) Post-merge demotion record. needs-human is set in .github/workflows/post-merge-demotion-alert.yml:767 and by babysit_postmerge.py under the agent identity, and the record holds the merge rung off. That may count as a safety limit under the owner's rule. (2) post-merge-failure record, filed when no lane merge is in the failing range (same workflow line). Its text says 'a human fixes main', and an unlabeled fix issue per check already goes to intake. (3) Suite-quarantine issue (babysit_postmerge.py around line 3143). (4) Red-main draft revert when a guard fails (.github/scripts/post-merge-demotion-alert/red-main.mjs:193, docs/conventions/pr-pipeline/README.md rule 3). The guards keep a bot from reverting a person's merge, an old merge, or a revert. The path is dry-run only today ('This version has no revert path'). Note: choosing (A) for 1 or 2 means editing .github/workflows/post-merge-demotion-alert.yml. This lane cannot push to that path, so that part needs a person or a host run.

   What the run says it did not do:

   • No change was made, because the align-or-keep decision for each path is open. Tidy, review and build were skipped because there is no diff.

   Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40943541515

   To retry, answer the question in a comment whose first line is **Decision recorded.**, then remove needs-human and add agent-ready again.