Bootstrap keeps yarn and node only at their pinned versions (closes #154)

script/bootstrap kept any yarn found on PATH, so YARN_VERSION applied
only where none was installed. It now keeps the yarn on PATH only when
yarn --version is exactly YARN_VERSION, and otherwise prepares that
version through corepack. The node on PATH is used only when it has the
pinned major version and is at least NODE_MIN_VERSION, as
REPO_POLICIES.md asks. After installing either, bootstrap looks the tool
up through PATH again, stops naming the path if it is not the pinned
one, and prints the version it uses, as it does for Go. The other host
scripts that run yarn run it through the new script/yarn, which uses the
same node test with ~/.local/bin first on PATH, and otherwise the pinned
node in nvm.

Model: opus-5-5

README.md

@@ -42,12 +42,12 @@ either one is broken. We provide:
 
 - `script/bootstrap` — install all dependencies (the pinned node via nvm unless
   the `node` on `PATH` has the pinned major version and is new enough for the
-  frontend's dependencies, yarn `YARN_VERSION` via corepack, or npm where there
+  frontend's dependencies, yarn `YARN_VERSION` via corepack unless the `yarn` on
-  is no corepack, unless the `yarn` on `PATH` is exactly that version,
+  `PATH` is exactly that version, `yarn install --frozen-lockfile`, Go
-  `yarn install --frozen-lockfile`, Go `GO_VERSION` unless the `go` on `PATH` is
+  `GO_VERSION` unless the `go` on `PATH` is exactly that version, and the Go
-  exactly that version, and the Go modules), linking what it installs itself
+  modules), linking what it installs itself into `~/.local/bin`, which has to be
-  into `~/.local/bin`, which has to be on `PATH`. It installs no Go linter and
+  on `PATH`. It installs no Go linter and not Docker: `make test` and
-  not Docker: `make test` and `make lint` run in Docker
+  `make lint` run in Docker
 - `script/setup` — make a fresh clone ready for development: bootstrap plus the
   git pre-commit hook
 - `script/dev` — run the Vite dev server, which proxies `/api` to a locally
@@ -61,11 +61,10 @@ either one is broken. We provide:
 - `script/clean` — remove what `script/build` writes
 - `script/projectname` — print the project name (used for the Docker image tag)
 - `script/yarn` — run yarn with the given arguments under the node
-  `script/bootstrap` would use: with `~/.local/bin` first on `PATH`, the first
+  `script/bootstrap` would use: with `~/.local/bin` first on `PATH`, the `node`
-  `node` on that `PATH` when it has the pinned major version and is new enough
+  there when it has the pinned major version and is new enough for the
-  for the frontend's dependencies, and otherwise the pinned node in nvm. Every
+  frontend's dependencies, and otherwise the pinned node in nvm. Every other
-  script that runs yarn on the host runs it through this one, except
+  script that runs yarn on the host runs it through this one
-  `script/bootstrap`, which picks its own node and yarn
 - `script/test` — build the `test` phase of `Dockerfile`, writing no image: the
   frontend's unit tests in its `frontend-test` stage, and the backend's Go tests
   with the race detector and coverage. The frontend's production build is left

TODO.md

@@ -22,18 +22,17 @@ Run `make frontend-viewport-test` in CI as its own step; it is not part of
 # Completed Steps
 
 - 2026-10-19: `script/bootstrap` keeps the `yarn` on `PATH` only when
