Install the pinned node when the installed one is another major version (closes #118)

script/bootstrap used whatever node was installed, so on the CI runner
image, which ships node 24, the pinned yarn 1.22.22 ran under node 24
and printed the deprecation warning DEP0169 on every bootstrap. It now
uses the installed node only when its major version is the pinned one,
and otherwise installs the pinned node with nvm, as it already did when
node was missing, with yarn and the packages under it. Only the major is
compared because the Dockerfile stages use a node 22 alpine image that
nvm cannot replace. script/fmt and script/fmt-check run yarn under nvm's
pinned node when nvm has it installed, and otherwise the yarn on PATH.

Model: opus-5-5

TODO.md

@@ -21,6 +21,17 @@ fmt-check, and commit.
 
 # Completed Steps
 
+- 2026-10-08: The canonical `script/bootstrap` now uses the installed node only
+  when its major version is the pinned one (issue 118). Otherwise, as when node
+  is missing, it installs the pinned node under nvm and installs yarn and the
+  packages under it. The CI runner image ships node 24, under which the pinned
+  yarn 1.22.22 printed the deprecation warning DEP0169 on every bootstrap. Only
+  the major is compared because the `Dockerfile` stages start from a node 22
+  alpine image whose exact version is not the pin, and nvm cannot install a
+  prebuilt node on alpine. `script/fmt` and `script/fmt-check` now run yarn
+  under nvm's pinned node when nvm has it installed, and otherwise the `yarn` on
+  `PATH`. `REPO_POLICIES.md` and both checklists say so. Not yet tried on the
+  shared runner. Repositories pick this up on their next re-vendor.
 - 2026-10-07: The `script/cibuild` item in `NEW_REPO_CHECKLIST.md` now matches
   the canonical `script/cibuild` (issue 125). Its image build carries the tag,
   `-t "$tag"`, and the item says that `$version` comes from