Skip to content

Hold Unapproved Agent-Safety Issues in an Attended backlog-burndown Run #3761

Closed

Description

@ptr727

Found by the local review pass on #3760 and classed pre-existing, since that pull request did not write the text in question.

Defect

backlog-burndown carries decision-triage "Needs the Maintainer" as a generated include, but only under "Away Mode", introduced as "The away run holds back what it names". "Ranking" for an attended run has no hold for an issue whose fix edits host-setup/agent-safety/.

Failure

Suppose an attended run finds an open issue asking for an edit under host-setup/agent-safety/, and no approval has been recorded on it. Ranking ranks it, a worker implements it, and the worker drives a pull request the maintainer never approved in design. After #3760 the merge is still held, since the merge grant does not reach such a pull request, so the cost is the wasted lane and review rather than an unreviewed merge.

Done When

The attended path applies the agent-safety hold from "Needs the Maintainer". It ranks such an issue only once an approval is recorded on it, and otherwise asks.

Activity

  1. added
    pre-existingReview finding classed pre-existing per local-strict-review Disposing of Findings
    proseA defect in rule or procedure text
    on Nov 1, 2026
  2. ptr727 commented on Nov 1, 2026

    @ptr727
    OwnerAuthor

    Released (2026-11-01): worktree and branch removed, so this claim holds no files. Its fix merged to develop in PR #3776. The issue closes when that is promoted.

    Backlog burndown claim (round 1, group G3). Branch: feature/burn-3761. Issues: #3761, #1275, #1274, #1306, #1301, #3733.

    Predicted file set:

    • .agents/skills/backlog-burndown/SKILL.md and its generated trees (.github/skills/backlog-burndown/, .claude-plugin/fleet-skills/skills/backlog-burndown/, .claude-plugin/fleet-skills/.source-digests/backlog-burndown)

    Updated: repo-worktree dropped (no change needed). #1276 and #1307 were removed from this group, because their direct-push rule also needs GOVERNANCE.md "Operational Repositories", and another live group holds that file. Both issues are released and return to the next round's ranking.

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

    pre-existingReview finding classed pre-existing per local-strict-review Disposing of FindingsproseA defect in rule or procedure textskillsAgent skill

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions