huskies: merge 1231 story project-rebuild must not silently downgrade a live sled to the stale image binary

script/build-project-images

@@ -6,6 +6,17 @@ set -euo pipefail
 #
 # 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.
 
 cd "$(dirname "$0")/.."
 

script/release

@@ -1,6 +1,16 @@
 #!/usr/bin/env bash
 set -euo pipefail
 
+# NOTE (story 1231): this script publishes the `huskies` binary artifact
+# (consumed by the `upgrade`/`upgrade all` chat commands) but does NOT
+# rebuild the huskies-project-* Docker images that `project-rebuild` uses.
+# Those images bake whatever binary was locally built the last time
+# `script/build-project-images` ran, so they silently drift stale otherwise
+# (currently baking 0.13.0). Run `script/build-project-images` after this
+# script — or better, fold it into this release flow — so a `project-rebuild`
+# right after a release doesn't need to self-heal a stale sled back up to the
+# version just published here.
+
 # ── Configuration ──────────────────────────────────────────────
 GITEA_URL="https://code.crashlabs.io"
 REPO="crashlabs/huskies"