-  `yarn --version` is exactly `YARN_VERSION`, and otherwise installs that
+  `yarn --version` is exactly `YARN_VERSION`, and otherwise prepares that
-  version as it did when no yarn was installed
+  version through corepack, as it did when no yarn was installed
   ([#154](https://git.eeqj.de/sneak/netwatch/issues/154)); any yarn used to be
   kept. It uses the `node` on `PATH` only when that node has the major version
-  of `NODE_VERSION`, as `REPO_POLICIES.md` asks, and is at least
+  of `NODE_VERSION` as well as being at least `NODE_MIN_VERSION`, as
-  `NODE_MIN_VERSION`; a node 24 was kept before. After installing node or yarn
+  `REPO_POLICIES.md` asks; a node 24 was kept before. After installing node or
-  it looks the tool up through `PATH` again and stops if that one fails the same
+  yarn it looks the tool up through `PATH` again and stops if that is not the
-  check, as it does for Go, and it prints the node and yarn versions it uses.
+  pinned one, as it does for Go, and it prints the node and yarn versions it
-  Every script that runs yarn on the host, except `script/bootstrap`, which
+  uses. Every script that runs yarn on the host runs it through the new
-  picks its own node and yarn, runs it through the new `script/yarn`. That
+  `script/yarn`, which puts `~/.local/bin` first on `PATH`, uses the `node`
-  script puts `~/.local/bin` first on `PATH`, uses the first `node` on that
+  there when it passes the same test, and otherwise runs yarn under the pinned
-  `PATH` when it passes the same test, and otherwise runs yarn under the pinned
   node in nvm; `make build` ran yarn under whatever node was first on `PATH`
 - 2026-10-19: report file writes no longer overlap
   ([#150](https://git.eeqj.de/sneak/netwatch/issues/150)), so the reports of

script/bootstrap

@@ -7,8 +7,7 @@
 # at least NODE_MIN_VERSION; otherwise NODE_VERSION is installed via nvm
 # (installing nvm itself first, from a hash-verified release archive,
 # never curl | sh). Yarn is used directly only if it is exactly
-# YARN_VERSION; otherwise that version is prepared through corepack,
+# YARN_VERSION; otherwise that version is prepared through corepack.
-# or installed with npm where there is no corepack.
 # Go, with its gofmt, is used directly only if it is exactly GO_VERSION;
 # otherwise that release is installed from its hash-verified archive.
 #
@@ -146,10 +145,12 @@ ensure_nvm() {
 }
 
 # node_ok: the node on PATH has the major version of NODE_VERSION and is
-# at least NODE_MIN_VERSION. Only the major is compared with the pin,
+# at least NODE_MIN_VERSION. Only the major is compared with the pin:
-# as REPO_POLICIES.md asks. node itself compares the versions: major,
+# the Dockerfile's node stages start from a node 22 alpine image whose
-# then minor, then patch. A node that fails does not pass.
+# exact version is not the pin, and nvm cannot install a prebuilt node
-# script/bootstrap and script/yarn carry this function unchanged.
+# on alpine. node itself compares the versions: major, then minor, then
+# patch. A node that fails does not pass. script/bootstrap and
+# script/yarn carry this function unchanged.
 node_ok() {
     if ! command -v node >/dev/null 2>&1; then return 1; fi
     node -e '

script/yarn

@@ -1,8 +1,7 @@
 #!/bin/sh
 # script/yarn: run yarn with the given arguments under the node
-# script/bootstrap would use. Every script that runs yarn on the host
+# script/bootstrap would use. Every other script that runs yarn on the
-# runs it through this one, except script/bootstrap, which picks its
+# host runs it through this one.
-# own node and yarn.
 set -eu
 
 ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
@@ -12,10 +11,12 @@ NODE_VERSION="22.17.0"
 NODE_MIN_VERSION="22.13.0"
 
 # node_ok: the node on PATH has the major version of NODE_VERSION and is
-# at least NODE_MIN_VERSION. Only the major is compared with the pin,
+# at least NODE_MIN_VERSION. Only the major is compared with the pin:
-# as REPO_POLICIES.md asks. node itself compares the versions: major,
+# the Dockerfile's node stages start from a node 22 alpine image whose
-# then minor, then patch. A node that fails does not pass.
+# exact version is not the pin, and nvm cannot install a prebuilt node
-# script/bootstrap and script/yarn carry this function unchanged.
+# on alpine. node itself compares the versions: major, then minor, then
+# patch. A node that fails does not pass. script/bootstrap and
+# script/yarn carry this function unchanged.
 node_ok() {
     if ! command -v node >/dev/null 2>&1; then return 1; fi
     node -e '