Repository navigation
fix\(pr-pipeline\): align every needs-human path with the owner stop rule - part 6 of 6 #11024
Description
Part 6 of 6 of #10517, split at intake (owner Q93). The done-when below is copied from #10517 as written.
Done when
- Five escalation classes in
plugins/autonomy/reference/guardrails.md#escalationthat loop-lane §2 still requires (gate-failure, verification-divergence, admission-rejection, demotion, structural-plan-approval). - Intake sends text addressed to the triage run (an injection attempt) to a person: a trust control, but not one of the three reasons as written.
- Each path above either routes to a lane (no needs-human) or is named in the "When work stops for the owner" section as a kept trust control, with its reason.
- A test or check per changed path shows the new routing.
- No HIGH/CRITICAL security path is loosened without a security-review pass at the head.
- Each path in the body either routes to a lane with no
needs-human, or is named indocs/conventions/loop-lane/README.md"When work stops for the owner" as a kept trust control with its reason, as decisions 1 and 4 assign. - Each changed path has a test or check showing the new routing.
- No kept trust control in decision 1 changes behavior. Each has a test showing it still stops for a person.
- A security-review pass ran at the head of every PR that touches a
person_reasonsor hold path.
Activity
github-actions commentedon Oct 29, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: this is part 6 of 6 of #10517, split at intake. It aligns the remaining needs-human paths with the owner stop rule. Each path either routes to a lane or is named in the loop-lane "When work stops for the owner" section as a kept trust control. It also restores the five escalation classes in the guardrails reference, and adds tests or checks for each changed path. It must keep the kept trust controls unchanged and get a security-review pass on any PR that touches a person_reasons or hold path. The scope and done-when are clear, so nothing is missing. This is a sibling of #11019, #11020, #11021, #11022 and #11023, not a duplicate of them.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 29, 2026
Not admitted to the issue lane yet: blocker #11019 is not closed by a listed human or a merge; blocker #11020 is not closed by a listed human or a merge; blocker #11021 is not closed by a listed human or a merge; blocker #11022 is not closed by a listed human or a merge; blocker #11023 is not closed by a listed human or a merge.