v0.5.9: Runtime Archive Destinations and Legacy Session Recovery
v0.5.9 includes the Runtime archive destination fix in #252, legacy Session recovery in #253, and the sidebar label alignment already merged in #249.
Runtime archival
A capacity-triggering write can now archive to eligible spaces activated or created by its initiating View after recall was pinned. The Host asks the owning Memory Spaces Source for its write scope and rechecks the exact Source, View, active destinations and cancellation before each batch. Recall remains pinned; older Sources retain the conservative fallback. Refusal preserves existing Runtime entries and pending input.
Legacy Session recovery
The explicit copy-repair CLI handles the three known old Mnemon summaries, compatible v2 subagent descriptors, packed empty-string placeholders and null delta names. It preserves stream assembly, sequence/provenance and token timing, as well as unrelated plugin content.
For completed tool chains whose IDs were cleared by the old DeepSeek adapter, repair can restore the unique provider ID already recorded in that same stream. It requires consistent call/result payloads and closed ownership references. It never generates an ID. Missing candidates, conflicting identities and unaccounted references still refuse the whole output. The original file and existing output paths are never overwritten. See Operations for preview and new-copy commands.
The reporter's original Windows source-build logs were not available for direct validation. Issue #251 remains open for confirmation against those artifacts.
Packages and upgrade
dsh-mnemon: 0.5.9.dsh-mnemon-source-memory-spaces: 0.5.7.
The Starter pins the complete sixteen-plugin composition. The other fifteen plugin versions and the supported DSH peer ranges remain unchanged. Mnemon CLI is maintained separately.
dsh plugin --profile web add dsh-mnemon@0.5.9Restart DSH and reload the browser. Substitute headless for that Profile. The full DSH profile requires Node ^22.19.0 || >=24.0.0. Updating the package does not automatically rewrite old Session files; use the explicit repair command when needed.
Verification
The combined implementation passed 1,452 tests with six opt-in skips, real Mnemon 0.2.8 CLI checks, sixteen independent plugin repositories and seventeen packed artifacts. The Runtime report and legacy Session report retain 26 before/after and cold-reopen screenshots with hashes and the revisions actually tested. Legacy continuation was exercised through the actual WebUI, including validation of the model request's recorded tool ID, arguments and result. Model responses used deterministic loopback fixtures.
The release workflow verifies the versioned workspace and independent artifacts, freezes only the two changed packages, publishes Memory Spaces Source before the Starter, and checks the complete Registry install plus a real upgrade from v0.4.7 before creating the GitHub Release.
Previous release: v0.5.8.