v0.7.0

v0.7.0

Release date: 2026-09-13

Highlights

• Moved the DSH integration cohort from the 0.1.0-rc.8 era onto the 0.1.5-rc.2 host cohort. Every @deepseek-ai/dsh-* peer floor, the devDependency floor, and the regenerated lockfile now sit on one cohort, with no rc.6/rc.8 provider left behind.
• Recomposed the client manifest after @deepseek-ai/dsh-client-runtime was removed in 0.1.2-alpha.1. dsh.client.inject now names the packages that actually own the services the client half consumes: dsh-client-ui-renderer (slots), dsh-client-ui-settings (settingsScope), and dsh-client-locale (locale).
• Routed every panel and dashboard HTTP route through the host's Connection auth gate. Raw webServer.register routes do not inherit authentication, so all 20 routes now call connection.requestRejection(req) before reading memory data or performing a side effect, and connection is declared next to webServer in the mount. The pre-existing same-origin checks remain as a second layer.
• Reworked the Memory Dashboard list into bounded pages with infinite scroll. The list requests 100 memories at a time, keeps a live status line under the list (Scroll to load more memories. / Loading more memories… / All matching memories loaded.), preserves the active filters and batch selection as pages append, and falls back to a scroll listener where IntersectionObserver is unavailable.

Compatibility and migration

• Supported host cohort is now 0.1.5-rc.2. The previous peer floor >=0.1.0-rc.6 could not match a later prerelease cohort under npm's prerelease matching rules, so installations on the new host produced peer warnings even though the plugin loaded.
• Unauthenticated requests to plugin routes now answer 401 where they previously served data on loopback. Browser sessions are unaffected: the panel and dashboard run with the host's signed dsh-auth-* cookie.
• dsh-better-sidebar is now a ^0.19.1 optional peer, matching the version the dashboard tab is verified against. Without it the core plugin and the Settings panel continue to work and the dashboard tab is unavailable.
• The dashboard memory list now loads in pages of 100 instead of one 150-row request, so batch actions apply to the rows loaded so far; use the filters to narrow the set before selecting all.
• No memory data, configuration key, tool name, or route path changed. The mnemosyne settings namespace and ~/.dsh/mnemosyne store are untouched.

Validation

• pnpm install: resolves the whole graph on 0.1.5-rc.2 with no peer-dependency warnings.
• node scripts/inject-lint.mjs (dsh-plugin-upgrade-skill): verdict OK — no removed-package residue, no missing peer for a declared client inject, Cordis peer at ^4.0.1.
• pnpm test: 157 tests passed (140 focused unit/client/identity tests and 17 integration tests), against a pre-migration baseline of 153 passing with no pre-existing failures.
• Isolated staging cold boot on the target cohort: plugin row composes with nothing pending, __DSH_BOOT__.entries advertises dsh-mnemosyne with the recomposed inject list, the host-advertised client bundle returns 200 with the dsh-mnemosyne registration id, and the auth gate answers 401 unauthenticated, 403 cross-origin, and serves the route body once authenticated and same-origin.
• npm pack --dry-run: cordis.patch.yml ships in the tarball and matches dsh.bundle.patch.

v0.6.0

v0.6.0

Release date: 2026-09-01

Highlights

• Added workspace-scoped memory recall and automatic writes. Workspace identity is explicit and stable through a .mnemosyne-id marker and identity.json; unbound workspaces never silently fall back to another namespace.
• Added the mnemosyne_bind tool plus workspace binding, adoption, rebind, namespace discovery, and migration routes. Migration supports dry runs, SQLite backups, journals, and revert, while keeping legacy session data isolated until the user opts in.
• Added filtered, confirmed batch memory management in the dashboard for veracity, expiry, importance, lifecycle invalidation, and scope moves, including workspace targets and backup-before-mutation protection. Single-memory controls use the same registered batch API.
• Tightened memory deletion to the current namespace or globally visible records, and preserved the existing same-origin, local-only dashboard security boundary.
• Added identity/namespace coverage and expanded host, client, and integration tests for workspace behavior, migration guardrails, dynamic scope configuration, and dashboard management.
• Kept DSH integration metadata compatible with the supported >=0.1.0-rc.6 host range and restored the required client runtime injection.

Compatibility and migration

