Mnemon
中文
mnemondsh-mnemon
Contents

v0.5.13: Workspace, Builtin and DSH 0.1.7 Compatibility

View source on GitHub

v0.5.13 includes three fixes:

  • #268 fixes #266: Windows workspace paths below a regular file are rejected with ENOTDIR before a storage identity is computed. Valid workspace identities, junctions, Unicode paths and missing directory descendants retain their behavior. Existing storage directories are not moved or deleted.
  • #269 fixes #265: the conversation that owns a Builtin memory page hides its width handles while that page is open. The handles cannot intercept memory-page input; returning to Chat restores width dragging. The resident composer remains usable, and the rule stays scoped away from Sidebar and other conversations.
  • #270 fixes #267: Mnemon uses DSH 0.1.7-alpha.1's Config-backed live settings, current icon exports and producer-owned Session message sources. Settings writes retain revision checks and profile ownership. Historical Mnemon messages still participate in deduplication, including the official Session migration format.

Packages and upgrade

This release advances only dsh-mnemon to 0.5.13. All sixteen companion plugins and their exact Starter pins remain unchanged. Mnemon CLI remains independently maintained.

The Client compatibility floor remains DSH 0.1.5-rc.1. The supported framework peer range is ^0.1.5-rc.1 || ^0.1.6-alpha.2 || ^0.1.7-alpha.1; the evidence covers 0.1.5-rc.2, 0.1.6-alpha.2 and 0.1.7-alpha.1 using unchanged public DSH packages.

Back up the DSH profile configuration, legacy settings files and relevant Mnemon data before upgrading.

sh
dsh plugin --profile web add dsh-mnemon@0.5.13

Restart DSH and reload the browser. Substitute headless for that Profile. The full DSH profile requires Node ^22.19.0 || >=24.0.0.

Settings recovery and rollback

On DSH 0.1.7, supplemental recovery reads the retained settings.yaml.imported file without changing its bytes. Current explicit settings and native Strategy choices take precedence over older preferences; existing profile expressions remain expressions. Recovery preserves profile-local Source and Strategy choices across configuration reconciliation.

If the original settings.yaml is present at startup, DSH first performs its own import. Mnemon's supplemental UI/View recovery waits for the next cold Host start, so this upgrade can require a second complete DSH stop/start. A browser refresh or plugin remount does not complete that deferred recovery.

Automatic recovery requires the canonical mnemon root and the exact owning profile's legacy namespace. It does not infer custom-root ownership or reuse a foreign profile's suffix. Ambiguous or invalid input remains available in the retained backup for manual review.

New profile settings are not exported back to the old settings file. Downgrading requires the corresponding configuration backup and manual reconciliation of later changes; there is no automatic reverse export. Runtime, Documents and Memory Spaces data formats are unchanged.

Verification

The implementation evidence includes native Windows before/after observations, real Builtin hit testing and composer/Chat operations, and packed WebUI settings, Runtime writes and Session restoration on the three supported DSH cohorts. Model responses use an explicit loopback fixture without an external model API key; storage, tools and browser operations are real.

The release workflow must verify the versioned artifacts, the full pinned Registry composition and an actual v0.4.7 upgrade before creating the GitHub Release.

Previous release: v0.5.12.