v0.3.3

Add verified compatibility with the DSH 0.2.1-rc.1 desktop runtime, while retaining exact CLI 0.2.1-rc.2 support and the existing pre-0.2.0 range. This resolves the desktop plugin-manager compatibility rejection without granting an exemption.

Validation: all 422 unit/integration tests, typecheck, build, and packed-file checks pass; 59 real boot/tool checks pass independently on each runtime.

v0.3.2 — DSH 0.2.1-rc.2 compatibility

Compatibility

• Declare support for DSH 0.2.1-rc.2 in the tools and system-prompt peer requirements (#45).
• Keep the existing pre-0.2.0 compatibility range; other 0.2.x prereleases require separate validation.

No memory schema, runtime implementation, or development dependency changes.

Validation

• Typecheck and all 422 tests passed.
• Build and package checks passed.
• The built package passed 59 real boot/tool lifecycle checks against DSH 0.2.1-rc.2, including CJK search, recall, scope isolation, and revision CAS.

v0.3.1 — CLI safety and memory retrieval fixes

修复 / Fixes

• CLI 数据库路径安全（#39）：保留显式 --db 的真实文件系统语义，避免 symlink/.. 指向错误数据库；修复同类路径下的导出失败与 doctor 路径误报，并保留数据库、别名和 SQLite sidecar 防覆盖保护。
• CLI 命令预检（#40）：未知命令在任何数据库访问前拒绝，不再因拼写错误创建或修改存储。
• 子命令帮助（#41）：--help 不再要求操作参数或打开数据库。
• 检索重排（#42）：采用独立于结果数量的有界候选池，先进行混合重排再截取最终结果，稳定不同 limit 的结果前缀和评分。
• 原生去重输出（#43）：向模型展示命中记录的 ID、revision、正文和相似度，支持依据返回结果安全地执行 CAS 更新。

验证 / Validation

• Node 22 / Node 24 tests and package checks.
• 422 combined regression tests, TypeScript checking, build, and real Cordis boot probe.
• No database schema change from v0.3.0.

Full changelog: v0.3.0...v0.3.1

v0.3.0 — revision CAS and explicit schema upgrade

Revision-aware memory mutations (issue #32, stage 1)

• Add persisted revision to memory records and opt-in expectedRevision compare-and-swap protection for update, confirm, forget and merge. Strict merge validates the target and every source atomically; callers omitting revision arguments keep legacy unprotected behavior.
• Expose revisions and structured mutation errors through tools, CLI and prompt recall. Update/confirm and merge targets increment revisions; deletions remain physical.
• Add explicit, backed-up schema v1 → v2 upgrades, with read-only preflight and locked revalidation. Reject malformed metadata, reusable memory ID schemas, invalid rows and incompatible FTS layouts before writing. Report retained backups even on upgrade lock/open failures.
• Export revision-preserving dsh-ltm-export/2; retain /1 import compatibility with atomic conflict rejection. Validate malformed imports before opening a store.
• Add migration/operator documentation and a Chinese README; harden packed-content checks.

Required database upgrade

Database schema changes from v1 to v2. Normal startup does not migrate automatically, and older plugin releases cannot open schema v2. Stop every process sharing the database, install 0.3.0 for all consumers, then explicitly run:

dsh-ltm --db /absolute/path/to/ltm.db upgrade-schema

This supported command always takes a SQLite-consistent backup before upgrading. Keep its reported backup path private and review the migration guidance before restoring. Restart consumers only after the upgrade succeeds. Do not mix old writers with revision-aware clients: old writers do not increment revisions. This command is for an existing dsh-ltm v1 database, not the separate legacy dsh-memory database.

Verification and scope

363 tests, supported Node 22/24 CI, real Cordis boot probe, and packed-content validation. Additional independent review and adversarial schema checks cover metadata constraints, ID-reuse/ABA, WAL-preserving refusal and post-backup failures.

This release completes only #32 stage 1 via #33. Provenance, evidence invalidation, dispute/review state and history/rollback remain out of scope; #32 stays open. CAS prevents stale-version writes, not factual errors, and does not protect identity across administrative restore/import resets.

v0.2.0 — memory quality diagnostics

What is new

• Read-only dsh-ltm doctor reports long entries, same-scope near duplicates, temporary-state/path cues, and actual recall budget usage without changing the database or exposing memory prose.
• Pinned writes and relevant updates return actual selected, truncated, and omitted memory IDs, using configured scopes and character/token limits.
• Tool guidance favors searching and updating an existing fact instead of appending changed state.
• Packaging CI validates actual build chunks, including renamed shared bundles.

Quality findings are advisory: no automatic cleanup, schema migration, or embeddings. Doctor uses CLI defaults or explicitly supplied configuration, not the running profile.

Verification

184 tests, 40 real Cordis boot checks, 6 packaging regression cases; Node 22/24 and packaging CI passed. Published to npm with provenance via Trusted Publishing.

Installation

dsh plugin add @tr1v3r/dsh-ltm@0.2.0

PRs: #28, #29.

v0.1.2 — one-command plugin installation

Fixes npm installation as a DSH profile bundle: the package now declares dsh.bundle.patch.

Install:

dsh plugin --profile web add @tr1v3r/dsh-ltm@0.1.2

The explicit version avoids pnpm 11 default 24-hour release-age fallback to older bundle-less versions. Strict policies may require approval or waiting.

• Database defaults to $DSH_HOME/memory/ltm.db; restart the profile after installation.
• Disable dsh-memory first if replacing it; remove old manual ltm inserts to avoid duplicate instances. Migration remains explicit.
• No memory schema changes.

Verification: 165 tests; Node 22/24 CI and package checks; real Cordis boot; isolated packed install and public npm install with automatic bundle registration and Chinese write/search. Published through npm Trusted Publishing with provenance.

See README for configuration and migration.