Skip to content

Run only stated or inferred commands unattended and report the unresolved cell - part 3 of 3 #16099

Closed

Description

@melodic-automation-lanes

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

Done when

  • The security review gate passed; the pull request body names this repository's dogfooding step.
  • AC7: nothing is cut here, so no control result is owed.
  • AC10: no new enforcement-placing skill is added here.

Activity

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

    @github-actions
    Contributor

    Size: Small
    Complexity: Low
    Uncertainty: Known
    Flags: none
    Blocked by: #16098
    Blast radius: this is the last part of #15731. It adds no code of its own. It covers the security review gate, the pull request body's dogfooding step, and the AC7 and AC10 notes, and maintainers and reviewers of the parent change read these.
    Reversible: yes; the items are checks on the pull request, so nothing needs undoing.
    Open questions: none

    I read this as part 3 of 3 of #15731. Its done-when is that the security review gate passes, the pull request body names this repository's dogfooding step, no control result is owed under AC7 because nothing is cut, and no new enforcement-placing skill is added (AC10). Part 2, #16098, is still open and comes first. #16097 doesn't appear among the open issues. The admission note says it isn't closed by a listed human or a merge, so that may still need checking. This isn't a duplicate, and no merged pull request already covers it.

    Automated triage. A maintainer reviews it.

  3. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 14, 2026
  4. melodic-automation-lanes commented on Nov 14, 2026

    @melodic-automation-lanes
    ContributorAuthor

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

  5. melodic-automation-lanes commented on Nov 20, 2026

    @melodic-automation-lanes
    ContributorAuthor

    {"v":1,"actor_id":337595936,"title_sha256":"112f87940fd8ca4c337b4df2e6d35113252e88850db9029d8173436945782e11","body_sha256":"ad4297adbf0abf228e470091b68ef56fed59a77405afa78fe0919c953a221792"}

  6. github-actions commented on Nov 20, 2026

    @github-actions
    Contributor
    No description provided.
  7. github-actions commented on Nov 20, 2026

    @github-actions
    Contributor
    No description provided.
  8. melodic-automation-lanes commented on Nov 20, 2026

    @melodic-automation-lanes
    ContributorAuthor

    The work-resolve-issue lane stopped on this issue (report-delivered): the issue asks for a report and no change, and the run posted that report, so the issue closes.
    It closes the issue as completed.

    In the run's words:

    report-delivered: part 3 of #15731 holds only gate items on work two merged PRs already delivered (#16819, merge bf22639; #17705, merge c9bc652). It needs no commit; the summary is the gate report.

    The run's report:

    Gate report for #16099, part 3 of 3 of #15731. The toolchain work landed in #16819 (closed part 1, #16097; toolchain 2.0.0 added the --unattended flag, the assumed: lines and the skip (unresolved: <ecosystem>.<key>) cell) and #17705 (closed part 2, #16098; carrier rows for the generic resolution text). Item 1, security review gate: passed on both PRs. The claude-security-review comment on #16819 at head 2294985 reported 0 findings (critical-findings: 0). The one on #17705 at head 479e2dd reported 0 findings (critical-findings: 0). The model tier each review ran at is not shown on the PR pages, so the plan's 'run at the frontier tier' clause is unconfirmed. Neither merged PR body names a dogfooding step, and this lane cannot edit a merged body, so this report names it: after the toolchain 2.0.x release reaches this repository, run /toolchain:check all --unattended here against the committed .claude/ecosystems/*.yaml records (bash, cross-cutting, dotnet, go, markdown, powershell, python, typescript, yaml). Confirm that each command prints an assumed: &lt;ecosystem&gt;.&lt;key&gt;=&lt;command&gt; (&lt;file&gt;:&lt;line&gt;) line, that no cell reads skip (unresolved: ...), and that nothing is installed or written under .claude/ecosystems/. Then run scripts/sync-shared-copies.sh --check for the carrier copies. This is the same step D24 requires in each listed repository before the parent closes. Item 2, AC7: nothing was cut. All nine bundled defaults are still under plugins/toolchain/reference/ecosystems/, and deleting them is the next item on this path, out of scope here. So no control result is owed. Item 3, AC10: neither PR adds a skill. #16819 changed the existing check and lint skills, and #17705 added carrier rows, generated copies and changelog fragments. So no new enforcement-placing skill was added.

    What the run says it did not do:

    • This report names the dogfooding step. It does not run it: /toolchain:check all --unattended is left for after release, and this lane runs no command from the checkout.
    • The two merged PR bodies were not edited to name the dogfooding step: they are merged, and this lane has no PR edit access. This report carries the step instead.
    • The security review's model tier ('run at the frontier tier') could not be confirmed from the PR pages; only the 0-finding results could.
    • Static reading only: .claude/ecosystems/markdown.yaml has no code-fix-cmd key, so an unattended --code-fix run may show skip (unresolved: markdown.code-fix-cmd). The dogfooding step would show whether it does.
    • Tidy skipped: the change has no lines to tidy.
    • Review skipped: there is no diff to review.

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

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

    No labels
    No labels

    Fields

    Work status

    agent-ready

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions