Contents

v0.5.42: Bounded Runtime Snapshots and Reliable Memory Management

View source on GitHub

  • Runtime snapshots: bound model-visible snapshot history while preserving append-only request prefixes for unchanged and eligible additive updates. Checkpoint on the snapshot count/byte budget or when permissions and visible facts require immediate cleanup (#579; fixes #573).
  • Skill origins: keep suggestions, drafts, rewrite, backtests and adoption bound to the original skill/workspace. Recover legacy suggestions from exact review evidence; preserve unresolvable manual drafts and ask for regeneration instead of targeting a same-named file (#580; fixes #574).
  • Permanent Document deletion: remove active or archived managed Markdown and its index record after confirmation, with index/file revision fences, ReadGrant checks and rollback on index-write failure. Refresh counts and selection; do not write a cold index or delete project source files (#581; closes #578).
  • Scoped source settings: distinguish inherited defaults from an explicitly empty scope, confirm zero-source saves, preserve runtime priority and keep eligible capability/custom Sources selectable. Existing write restrictions stay separate (#569; fixes #568).
  • Git-sync archives: reject unsafe paths, excessive entry counts/sizes and inconsistent stored ZIP sizes before extraction. Existing valid stored/deflated packs remain supported (#564).

Runtime context and cache reuse

Runtime keeps at most four eligible complete projected snapshots / 64 KiB of UTF-8 text in the current model-visible group. Unchanged content adds nothing. Eligible additive updates preserve the existing request prefix; deletions, corrections, authority/scope changes and either budget trigger a checkpoint. One oversized current snapshot is retained whole. Checkpoints retire old model-visible snapshots while preserving the append-only session audit. These initial limits balance context growth and prefix reuse; they are not an empirically optimal cache setting or a claim of measured cloud cache hits.

Runtime verification records actual Host request prefixes, checkpoint behavior and migration boundaries. Provider caching remains best-effort and depends on the provider's own rules.

Upgrade and compatibility

Use Memory System → Status → Check versions → Update, then restart DSH. For an exact Web-profile install:

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

Existing memory data and settings require no manual migration. Existing conversations clean up recognized historical Runtime snapshots as they next run. Permanent Document deletion applies to the managed copy and its index.

Official support retains 0.2.0-rc.2, 0.2.1-rc.2, 0.2.1-rc.3, 0.2.1-rc.5 and 0.2.2-rc.1. RC1 requires Node >=24.9.0. Additional acceptance targets the unmodified source commit fcc0ad462172522aaf5c93a7b2e01f6b9f0b0159; it does not cover arbitrary master/alpha revisions or the reporter's Windows machine. See compatibility.

Changed packages

Package Previous New
dsh-mnemon 0.5.41 0.5.42
dsh-mnemon-source-documents 0.5.13 0.6.0
dsh-mnemon-source-runtime 0.5.17 0.5.18
dsh-mnemon-source-skills 0.5.8 0.5.9

The other fifteen components retain their versions. Use the Starter's exact eighteen-component composition; independent plugin versions do not need to match the Starter.

Release acceptance · Full diff