stratagate-dsh 0.2.91 → 0.2.93

package/docs/ARCHITECTURE.md

@@ -179,6 +179,38 @@ Criticality floors in the reference implementation are:
 
 A pinned event has effective weight 1. A superseded event is capped at 0.1. Forgotten and archived events have effective weight 0.
 
+### Recording final-answer use with `recordMemoryUse()`
+
+Call this API after the application has selected the Events used as evidence for an answer. Do not pass every search hit or every memory injected into context. The core method records the application's selection; it does not independently inspect the answer text or perform the retrieval sufficiency assessment. The DSH tool protocol supplies those checks before recording use.
+
+```ts
+// memory is an opened StrataGate instance.
+// Persist these values with the answer operation before attempting the write.
+const usedEventIds = ['event-selected-for-this-answer']; // Existing Event IDs.
+const usageReceiptId = 'answer:stable-answer-id:memory-use';
+
+await memory.recordMemoryUse(
+  { eventIds: usedEventIds },
+  { receiptId: usageReceiptId },
+);
+
+// A retry of the same operation uses the same IDs and receipt.
+await memory.recordMemoryUse(
+  { eventIds: usedEventIds },
+  { receiptId: usageReceiptId },
+);
+```
+
+Replace the example identifiers with the application's actual Event IDs and a stable answer-operation ID. A new answer operation needs a new receipt; a retry must reuse the original receipt rather than generate a new UUID.
+
+- Persistent mode requires a nonempty `receiptId`; whitespace-only IDs are rejected.
+- Reusing a receipt with the same Event IDs, Element IDs, and audit metadata returns without reinforcing again.
+- Reusing it with different IDs or audit metadata throws an error. Keep the original payload when retrying; do not reuse the receipt for a revised evidence selection.
+- Within one call, duplicate IDs are deduplicated. Missing, forgotten, or archived Events are skipped, so callers should submit known eligible IDs.
+- Each eligible Event's internal `mentionCount` increases once and its `lastAdoptedTurn` moves to the current turn. The field counts recorded use, despite its historical name; retrieval alone does not increment it.
+
+`StrataGate.inMemory()` allows calls without a receipt, but these calls have no receipt-based retry deduplication. DSH users do not need to call this API manually. See [the implementation](../packages/core/src/store.ts) for `MemoryUseRefs`, `RecordMemoryUseOptions`, and receipt conflict handling.
+
 ## Retrieval assessment contract
 
 The assessment contract is deliberately small:

package/docs/DSH.md

@@ -215,11 +215,15 @@ For diagnostics, the five most recent successful memory-model responses are reta
 
 ## Compatibility and permissions
 
-Release gates exercise the complete DSH `0.1.2-rc.1` family, `@deepseek-ai/dsh@0.1.5-rc.1`, `@deepseek-ai/dsh@0.1.6-alpha.1`, `@deepseek-ai/dsh@0.1.7-rc.1`, and `@deepseek-ai/dsh@0.1.7-rc.2` on Node `24`, on both Linux and Windows. The 0.1.5 CLI's real dependency tree resolves its internal DSH packages to `0.1.5-rc.2`; the 0.1.6 and 0.1.7 CLIs resolve the tested internal DSH and Session Format packages to their respective versions. The 0.1.7 host also supplies Cordis `4.0.4` and Schemastery `3.18.4`. Optional peers for the DSH `0.1.7` packages now accept `>=0.1.7-rc.1 <0.1.8-0`. Startup still requires one coherent DSH internal version and limits Cordis and Schemastery to compatible patch lines. Later `0.1.7` releases can install without a plugin update, but the release gate only tests the versions listed above; compatibility checks remain advisable after a host upgrade. DSH `0.1.8` is excluded.
+Installation peers and startup checks support the complete DSH `0.2.0` version family: all Alpha, Beta, RC, and stable releases (`>=0.2.0-0 <0.2.1-0`), without enumerating individual prereleases. Previously supported DSH `0.1.2-rc.1`, CLI `0.1.5-rc.1` (internal packages `0.1.5-rc.2`), `0.1.6-alpha.1`, and the `0.1.7` family from rc.1 through stable remain supported. Startup still requires one coherent internal DSH version and compatible Cordis `4.0.x` patches from `4.0.4` and Schemastery `3.18.x` patches from `3.18.4`; older hosts retain their original dependency families. DSH `0.1.8`, `0.2.1`, and their prereleases remain excluded.
 
-DSH core packages are host-provided optional peers. After upgrading a profile that once installed those peers locally, run `dsh plugin --profile <name> exec stratagate-dsh-repair` before starting it. The command moves only the known DSH runtime packages into `.stratagate-runtime-backups` inside that profile and writes a recovery receipt; it does not delete them or touch session data. At startup, a bootstrap resolver also forces StrataGate's own imports through the installation-owned module fallback, then verifies the resolved DSH core family and stops with an actionable error for an unknown host family. On DSH `0.1.5` through `0.1.7`, v0 sessions containing the retired `stratagate/memory-citations` event are copied to a validated v1 generation before the host continues its migration chain. The original v0 log is never modified; a `stratagate-legacy-citations-v1.json` receipt records source/target hashes and recovery instructions.
+Development dependencies are pinned to DSH `0.2.0-rc.2` for reproducible checks. The release-gate matrix is configured to verify the previously listed older hosts plus `0.2.0-rc.1` and `0.2.0-rc.2` on Node `24`, Linux, and Windows. `dshWorkshop.compatibility.dshVersions` records concrete verification hosts; installation compatibility comes from the full peer ranges, so that test list does not restrict future `0.2.0` updates.
 
-DSH 0.1.7 stores plugin configuration in the profile and presents live controls through config forms. StrataGate's chat settings use those forms on 0.1.7 and the older settings service on earlier supported hosts. Changing the structured reasoning effort takes effect on subsequent memory-model calls without a plugin restart.
+On DSH `0.2.0`, the host-owned `dsh-session-format`, `dsh-session-format-catalog`, and `dsh-session-format-v0-to-v1` packages must also match the core DSH version. Mixed or missing Session Format packages stop startup before legacy migration; earlier hosts retain their existing compatibility rules.
+
+DSH core packages are host-provided optional peers. After upgrading a profile that once installed those peers locally, run `dsh plugin --profile <name> exec stratagate-dsh-repair` before starting it. The command moves only the known DSH runtime packages into `.stratagate-runtime-backups` inside that profile and writes a recovery receipt; it does not delete them or touch session data. At startup, a bootstrap resolver also forces StrataGate's own imports through the installation-owned module fallback, then verifies the resolved DSH core family and stops with an actionable error for an unknown host family. On supported DSH `0.1.5`, `0.1.6`, `0.1.7`, and `0.2.0` hosts, v0 sessions containing the retired `stratagate/memory-citations` event are copied to a validated v1 generation before the host continues its migration chain. The original v0 log is never modified; a `stratagate-legacy-citations-v1.json` receipt records source/target hashes and recovery instructions.
+
+DSH 0.1.7 and 0.2.0 store plugin configuration in the profile and present live controls through config forms. StrataGate's chat settings use those forms on 0.1.7 and 0.2.0 and the older settings service on earlier supported hosts. Changing the structured reasoning effort takes effect on subsequent memory-model calls without a plugin restart.
 
 DSH 0.1.6's official DeepSeek profile may enable Session Log request metadata by default, so the Host can include original Session Events in the `dsh_session_log` request field. This metadata is outside the model messages, system prompt, and tool schema and does not indicate that StrataGate compression was bypassed. StrataGate does not alter this DSH-wide setting; users who want it disabled should set `session-log-deepseek.enabled=false` through DSH configuration.
 

package/docs/DSH.zh-CN.md

@@ -187,11 +187,15 @@ config:
 
 ## 兼容性与权限
 