• Existing installations retain session-scoped behavior unless recallMode or autoWriteScope is explicitly changed. recallMode=workspace requires workspace-level automatic writes.
• Workspace mode requires an explicit project binding. Use mnemosyne_bind after user consent or bind the project from the dashboard; the plugin refuses $HOME and / as binding targets.
• Legacy default and dsh_* rows are not automatically reassigned. Review the dashboard migration tools and create a backup before moving data.
• dsh-better-sidebar@^0.16.1 remains optional; without it, the core plugin and Settings panel continue to work, but the dashboard tab is unavailable.

Validation

• pnpm install --frozen-lockfile --ignore-scripts && pnpm test: 153 tests passed (136 focused unit/client/identity tests and 17 integration tests).

Version iteration

• v0.5.0 introduced the bundled local Memory Dashboard as a read-only inspection surface.
• v0.6.0 adds explicit workspace memory identity, migration and backup tooling, and confirmed dashboard memory management while preserving session compatibility by default.

Summary

This release turns the dashboard from an inspection surface into a safe, explicitly authorized memory-management surface and adds project-level memory sharing without silently changing existing session-scoped installations.

Lazy alternative

Skipped a separate workspace service and database migration layer; add them only if namespace-based isolation no longer meets cross-bank or multi-machine requirements.

License

MIT

Full Changelog: v0.5.0...v0.6.0

v0.5.0

v0.5.0

Release date: 2026-08-26

Highlights

• Added a read-only Mnemosyne memory dashboard that can be opened from the existing Settings panel when dsh-better-sidebar is available.
• Vendored the dashboard web assets into the plugin package so the view is served by the existing DSH listener without a second process, port, login flow, or remote asset dependency.
• Added active-bank dashboard routes for overview counts, recent/searchable memories, today's activity, knowledge triples, consolidation history, memory details, graph data, lifecycle summaries, and compatible upstream dashboard views.
• Added schema-tolerant SQLite reads for current and legacy Mnemosyne tables, including duplicate-memory suppression and bounded pagination, filtering, sorting, and response fields.
• Kept the dashboard read-only: browser requests are GET-only, local/same-origin checks are enforced, database access uses SQLite read-only mode, and no arbitrary database path or SQL is accepted from the browser.
• Added optional and lazy Better Sidebar registration so the existing Mnemosyne Settings panel continues to work when the sidebar plugin is not installed or loads later.
• Added English and Simplified Chinese dashboard labels, a dedicated brain icon, active-language switching, and a single-instance dashboard tab.

Compatibility

• dsh-better-sidebar@^0.16.1 is an optional peer dependency. Dashboard integration is unavailable when it is absent; the core plugin and Settings panel remain available.
• The dashboard reads the active Mnemosyne bank resolved by the plugin. It does not aggregate other banks or alter session-scope behavior.
• Dashboard assets and their upstream notices/license are included under assets/dashboard/.

Validation

• pnpm test
• 124 tests passed: 103 unit, 17 integration, and 4 client tests.
• Dashboard route tests cover parameter bounds, active-bank reads, schema-tolerant responses, GET-only enforcement, same-origin rejection, read-only API behavior, static asset containment, and optional Better Sidebar registration.

Version Iteration

• v0.4.4 focused on auto-sleep correctness, session-disposed consolidation, scope migration locking, diagnostics resilience, storefront sync, and documentation.
• v0.5.0 adds the first user-facing memory inspection surface: a bundled, local, read-only dashboard while preserving the existing CLI-first tools, automatic memory behavior, configuration flow, and data isolation.

v0.4.4

v0.4.4

Fixes

• Auto-sleep threshold: a cleared sleep_threshold now falls back to the upstream default (50) instead of firing every periodic check.
• Session-disposed consolidation: sessions that never auto-stored a memory no longer trigger a forced sleep.
• Scope migrations (default → global, scoped → default) run under the same per-bank memory lock as the tools.
• Diagnose stays healthy when the auxiliary consolidation count is unavailable.
• Settings panel: merged a duplicated disabled prop on the model picker button.

Other

• Added an automated awesome-dsh-plugin storefront sync (fork-based PR).
• Documentation synced (README, design, data-flow comparison). 117 tests: 96 unit + 17 integration + 4 client.

Full Changelog: v0.4.3...v0.4.4

v0.4.3

Full Changelog: v0.4.0...v0.4.3

v0.4.0

Full Changelog: v0.3.1...v0.4.0

v0.3.1

Full Changelog: v0.3.0...v0.3.1