package-updater-update-toolchainlisted

# Update the toolchain Move the pins that select the tools everything else resolves through — one tool per commit, with every release in the span linked. Use the `package-updater-updating-packages` skill for the phase structure, and in particular `references/upstream-links.md`, which carries the per-tool link taxonomy this command depends on. Also read `references/commit-conventions.md`, `references/ecosystems.md`, and `references/repo-scope.md`. For dependencies rather than tools, use the `package-updater-update` skill or the `package-updater-update-package` skill. User arguments: $ARGUMENTS ## Context Repository — run this command and read the output: ```bash git remote get-url origin 2>/dev/null || echo "(not a git repository)" ``` Default branch — run this command and read the output: ```bash git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo "(unknown)" ``` Pin files on this branch — run this command and read the output: ```bash out=$(for f in .tool-versions .nvmrc .python-version mise.toml .mise.toml; do [ -f "$f" ] && { echo "--- $f"; cat "$f"; }; done 2>/dev/null); if [ -n "$out" ]; then echo "$out"; else echo "(no toolchain pin files)"; fi ``` Package manager and engines — run this command and read the output: ```bash out=$(grep -hE '"(packageManager|engines|node|npm|pnpm)"[[:space:]]*:' package.json 2>/dev/null); if [ -n "$out" ]; then echo "$out"; else echo "(none declared)"; fi ``` What the version manager reports as outdated — run