v0.5.6: Built-in Workspace Storage and Memory Reliability

v0.5.6 adds centralized per-workspace storage to Core/Host and includes the memory reliability fixes merged since v0.5.5: #216, #212, #213, #214 and #199.

#Centralized workspace storage

Choose Centralized workspaces in Settings → Memory system. Core/Host routes Runtime, Documents, Memory Spaces and state to <central-root>/workspaces/<sha256(canonical-workspace-path)>/. The optional root accepts an absolute path or home-relative path; clearing it uses MNEMON_DATA_DIR or ~/.mnemon. The independent USER.md setting can retain a global profile.

This is built into the main package. Sidebar inspection follows the selected registered workspace; Builtin and Headless operations follow their owning session. Existing symlink aliases share an identity, while moving or renaming a workspace selects a new identity. Scope changes preserve old data without migrating, merging or deleting it. Remote Provider namespaces keep their own sharing semantics. See configuration.

Long Memory Space paths now fit their column, and workspace selection and alignment remain accessible when labels wrap.

#Memory and CLI fixes

• The default Strategy applies Runtime capacity archival consistently to named tools, generic Actions, child Agents and browser management. Maintenance retains the selected Source and namespace, revision fences and queued-turn ownership.
• Native bulk archival preserves distinct but similar facts, reuses only exact existing content and validates import receipts before Runtime compaction. Host and Memory Spaces subprocess readers preserve UTF-8 characters across output chunks.
• Autonomous write workers cannot call mnemon_forget; idle review can create a separate Document but cannot overwrite or archive existing Documents. Explicit user operations retain their write tools, and unsuccessful forget receipts no longer claim deletion.
• Runtime entries and active, archived and searched Documents appear newest first by creation time, including before loading more items. Editing an older item does not move its creation date.
• Verified npm JavaScript launchers run in Node mode under an Electron Host, fixing CLI version detection, memory operations, ownership checks and updates while preserving embedding overrides and native executable behavior.

#Packages and upgrade

The other eleven official plugins remain pinned at 0.5.4. The Starter installs the exact tested sixteen-plugin combination. Mnemon CLI remains separately maintained through @mnemon-dev/mnemon.

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

Restart DSH and reload the browser; use headless instead of web for that Profile. The DSH baseline remains 0.1.2-rc.1, whose complete profile requires Node ^22.19.0 || >=24.0.0.

Existing storage formats remain compatible and enabling the new scope does not move existing memory. A Pack exports the selected root only; back up the complete central directory to retain every workspace. Before rolling back to dsh-mnemon@0.5.5, switch away from the new workspaces scope to a layout supported by that version and retain a backup. Old roots remain on disk; rollback does not combine data from different roots.

#Verification and limits

Release gates run the complete versioned workspace suite, independent package verification, a packed Starter install, frozen artifact integrity checks, npm read-back and a real Registry upgrade from v0.4.7.

The versioned release verification records 1,176 passing local tests, 17 packed artifacts and three fresh WebUI screenshots of settings, the 0.5.6 version and memory retained after reload.

The Core WebUI report retains nine screenshots and covers scope validation, two-workspace isolation, global USER.md, real Native storage, Host restart, Sidebar/Builtin routing, Chinese Dark, English Light and a 390-pixel layout. Electron evidence, creation-order evidence and Document protection evidence retain their original tested revisions.

The Flash capacity tests and automatic-memory acceptance are historical bounded experiments. The latter was accepted after user review, with partial replacements, stale documents, transient retention and incomplete recall recorded as follow-ups. This release does not claim to resolve those model-quality findings. Ordinary CI skips opt-in live-model checks; the Windows binary smoke test requires Windows.

Previous release: v0.5.5.