Mnemon
中文
mnemondsh-mnemon
Contents

v0.3.5: Dual DSH Host Compatibility

View source on GitHub

v0.3.5 keeps the reproducible DSH 0.1.1-rc.2 npm baseline while adding source compatibility with the GitHub-only DSH 0.1.2-alpha.1 preview. One plugin build now spans both Host generations without parsing a version, inspecting function arity, or branching on capabilities.

Compatibility

  • The Web client follows the alpha's split ownership model: Session and Workspace state remain available through the controller/renderer services, the renderer owns slots, Chat-specific slot contracts no longer require the removed owner type, Workspace selection no longer depends on recentWorkspaceId, and third-party locale IDs pass through safely.
  • The package no longer imports the removed @deepseek-ai/dsh-client-runtime entry directly. Its DSH client ordering dependency moves to @deepseek-ai/dsh-client-ui-renderer, while the published rc.2 dependency graph remains reproducible.
  • Generic Mnemon Connection channels survive the alpha's ApiProxy-to-Remote/gateway migration, and the child-local subagent token-usage projection remains isolated from DSH's complete-log metric.
  • Host RPC registration uses one unconditional call shape. Mnemon always supplies the trailing authority object required by rc.2; alpha's two-argument JavaScript implementation ignores the extra argument and applies its uniform authenticated browser-session boundary.

Security and upgrade

No persistence or Provider-data migration is required. DSH 0.1.1-rc.2 still consumes the startup-only remoteAccess setting: management channels remain loopback by default and are promoted together only when explicitly configured as trusted-host. DSH 0.1.2-alpha.1 ignores that transport argument and requires its launch-token-derived browser session for every channel. Retaining the setting lets the same configuration move forward to alpha or roll back to rc.2 without weakening rc.2's defaults.

Update dsh-mnemon, restart each DSH profile that uses it, and reopen the Memory System surface. Registry installations should continue using DSH 0.1.1-rc.2; the alpha is a source-verification target, not an npm installation target. Rolling back dsh-mnemon to 0.3.4 requires no data conversion.

Verification

  • The complete TypeScript and Vitest chain passes with 524 tests; one Windows-only smoke test is skipped on the local non-Windows run.
  • A real Connection compatibility test registers the same three-argument call against both the installed rc.2 implementation and the source-linked alpha implementation.
  • CI verifies Linux on Node.js 22.19 and 24, Windows on Node.js 24, and a dedicated Node.js 24 build linked to the exact upstream dsh-v0.1.2-alpha.1 tag at commit cd5ef814.
  • The deterministic double build verifies 106 generated files with identical hashes, and an isolated real Headless profile activates with 35 total tools and five representative Mnemon tools.
  • The packed package contains 113 files, 378,527 packed bytes, and 1,714,783 unpacked bytes; all 10 Node-compatible public entries import successfully, and publint strict plus the attw ESM profile pass.
  • git diff --check passes for the release changes.

See PR #105 for the compatibility implementation and evidence. See the v0.3.4 release notes for the preceding Runtime Memory scope and capacity release.