Skip to content

Delete toolchain's bundled ecosystem defaults - part 2 of 3 #16032

Open

Description

@melodic-automation-lanes

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

Done when

  • AC4 (first clause): toolchain runs no bundled default command; the bundled ecosystems folder is gone and nothing outside changelogs and the kept test fixture names it.
  • The no-record fixture's after run holds no bundled command.
  • The resolution-ladder reference no longer describes a bundled portable default; the shell-portability baseline passes its own stale-entry check.
  • 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 13, 2026
  2. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    Size: Medium
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: none

    Understood: this is part 2 of 3 of #15733, split at intake. It asks to delete toolchain's bundled ecosystem defaults folder, so that nothing outside changelogs and the kept test fixture names it. The no-record fixture's after run must hold no bundled command. The resolution-ladder reference and the shell-portability baseline's stale-entry check must be updated to match. No new enforcement-placing skill is added here.

    Nothing is missing. The sibling parts are #16031 (part 1) and #16033 (part 3). They are split-outs of the same parent, not duplicates. I found no merged pull request that already does this. Ordering against part 1 is for the issue lane to confirm.

    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 #16031 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

    No labels
    No labels

    Type

    Fields

    Work status

    ready

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions