huskies: merge 1242 refactor script/release builds project images so they can't drift

script/build-project-images

@@ -4,19 +4,10 @@ set -euo pipefail
 # Build all project images in dependency order:
 #   huskies  →  huskies-project-base  →  huskies-project-<stack> (one per stack fragment)
 #
-# Run this after `script/docker_rebuild` or whenever you add a new stack.
-# Safe to re-run: each step re-tags the image with the latest layers.
-#
-# IMPORTANT (story 1231): this script is NOT part of `script/release`. The
-# huskies-project-* images bake whatever `huskies` binary happened to be built
-# locally the last time this ran — as of this comment that's 0.13.0, several
-# releases behind the current fleet artifact. `project-rebuild` self-heals a
-# sled that comes back on a stale baked binary (it re-upgrades it in place
-# from the gateway's published artifact), but that costs an extra
-# download+restart cycle every time. Run `script/build-project-images` after
-# every `script/release` — ideally as a step in the release flow itself — so
-# freshly rebuilt sleds start on a current binary instead of relying on the
-# self-heal.
+# Called automatically by `script/release` (story 1242) so the huskies-project-*
+# images never drift from the version being published. Also safe to run
+# standalone after `script/docker_rebuild` or whenever you add a new stack —
+# each step re-tags the image with the latest layers.
 
 cd "$(dirname "$0")/.."