gascity now builds the worker-env manifest from the worker's toolchain,
not the image's patch revisions. The manifest records the arch, the OS
release, Go and dolt, and the upstream releases of the libraries and
tools actions reach (major.minor; git and yq at their major). The Debian
epochs and Ubuntu revisions are gone, so the Blacksmith image's routine
security updates no longer move the hash. That is what stranded every
remote action on 2026-10-07: coreutils 9.4-3ubuntu6.1 -> 6.2 and libc6
2.39-0ubuntu8.6 -> 8.8 forced re-pins (gascity #7266, beads #7338).
- tools/rbe/worker-env.txt: byte-identical copy of gascity's new
manifest. platforms/BUILD.bazel pins its sha256,
sha256:6be1381cf08e7fd66684cfce6f26aca57de2561e722c505d1f2f578e9fdeafa7.
The manifest now also measures python3, curl, openssl, unzip and yq,
which //scripts:scripts_test runs from the executor.
- scripts/rbe_worker_env_test.go: the manifest must be a rendering of
gascity's tools/rbe/worker-env (sorted; one arch, dolt, go, os and yq
line; packages at most major.minor, installed). A copy of an older
gascity manifest with dpkg revisions, a hand edit or a truncated copy
fails here.
- tools/rbe/worker-env-sync, run by nightly.yml: compares the manifest
and the pin with gascity's main byte for byte. If they differ, it
prints the diff and the pin to commit, and fails.
Merge this together with the gascity change. Pool workers run gascity
main's provisioning, so they serve the new hash only once that change
lands, and beads' actions on any other pin queue. This supersedes #7338
(the old-format re-pin). The new key misses the cache once.
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>