-发布门禁会在 Node `24`、Linux 和 Windows 上测试完整的 DSH `0.1.2-rc.1` 依赖族，以及 `@deepseek-ai/dsh@0.1.5-rc.1`、`@deepseek-ai/dsh@0.1.6-alpha.1`、`@deepseek-ai/dsh@0.1.7-rc.1` 和 `@deepseek-ai/dsh@0.1.7-rc.2`。0.1.5 CLI 的真实依赖树会把内部 DSH 包解析为 `0.1.5-rc.2`；0.1.6 和 0.1.7 CLI 的受测内部 DSH 与 Session Format 包分别解析为对应版本。0.1.7 宿主还提供 Cordis `4.0.4` 和 Schemastery `3.18.4`。插件将 DSH `0.1.7` 内部包的可选 peer 范围放宽到 `>=0.1.7-rc.1 <0.1.8-0`，启动时仍要求它们全部来自同一版本，并限制 Cordis 与 Schemastery 在已知的小版本补丁范围内。未来 `0.1.7` 更新可直接安装，但发布门禁只覆盖上面列出的版本；更新后仍应运行兼容性检查。不包含 `0.1.8`。
+安装声明与启动检查支持整个 DSH `0.2.0` 版本族：全部 Alpha、Beta、RC 和正式版（`>=0.2.0-0 <0.2.1-0`），无需逐个列出预发布版本。此前支持的 DSH `0.1.2-rc.1`、CLI `0.1.5-rc.1`（内部包 `0.1.5-rc.2`）、`0.1.6-alpha.1`，以及从 rc.1 到正式版的 `0.1.7` 仍受支持。启动时仍要求核心 DSH 包来自同一个版本，并限制 Cordis 为 `4.0.x`（从 `4.0.4` 起）、Schemastery 为 `3.18.x`（从 `3.18.4` 起）；早期宿主保留其原有依赖族。`0.1.8`、`0.2.1` 及其预发布版本均不在支持范围内。
 
-DSH 核心包现在都是由宿主提供的可选 peer。若某个 profile 曾在本地安装这些 peer，升级后、启动前运行 `dsh plugin --profile <名称> exec stratagate-dsh-repair`。该命令只会把已知 DSH 运行时包移动到 profile 内的 `.stratagate-runtime-backups` 并写入恢复收据，不会删除包或触碰会话数据。启动时 bootstrap 还会把 StrataGate 自身的 DSH 导入定向到宿主维护的共享模块回退目录，再检查实际解析出的 DSH 核心族；未知宿主会立即给出明确错误并停止，而不是让正文区域空白。对于 DSH `0.1.5` 至 `0.1.7`，含已废弃 `stratagate/memory-citations` 事件的 v0 会话会先复制成经过校验的 v1 代际，再由宿主继续其迁移链；原始 v0 日志不会被修改，并写入 `stratagate-legacy-citations-v1.json` 记录源/目标哈希和恢复说明。
+开发依赖固定为 DSH `0.2.0-rc.2`，保证检查可复现。发布门禁配置在 Node `24`、Linux 和 Windows 上验证此前列出的旧宿主，以及 `0.2.0-rc.1` 和 `0.2.0-rc.2`。`dshWorkshop.compatibility.dshVersions` 记录用于验证的具体宿主；安装兼容性由完整的 peer 版本范围声明，测试版本列表不会限制新的 `0.2.0` 更新。
 
-DSH 0.1.7 将插件配置保存在 profile 中，并通过配置表单提供实时控制。StrataGate 聊天界面中的设置在 0.1.7 使用配置表单，在之前受支持的宿主上继续使用旧设置服务。调整结构化任务的推理力度后，后续记忆模型调用会直接使用新值，无需重启插件。
+在 DSH `0.2.0` 上，由宿主提供的 `dsh-session-format`、`dsh-session-format-catalog` 和 `dsh-session-format-v0-to-v1` 也必须与核心 DSH 包版本一致。Session Format 包混装或缺失时，插件会在旧会话迁移前拒绝启动；早期宿主保留原有兼容规则。
+
+DSH 核心包现在都是由宿主提供的可选 peer。若某个 profile 曾在本地安装这些 peer，升级后、启动前运行 `dsh plugin --profile <名称> exec stratagate-dsh-repair`。该命令只会把已知 DSH 运行时包移动到 profile 内的 `.stratagate-runtime-backups` 并写入恢复收据，不会删除包或触碰会话数据。启动时 bootstrap 还会把 StrataGate 自身的 DSH 导入定向到宿主维护的共享模块回退目录，再检查实际解析出的 DSH 核心族；未知宿主会立即给出明确错误并停止，而不是让正文区域空白。对于受支持的 DSH `0.1.5`、`0.1.6`、`0.1.7` 和 `0.2.0`，含已废弃 `stratagate/memory-citations` 事件的 v0 会话会先复制成经过校验的 v1 代际，再由宿主继续其迁移链；原始 v0 日志不会被修改，并写入 `stratagate-legacy-citations-v1.json` 记录源/目标哈希和恢复说明。
+
+DSH 0.1.7 和 0.2.0 将插件配置保存在 profile 中，并通过配置表单提供实时控制。StrataGate 聊天界面中的设置在 0.1.7 和 0.2.0 使用配置表单，在之前受支持的宿主上继续使用旧设置服务。调整结构化任务的推理力度后，后续记忆模型调用会直接使用新值，无需重启插件。
 
 DSH 0.1.6 的官方 DeepSeek profile 默认可能启用 Session Log 请求元数据，因此宿主可能把原始 Session Event 放入 `dsh_session_log` 请求字段。该元数据不属于模型 messages、system prompt 或 tool schema，不能据此判断 StrataGate 压缩失效。StrataGate 不会修改这一 DSH 全局设置；需要关闭的用户应通过 DSH 配置设置 `session-log-deepseek.enabled=false`。
 

