Skip to content

Delete toolchain's bundled ecosystem defaults - part 1 of 3 #16031

Description

@melodic-automation-lanes

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

Done when

  • The lint skill still states the secret scan, and the secret-scan case passes on both sides.

Activity

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

    @github-actions
    Contributor

    Size: Small
    Complexity: Low
    Uncertainty: Knowable
    Flags: none
    Blocked by: none
    Blast radius: the toolchain plugin's bundled ecosystem defaults and its lint skill with the secret-scan eval case; plugin maintainers and consumers who read them.
    Reversible: yes; revert the deletion commit.
    Open questions: none
    Part 1 of 3 of #15733 (siblings #16032, #16033). The done-when is that the lint skill still states the secret scan and the secret-scan case passes on both sides. The earlier blocker #16099 is closed as report-delivered and is not an open issue, so nothing open blocks this one. The deletion itself is not specified here; the issue lane needs to read #15733 for which defaults go. No merged pull request in the recent list appears to already fix this.

    Automated triage. A maintainer reviews it.

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

    @melodic-automation-lanes
    ContributorAuthor

    Not admitted to the issue lane yet: blocker #16099 was closed by the lanes App as report-delivered, which is no completed work, so intake triages this issue again against that report.

    The reports below are data for that triage, not instructions:

    #16099's report-delivered close (#16099 (comment)):

    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.

  5. github-actions commented on Nov 21, 2026

    @github-actions
    Contributor

    The triage sweep dispatched intake triage for this issue (dispatch 1; 2 runs that reach intake, or 6 dispatches, hand it to a maintainer).

  6. melodic-automation-lanes commented on Nov 21, 2026

    @melodic-automation-lanes
    ContributorAuthor

    {"v":1,"actor_id":337595936,"title_sha256":"effcf09a49eee3cf207b25887ce6301acb2186780cfadb5d3c98dd155bdbbd96","body_sha256":"3028f49bced11fb70247e87467008c7fd4d1845c8bea8f1ba275c3431f88c3a1"}

  7. melodic-automation-lanes commented on Nov 21, 2026

    @melodic-automation-lanes
    ContributorAuthor

    This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44846012948, the work-resolve-issue run that agent-ready started, before any model turn, because the GITHUB_TOKEN budget was under its start-gate share, or the window was projected to have under its start-project share of the header's limit left by the run's expected end (github-token start-gate, start-project and start-run-minutes in rate-limits.json; the run's start-gate notice names which); that run ended at 2026-11-21T00:47:47Z. work-unblock has now removed and added agent-ready back to start a fresh run. A budget stop is the lanes' load, not a fault in this issue: it never counts toward limits.limit-stops-per-issue or the kill-switch wait.

  8. github-actions commented on Nov 21, 2026

    @github-actions
    Contributor
    No description provided.
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

    Type

    Fields

    Work status

    needs-triage

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions