-
v1.8.10 — deploy the transcript scrubber fleet-wide
Publish Docker Image / build-variant-studio (push) Successful in 17m4sLint / actionlint (push) Successful in 17sPublish Docker Image / resolve-versions (push) Successful in 14sPublish Docker Image / base-decide (push) Successful in 12sPublish Docker Image / build-variant (push) Successful in 18m45sPublish Docker Image / build-base (push) Successful in 41m59sPublish Docker Image / update-description (push) Successful in 6sPublish Docker Image / promote-base-latest (push) Successful in 11sPublish Docker Image / smoke (push) Successful in 4m55sLint / hadolint (push) Successful in 8sPublish Docker Image / smoke-studio (push) Successful in 5m9sreleased this
2026-08-27 17:52:00 +02:00 | 65 commits to main since this releaseShips mempalace-toolkit b2b50af (from 5b8d78f): feeder-side secret scrubbing at the
single staging choke point, the symlink-resolution fix that stops the fail-closed
feeder refusing to stage, the hlc owed-set join, the queued-delivery note, and
explicit MEMPALACE_MAILBOX_NOTIFY protocol modes.Also pi-studio v0.9.48 -> v0.9.52 for the studio variant: 22 additive commits, pi
floor >=0.84.3 met exactly by our pin.Reason for the tag: the scrubber has been live on one device only; every other
device kept staging unscrubbed transcripts into the shared palace.ACCEPTANCE ON FIRST CLIENT — the feeder is fail-closed, so its failure is silent.
Confirm a [scrub] summary line appears, the palace drawer count moves for that
session, and exit 3 did not fire through the /usr/local/bin symlink. Silence means
the memory feed is down, not that all is well.Downloads