docs(changelog): mailbox owed-list fix from mempalace-toolkit c04d488
Lint / hadolint (push) Successful in 10s
Lint / skill-floor (push) Successful in 13s
Lint / doc-drift (push) Successful in 14s
Lint / skill-frontmatter (push) Successful in 18s
Lint / actionlint (push) Successful in 32s

This commit is contained in:
2026-10-25 13:10:00 +01:00
parent b06941d714
commit f7e35962d6
+12
View File
@@ -157,6 +157,18 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
### Fixed
- **Mailbox: asks this device answered long ago came back as owed
(mempalace-toolkit `c04d488`).** mempalace 3.11.0 stopped treating
`from_agent` as a filter on `event_list`; the filter is now `writer`. The
baked bridge still sent `from_agent` to find this device's own replies, so
against the central palace (on 3.11.0 since 2026-10-24T22:20Z) it got the
newest 100 events from every writer, and older replies dropped out. On
tor-ms22 the wake-up listed 22 owed asks; all 20 threads already had a
closing reply. The bridge now sends `writer`, and falls back to `from_agent`
only when a 3.10.0-or-older server rejects `writer`. Measured against the
live palace: 0 owed with the fix, 22 with `d5a03f4`. Until a device runs this
release, its wake-up keeps listing them; don't re-close them.
- **CI: a smoke job's image could be deleted mid-test by another job's disk
reclaim.** This is why v1.12.2's `-studio` tags were not published by its
tag run. Everything on one runner host shares its Docker daemon: concurrent