package/docs/EVALUATION.md

@@ -177,3 +177,13 @@ It does not yet support these broader claims:
 - a causal benefit from element cards without disabled/forced/fixed-state ablations.
 
 The next credible milestone is a fixed-state component ablation, followed by the same frozen end-to-end protocol across more conversations and then the full dataset.
+
+## Follow-up validation plan
+
+The following are proposed experiments, not completed results:
+
+1. Hold the model and memory state fixed and ablate short-term display decay and individual retrieval mechanisms. Compare answer accuracy, historical context size, background model input, and total call costs separately.
+2. Give the answering model known-correct source evidence directly. This separates failures to retrieve evidence from reasoning failures that remain when evidence is available.
+3. Repeat the frozen protocol across additional conversations before reporting a full LoCoMo result.
+
+These experiments would help distinguish the contribution of each component from improvements observed between versions that changed multiple components together.

package/docs/EXTERNAL_MEMORY_IMPORT.zh-CN.md

@@ -52,3 +52,48 @@ const result = await memory.importExternalMemory({
 如果外部 AI 仍然返回 Markdown 代码块，`parseExternalMemoryExport()` 会自动去除围栏；其它非 JSON 文本会被拒绝，避免把模型解释误写进记忆。
 
 用于第二阶段裁决的系统提示词可使用 `EXTERNAL_MEMORY_DECIDER_PROMPT_ZH_CN`。它明确规定了五种写入动作的边界，并要求模型只能引用本次 Top-K 结果中的事件 ID。
+
+## 导出常量、格式与解析器
+
+| 入口 | 用途 |
+| --- | --- |
+| `EXTERNAL_MEMORY_EXPORT_PROMPT_ZH_CN` | 交给外部 AI，要求生成 `stratagate.external-memory.v2` JSON |
+| `parseExternalMemoryExport()` | 严格解析导出内容，允许去除 Markdown 代码围栏 |
+| `externalMemoryJsonExtractor` | 将严格 JSON 解析包装为可直接传给核心导入 API 的 extractor |
+| `EXTERNAL_MEMORY_DECIDER_PROMPT_ZH_CN` | 指导裁决模型从 ADD、MERGE、SUPERSEDE、CONFLICT、IGNORE 中选择动作 |
+
+v2 将记忆性质 `memoryKind` 与内容分类 `category` 分开。决定如何导入时，应同时保留原始说法、来源和时间依据；未知日期不应由导出日期补齐。最小接入示例中的 `memory` 是已经打开的 StrataGate 实例，`text` 是外部 AI 返回的内容。
+
+示例里的“有匹配就 MERGE”只展示回调结构，不应直接作为实际裁决策略。检索相关不代表两条记忆属于同一件事；实际接入应结合候选内容和匹配结果决定动作。
+
+## DSH 界面：预览、恢复与确认
+
+DSH 管理界面使用可持久化的导入任务，而不是只调用一次严格解析器：
+
+1. **创建任务并解析。** 保存导入文本，尝试解析候选记忆。合法 JSON 进入逐条处理；解析失败的任务进入 `extracting` 状态，由运行时调用模型尝试恢复候选。
+2. **逐条比较。** 每条候选只与有限数量的本地 Event 比较。核心任务默认 `topK=5`，限制在 1–20；与已有有效记忆或本批次较早候选完全重复的内容会确定性地选择 IGNORE。
+3. **生成处理建议。** 模型决定新增、合并、取代、冲突或忽略。引用仅限本次匹配范围；需要既有目标却没有有效目标的建议会降低置信度。
+4. **确认与提交。** 正常解析的候选在置信度达到当前阈值 0.85 时无需逐项确认；低置信度项需要确认。由不合格 JSON 恢复出来的候选会强制进入确认流程，不能仅凭高置信度自动放行。
+
+严格的 `parseExternalMemoryExport()` / `externalMemoryJsonExtractor` 本身不会调用模型修复 JSON。模型兜底属于 DSH 运行时的任务编排；恢复不出候选时，任务失败并记录错误。
+
+## 进度保存与失败重试
+
+任务保存原始输入、候选列表、已处理数量、逐条决定及错误信息。关闭后重新打开页面可以继续查看任务，不需要重新粘贴原始内容。持久化使用需要通过 `StrataGate.open()` 打开数据库；内存模式不提供进程退出后的保留保证。
+
+核心任务接口分别处理：
+
+- `createExternalMemoryImportJob()`：创建任务并尝试严格解析。
+- `completeExternalMemoryFallback()`：保存运行时模型恢复出的候选。
+- `prepareNextExternalMemoryImport()` / `completeNextExternalMemoryImport()`：准备和保存单条裁决；模型调用在事务外执行。
+- `retryExternalMemoryImportJob()`：将失败任务恢复到解析恢复或逐条处理阶段，保留已保存进度。
+
+这些接口管理任务状态；自定义接入方仍需驱动模型调用和后续提交。重复提交已经完成的候选索引不会再推进一次进度。
+
+## 来源保留与批次撤销
+
+正常导入把原文保存为来源 Block，新 Event 引用该来源。MERGE / SUPERSEDE 创建新的 Event，并维护旧事件状态和关系，不直接覆盖旧事件正文。只为新写入的 Event 安排后续投影任务。
+
+显式撤销是独立操作：`undoExternalMemoryImport(sourceBlockId)` 会移除该批次导入的 Event，清理相应来源关系与派生数据，并按剩余替代关系恢复受影响的旧事件状态。它不等同于权重衰减，也不能理解为仅隐藏导入结果。DSH 界面提供提交后的批次撤销入口。
+
+实现入口：[核心导入与任务状态](../packages/core/src/store.ts)、[格式与提示词](../packages/core/src/external-memory.ts)、[DSH 运行时](../src/runtime.ts)。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "stratagate-dsh",
-  "version": "0.2.91",
+  "version": "0.2.93",
   "description": "Recent conversations stay vivid. Older ones fade into summaries, not oblivion. StrataGate gives DeepSeek Harness six-layer, time-decaying memory, while lasting events and relationships settle into a knowledge graph. Bring your memories from other AIs with you—no need to start over.",
   "type": "module",
   "main": "./dist/index.js",
@@ -119,7 +119,9 @@
         "0.1.5-rc.1",
         "0.1.6-alpha.1",
         "0.1.7-rc.1",
-        "0.1.7-rc.2"
+        "0.1.7-rc.2",
+        "0.2.0-rc.1",
+        "0.2.0-rc.2"
       ]
     },
     "permissions": [
@@ -153,17 +155,17 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "4.0.2 || ~4.0.4",
-    "@deepseek-ai/dsh-agent-default-model": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-client-ui-conversation": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-llm": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-native-command": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-session": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-session-format": "0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-session-format-catalog": "0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-session-format-v0-to-v1": "0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-settings": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-system-prompt": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-tools": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0",
+    "@deepseek-ai/dsh-agent-default-model": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-client-ui-conversation": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-llm": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-native-command": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-session": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-session-format": "0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-session-format-catalog": "0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-session-format-v0-to-v1": "0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-settings": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-system-prompt": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
+    "@deepseek-ai/dsh-tools": "0.1.2-rc.1 || 0.1.5-rc.2 || 0.1.6-alpha.1 || >=0.1.7-rc.1 <0.1.8-0 || >=0.2.0-0 <0.2.1-0",
     "@deepseek-ai/schemastery": "3.18.2 || ~3.18.4"
   },
   "peerDependenciesMeta": {
@@ -209,18 +211,19 @@
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "4.0.4",
-    "@deepseek-ai/dsh": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-agent-default-model": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-ui-conversation": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-llm": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-native-command": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session-format": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session-format-catalog": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session-format-v0-to-v1": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-settings": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-system-prompt": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-tools": "0.1.7-rc.2",
+    "@deepseek-ai/dsh": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-agent-default-model": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-app-boot": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-client-ui-conversation": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-llm": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-native-command": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-session": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-session-format": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-session-format-catalog": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-session-format-v0-to-v1": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-settings": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-system-prompt": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-tools": "0.2.0-rc.2",
     "@deepseek-ai/schemastery": "3.18.4",
     "@types/node": "^22.0.0",
     "cytoscape": "^3.34.1",