Skip to content

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

Open

Description

@melodic-automation-lanes

Part 2 of 6 of #10517, split at intake (owner Q93). The done-when below is copied from #10517 as written.

Done when

  • babysit_risk.person_reasons escalates only a CRITICAL security finding; the rule says HIGH or CRITICAL.
  • Other person_reasons: a high path (floor, denied or aliasing path), a trusted-actor widening, a file listing too long to check.
  • babysit_risk.person_reasons escalates a HIGH or CRITICAL security finding, and test_babysit_risk.py covers both.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 29, 2026
  2. github-actions commented on Oct 29, 2026

    @github-actions
    Contributor

    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: babysit_risk.person_reasons escalates only a CRITICAL security finding, but the owner stop rule says HIGH or CRITICAL. The fix is to escalate both, keep the other person reasons (high path, trusted-actor widening, file listing too long to check), and cover both severities in test_babysit_risk.py. This is part 2 of 6 of #10517. The sibling parts are separate slices, not duplicates.

    Automated triage, applied by the lanes App.

  3. added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 29, 2026
  4. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    on Oct 29, 2026
  5. melodic-automation-lanes commented on Oct 29, 2026

    @melodic-automation-lanes
    ContributorAuthor

    Not admitted to the issue lane yet: blocker #11019 is not closed by a listed human or a merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: mediumReal value, no hard deadline; normal backlog flow.status: readyTriaged, unblocked, and fully specified; eligible to pick up.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions