Contents

v0.5.35: Safer Memory Updates and Skill Evals

View source on GitHub

This release collects the fixes and small enhancements merged since v0.5.34.

  • Skills: removed skills appear in a Trash tab and can be restored to their recorded project and path. Restoration checks conflicts, offers renaming, and retains a displaced skill in Trash when replacement is confirmed. Completed background work refreshes skill cards. Reviews receive bounded context about open suggestions so they can reuse a pending suggestion while preserving its earlier requirements. Self-evolution settings explain that task and subagent sessions stay locally until deleted.
  • Evals: mark a case as Requires image input when a text-only backtest cannot measure it. The run displays Not measured, makes no executor or judge model call for that case, and excludes it from scores, pass rates and baseline comparisons. This is an explicit marker; image execution and automatic detection are not included.
  • Runtime and sync: automatic replacements preserve an entry's existing importance. Imports and Git sync preserve excess Runtime memories in a transactional local archive instead of failing the hot-memory budget or discarding records. Conflicting imported Memory Spaces stay inactive, receive a distinct name, and reuse the same conflict copy on a repeated merge. Model-facing Runtime snapshots omit default annotations and monitoring fields while retaining non-default metadata.
  • Providers: OpenViking writes work with its stricter 0.5 content API; keyword retrieval uses literal grep with scoped, bounded results and full-content reads. Holographic importance is converted from 1–5 to trust in 0–1, and omitted importance keeps the Provider default. Recall preserves native Provider ranks without treating uncalibrated scores as normalized confidence.
  • Host and integrations: independent tasks retain configured reasoning effort when inheriting the DSH model. Installation guidance explains DSH's automatic bundle patch and recovery from duplicate manual insertions. The public Host SDK exports canonicalWorkspacePath and workspaceStorageId; this does not introduce workspace storage migration. Themes can set --mn-block-fill for informational blocks without changing the default appearance.

Upgrade and compatibility

DSH 0.2.1-rc.2 and 0.2.0-rc.2 remain supported. From v0.5.34, use Memory System → Status → Check versions → Update, then restart DSH. For an exact WebUI installation:

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

For older installations and the desktop app, follow Compatibility and upgrades and Installation.

Existing memory needs no migration. Archived Runtime overflow remains local and is not a deletion; see operations for its recovery and backup boundaries. Skills Trash retains removed files until explicitly purged. The new eval marker is optional and earlier cases remain unchanged. Before downgrading to a Host that does not recognize it, disable marked cases; older Hosts cannot enforce the skip. Existing eval runs are unchanged: mark the case and rerun to record a new unmeasured result. No workspace paths or storage IDs change.

Changed packages

Package Previous New
dsh-mnemon 0.5.34 0.5.35
dsh-mnemon-source-runtime 0.5.15 0.5.16
dsh-mnemon-source-memory-spaces 0.5.22 0.5.23
dsh-mnemon-source-skills 0.5.1 0.5.2
dsh-mnemon-provider-hindsight 0.5.6 0.5.7
dsh-mnemon-provider-holographic 0.5.6 0.5.7
dsh-mnemon-provider-mnemon-native 0.5.9 0.5.10
dsh-mnemon-provider-openviking 0.5.8 0.5.9
dsh-mnemon-strategy-default-three-tier 0.5.10 0.5.11

The other ten component versions are unchanged. The Starter pins all eighteen components exactly.

Verification

The release acceptance record records the tested candidate packages, supported hosts, installation and upgrade checks, screenshots and limitations. The publication workflow verifies the full workspace, independent plugins, the pinned registry composition and a real upgrade before creating the GitHub Release.

Previous release: v0.5.34.