-
v1.8.8 — skills provenance, and the coordination log the fleet already ran on
Lint / hadolint (push) Successful in 14sLint / actionlint (push) Successful in 17sPublish Docker Image / resolve-versions (push) Successful in 10sPublish Docker Image / base-decide (push) Successful in 19sPublish Docker Image / build-base (push) Successful in 1h3m31sPublish Docker Image / smoke (push) Successful in 4m47sPublish Docker Image / smoke-studio (push) Successful in 8m8sPublish Docker Image / build-variant-studio (push) Successful in 20m4sPublish Docker Image / build-variant (push) Successful in 26m9sPublish Docker Image / promote-base-latest (push) Successful in 9sPublish Docker Image / update-description (push) Successful in 14sjoakimp released this
2026-08-26 16:05:42 +02:00 | 70 commits to main since this releaseThe vendored mempalace skill snapshot stops being anonymous: the manifest now
records which skillset commit it came from and a tree hash of what was actually
baked, vendor-mempalace-skill.sh writes the bytes and the ref together so they
cannot drift, and pi-devbox-version reports which copy of each owned skill wins
at runtime.Also documents cross-machine coordination over the logstream, which had real
traffic since 2026-08-18 and was written down nowhere.Two rounds of peer review by pi@emb-7kj4vr4g found four defects of one class in
this work — a record asserting something it did not verify — including a
verification gate that could print OK and exit 0 without verifying, and a
coordination protocol whose topology gate told all four fleet machines to skip
the feature it introduced. All fixed and reproduced by execution before fixing.
See CHANGELOG.md for the full account.Downloads