Skip to content

pr-merge: per-PR live smoke of changed skills before unattended merge (owner decision 16) #7529

Closed as not planned

Description

@kyle-sexton

Decision

Owner decision 16 (2026-10-14): a per-PR live smoke of changed skills (behavior probes plus claude plugin eval) is required merge evidence before the first unattended merge of any PR touching plugins/*/skills/** or plugins/*/agents/**. Until it exists, those PRs are excluded from auto-merge. Decision 73: review, security review, ci-status and the skill smoke always run in CI.

The #6202 Amendment now points at this decision in place of its earlier "no smoke check" line.

Work

  • Design and build the per-PR smoke in CI for changed skills and agents.
  • Make pr-merge exclude PRs touching those paths until the smoke exists and passes.

Refs: #6202

Activity

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

    @github-actions
    Contributor

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

    Size: Large
    Complexity: High
    Uncertainty: Knowable
    Flags: none
    Blocked by: #7719

    Decision recorded. The owner answered in the Refinement and Issue Triage sessions (2026-10-25), deciding the open items below on the facts:

    go with whatever the facts/data/metrics + /discovery:research says and ensure we're aligned with SOLID, DRY/SSOT principles

    [quote truncated; the full decision is at the link]

    #7529 (comment)

    This decision settles the open questions. The smoke is parked under #7719 (D2), so nothing is built until that re-evaluation. The pr-merge exclusion line is dropped, because D2 says not to re-add the globs. The credential question is answered when the smoke is designed. I've left the existing structural class for a maintainer to confirm.

    Automated triage, applied by the lanes App.

  3. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 15, 2026
  4. kyle-sexton commented on Oct 18, 2026

    @kyle-sexton
    MemberAuthor

    Decision recorded.

    Question: Owner decision 16 kept skill and agent PRs out of unattended merge until a per-PR smoke passed. Q624 later removed all path denials, so those PRs now merge on the verifier verdict alone. Options: (a) re-add plugins/*/skills/** and plugins/*/agents/** to denied-paths now, then build the smoke; (b) Q624 supersedes it, close; (c) build the smoke as pr-verify evidence with no path denial.

    Owner's answer: defer under #7719 Do not re-add the globs: #7719 lists "the denied paths" and "Q582's requirement that the verifier run a changed skill" as restrictions removed on purpose, to be re-evaluated against what the drain shows. A paid eval per PR also needs D10's credential answer first. Basis: #7719 body; docs/conventions/pr-pipeline.yaml:322-332.

    The owner accepted this recommendation as item D2 of a 21-decision batch in an attended backlog-shaping session on 2026-10-18. The batch question: "Accept all 21 batch 7 decisions, with my change to D13 (#6008 goes to the lane, but you merge its PR because it edits AGENTS.md)? I post a 'Decision recorded.' comment on each issue." The owner answered: "Accept, with my D13 change (Recommended)".

    Posted by AI from the owner's answer in that session.

  5. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 24, 2026
  6. kyle-sexton commented on Oct 24, 2026

    @kyle-sexton
    MemberAuthor

    Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.

    To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.

  7. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    priority: mediumReal value, no hard deadline; normal backlog flow.
    status: needs-decisionAwaiting a human or maintainer judgment call.
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 24, 2026
  8. changed the issue type fromtoon Oct 24, 2026
  9. kyle-sexton commented on Oct 25, 2026

    @kyle-sexton
    MemberAuthor

    Decision recorded. The owner deferred this work under #7719 on 2026-10-18 and ruled out re-adding the path denials. Nothing new is decided here. Intake's triage (#7529 (comment)) asked two questions: Q1 (keep open as parked, or close) is answered by "defer under #7719" below, so the issue stays open and parked; Q2 (is the smoke still wanted as pr-verify evidence) waits on #7719's re-evaluation and D10.

    Sources, quoted verbatim:

    The body's second work line ("Make pr-merge exclude PRs touching those paths until the smoke exists and passes") is replaced by this decision. On origin/main, docs/conventions/pr-pipeline.yaml sets denied-paths: [] today.

    No lane work: the decision's only checkable part, denied-paths: [] with no skill or agent globs, already holds on main (docs/conventions/pr-pipeline.yaml:980). This issue stays parked under #7719.

    Checks a person runs:

  10. 17 remaining items

  11. melodic-automation-lanes commented on Oct 27, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane: no trusted-human acceptance criteria: a listed human must put the confirmed - [ ] criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited; Size large: the split into sub-issues at intake is pending (owner Q93). Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  12. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    and removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Oct 27, 2026
  13. melodic-automation-lanes commented on Oct 29, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue lane did not start this issue (split-required). Its Size is too large for one run: split it into smaller issues with /work-items:decompose.

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

    To retry, remove needs-human and add agent-ready again.

  14. kyle-sexton commented on Oct 29, 2026

    @kyle-sexton
    MemberAuthor

    Scope narrowed: excluding PRs that touch skill paths from auto-merge, and requiring the smoke as merge evidence, are path holds. The owner removed path holds (owner decisions Q15/Q16, 2026-10-29: "There should be no path restrictions. We can add that in later."), so that part is deferred until open issues and open PRs reach 0. Building the per-PR skill smoke as a CI test stays in scope.

  15. kyle-sexton commented on Nov 1, 2026

    @kyle-sexton
    MemberAuthor

    Cordoned to the After zero milestone by the Issue Triage session; not closed, and needs-human removed. The 2026-10-29 comment on this issue records the skill-path auto-merge exclusion and the merge-evidence smoke as path holds "deferred until open issues and open PRs reach 0", and #7719 lists the changed-skill verifier run among the restrictions removed for throughput. Standing direction §10 defers that hardening to after zero; the per-PR skill smoke is built then.

  16. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Nov 1, 2026
  17. added this to the After zero milestone on Nov 1, 2026
  18. kyle-sexton commented on Nov 5, 2026

    @kyle-sexton
    MemberAuthor

    Closed at the owner's direction (2026-11-05, hub session): hardening issues close now and are rediscovered and reopened one at a time at the hardening pass.

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.work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.

    Fields

    Work status

    confirmed

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions