v0.5.7: DSH 0.1.5 Compatibility and Document Archival

v0.5.7 fixes Memory system HTTP 405 errors on DSH 0.1.5-rc.1, provides explicit copy recovery for affected legacy Sessions, and makes document archival use verified Host receipts. It includes #226 and #224.

#DSH compatibility and legacy Sessions

The Starter supplies the Connection dependency needed to register Memory system RPC routes on the published DSH 0.1.5-rc.1 profile. Settings, Status and Source operations load through the normal authenticated transport. Earlier supported DSH peer ranges remain accepted; the development and release checks now use the published 0.1.5-rc.1 package cohort.

New Mnemon recall and instruction messages omit the legacy summary metadata rejected by DSH's Session migration. The new dsh-mnemon-repair-session command previews affected v0 JSONL or JSONL.zstd files and can write a separate repaired copy. It removes only the two known historical Mnemon summary fields, preserves the remaining decoded bytes and refuses overwrites or unsupported input.

Existing Sessions are not repaired automatically. Stop DSH and back up the entire Session root before following the legacy Session recovery procedure. Test the copy before explicitly replacing a Session; DSH then performs its own migration. Retain the original backup for rollback. Plain JSONL recovery works on Node 20; compressed recovery requires Node 22.19 or newer supported Node versions.

#Document archival

The archive worker proposes an index summary and an existing eligible Memory Space without writing data. The Host validates the proposal and current access policy before indexing, appends the exact cold path and content hash, and constructs lineage from its own durable receipt. Invalid plans leave the document active and create no index.

An exact existing index can be reused. If committing the archived document fails, the Host compensates a newly created index. The archive dialog explains that a destination must support synchronous writes and deletion; changes to read-only policy during the operation are respected. The original document content remains available in cold storage.

#Packages and upgrade

Mnemon Native Provider and Default Three-tier Strategy remain at 0.5.5; the other eleven official plugins remain at 0.5.4. The Starter pins this complete sixteen-plugin combination. Mnemon CLI is still maintained separately through @mnemon-dev/mnemon.

dsh plugin --profile web add dsh-mnemon@0.5.7

Restart DSH and reload the browser. Substitute headless for that Profile. The full DSH 0.1.5-rc.1 profile requires Node ^22.19.0 || >=24.0.0. Runtime, Documents and Memory Space storage formats are unchanged. Downgrading Mnemon does not undo DSH's Session migration; use the retained pre-migration backup when returning to an older DSH version.

#Verification

The versioned release report records 1,218 passing tests, 16 independently verified plugin repositories, 17 packed artifacts and three fresh WebUI screenshots of version 0.5.7, successful archival and the retained Native index after reload.

The release workflow verifies the versioned workspace, independent plugin packages and packed upgrades, freezes the four changed artifacts, checks npm integrity and clean installation of the complete composition, and tests a Registry upgrade from v0.4.7 before creating the GitHub Release.

The DSH compatibility report retains eleven real WebUI screenshots, including the HTTP 405 reproduction and a repaired Session reopened after restart. The document archive report retains thirteen screenshots covering successful archival, invalid plans, retry, cold content, recall and tool lineage. These reports keep their original tested revisions. Loopback model fixtures validate application behavior, not model quality; live-model and platform-specific opt-in tests are separate.

Previous release: v0.5.6.