You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Delete toolchain's bundled ecosystem defaults - part 2 of 3 #16032
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.
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.
Activity
github-actions commentedon Nov 13, 2026
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.
melodic-automation-lanes commentedon Nov 13, 2026
Not admitted to the issue lane yet: blocker #16031 is not closed by a listed human or a merge.