dsh-tdai-memory 0.2.10 → 0.2.11

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 Scorp1o117
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 Scorp1o117
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,130 +1,130 @@
-# dsh-tdai-memory
-
-[![中文文档](https://img.shields.io/badge/%E4%B8%AD%E6%96%87%E6%96%87%E6%A1%A3-blue)](README.zh.md)
-
-**GitHub**: [Scorp1o117/dsh-tdai-memory](https://github.com/Scorp1o117/dsh-tdai-memory) · **npm**: [dsh-tdai-memory](https://www.npmjs.com/package/dsh-tdai-memory)
-
-[![Enhancement Suite](https://img.shields.io/badge/part%20of-Enhancement%20Suite-3964fe)](https://github.com/Scorp1o117/dsh-enhancement-suite) [![npm](https://img.shields.io/npm/v/dsh-enhancement-suite)](https://www.npmjs.com/package/dsh-enhancement-suite)
-
-Part of the [DeepSeek Harness Enhancement Suite](https://github.com/Scorp1o117/dsh-enhancement-suite) — Vision · Soul/Persona · Long-term Memory · Plugin Marketplace.
-
-A port of **TencentDB Agent Memory** (Tencent Cloud's open-source four-layer
-memory system, originally an OpenClaw plugin) into DeepSeek Harness.
-
-## Features
-
-- **L0 conversation capture**: every turn (turn end, request boundary) is
-  written to raw conversation storage (JSONL + SQLite + FTS + vectors)
-- **L1 structured memory**: a background pipeline uses an LLM to extract
-  facts / preferences / events (persona / episodic / instruction) from
-  conversations, stored in `records/` + SQLite + FTS + vectors
-- **L2 scenes / L3 persona**: scene blocks and user profile generation
-  (pipeline-scheduled)
-- **Automatic recall injection**: on every prompt assembly, relevant memories
-  and the user profile are retrieved by the current user message and injected
-  as dynamic context (the model "just remembers")
-- **Tools**: `tdai_memory_search` (L1 structured search),
-  `tdai_conversation_search` (L0 raw-text search)
-
-The data directory reuses the existing `~/.memory-tencentdb/memory-tdai`, so
-**previously accumulated memories carry over seamlessly**.
-
-## Architecture (porting approach)
-
-| Layer | Content |
-|---|---|
-| Core | The host-neutral core of `tdai-memory-openclaw-plugin` (`src/core`, `src/utils`), tsc-compiled to ESM (`dist-dsh/`), zero changes |
-| Host adapter | `StandaloneHostAdapter` (official standalone mode, direct OpenAI-compatible calls) |
-| dsh shell | `index.js`: config mapping, `session/event` + `session/flush` capture, `system-prompt/assemble` recall injection on `agent.ctx`, tool registration, lifecycle |
-| Fallback | `recall-inject.js`: preset-row recall injection (used when mounted inside an agent preset) |
-
-Hard-won wiring details:
-
-- **Capture**: `session/flush` listener (await semantics; must complete before
-  headless exits); `turn/start` timestamps as the L0 cursor floor; turn-id dedup
-- **Headless one-shot runs**: wait for `core.handleSessionEnd()` inside flush
-  (L1 extraction finishes before exit; otherwise the 5s shutdown timeout kills it)
-- **Recall injection**: must be registered on **`agent.ctx`** (assembly runs in
-  the agent scope; root listeners never see it); attach one tick after
-  `session/created` by resolving the agent from the `agents` service
-
-## Configuration (profile patch + settings)
-
-Configuration is **settings-namespace driven**: the profile patch is the base
-layer, and the `tdai-memory:` section of `$DSH_HOME/settings.yaml` overrides it
-(LLM/embedding keys live in settings.yaml). The **Web UI Settings → 记忆**
-section edits every field (v0.2.0, write-only keys); TdaiCore is built at
-startup, so changes apply **after a restart**.
-
-```yaml
-# $DSH_HOME/settings.yaml
-tdai-memory:
-  llm:
-    apiKey: 'sk-...'
-  embedding:
-    apiKey: 'local-no-key'
-```
-
-```yaml
-# profile patch (base layer)
-- id: tdai-memory
-  name: 'dsh-tdai-memory'
-  config:
-    extraction:
-      enabled: true
-      enableDedup: false      # dedup LLM output parsing is flaky; off by default
-    llm:                      # L1/L2/L3 extraction model (OpenAI-compatible)
-      baseUrl: 'https://opencode.ai/zen/go/v1'
-      model: 'mimo-v2.5'      # deepseek-v4-flash produces invalid extraction JSON
-    embedding:                # vectors (OpenAI-compatible /v1/embeddings)
-      baseUrl: 'http://127.0.0.1:8088/v1'
-      model: 'Qwen3-Embedding-0.6B'
-      dimensions: 1024
-      sendDimensions: false
-```
-
-## Install
-
-```bash
-dsh plugin --profile web add dsh-tdai-memory
-```
-
-then mount it in `$DSH_HOME/profiles/web/cordis.patch.yml`:
-
-```yaml
-- insert:
-    - id: tdai-memory
-      name: 'dsh-tdai-memory'
-      config: {}          # keys can live in settings.yaml instead
-```
-
-and restart `dsh web`. LLM/embedding API keys can be set in the Web UI
-settings page (记忆 / Memory) or directly in `settings.yaml` under
-`tdai-memory:`.
-
-> **Note for users**
-> - This plugin is a standard **profile bundle** (`dsh.bundle.patch`):
->   `dsh plugin --profile web add dsh-tdai-memory` installs and mounts it in
->   one step — no manual `cordis.patch.yml` edits needed.
-> - The settings section needs the `dsh-host-apiproxy` namespace allowlist;
->   the plugin patches it automatically on first start — **restart `dsh web`
->   once more** and the section appears. A dsh update overwrites the patch;
->   the next plugin start re-applies it.
-> - Settings changes apply **after a restart** (TdaiCore is built at startup).
-> - Tested against DSH `0.1.0-rc.6`.
-
-## Known trade-offs
-
-- **Extraction model**: `mimo-v2.5` extracts correctly but takes 20-30s per
-  call (background execution, does not block the conversation);
-  `deepseek-v4-flash` is fast but its JSON output is non-compliant (extracts 0)
-- **dedup**: LLM conflict-detection output parsing is unstable (once caused
-  stored=0); off by default; enable only with a more reliable model
-- **L1 memory vectors**: written with storage (8088 embedding is fast); L0
-  vectors run as a background task, drained by `destroy()` on headless exit
-- **Upgrades**: after pulling new upstream code, rerun
-  `npx tsc -p dsh-tsconfig.json` in the tdai project dir (output in `dist-dsh/`)
-
-## License
-
-MIT
+# dsh-tdai-memory
+
+[![中文文档](https://img.shields.io/badge/%E4%B8%AD%E6%96%87%E6%96%87%E6%A1%A3-blue)](README.zh.md)
+
+**GitHub**: [Scorp1o117/dsh-tdai-memory](https://github.com/Scorp1o117/dsh-tdai-memory) · **npm**: [dsh-tdai-memory](https://www.npmjs.com/package/dsh-tdai-memory)
+
+[![Enhancement Suite](https://img.shields.io/badge/part%20of-Enhancement%20Suite-3964fe)](https://github.com/Scorp1o117/dsh-enhancement-suite) [![npm](https://img.shields.io/npm/v/dsh-enhancement-suite)](https://www.npmjs.com/package/dsh-enhancement-suite)
+
+Part of the [DeepSeek Harness Enhancement Suite](https://github.com/Scorp1o117/dsh-enhancement-suite) — Vision · Soul/Persona · Long-term Memory · Plugin Marketplace.
+
+A port of **TencentDB Agent Memory** (Tencent Cloud's open-source four-layer
+memory system, originally an OpenClaw plugin) into DeepSeek Harness.
+
+## Features
+
+- **L0 conversation capture**: every turn (turn end, request boundary) is
+  written to raw conversation storage (JSONL + SQLite + FTS + vectors)
+- **L1 structured memory**: a background pipeline uses an LLM to extract
+  facts / preferences / events (persona / episodic / instruction) from
+  conversations, stored in `records/` + SQLite + FTS + vectors
+- **L2 scenes / L3 persona**: scene blocks and user profile generation
+  (pipeline-scheduled)
+- **Automatic recall injection**: on every prompt assembly, relevant memories
+  and the user profile are retrieved by the current user message and injected
+  as dynamic context (the model "just remembers")
+- **Tools**: `tdai_memory_search` (L1 structured search),
+  `tdai_conversation_search` (L0 raw-text search)
+
+The data directory reuses the existing `~/.memory-tencentdb/memory-tdai`, so
+**previously accumulated memories carry over seamlessly**.
+
+## Architecture (porting approach)
+
+| Layer | Content |
+|---|---|
+| Core | The host-neutral core of `tdai-memory-openclaw-plugin` (`src/core`, `src/utils`), tsc-compiled to ESM (`dist-dsh/`), zero changes |
+| Host adapter | `StandaloneHostAdapter` (official standalone mode, direct OpenAI-compatible calls) |
+| dsh shell | `index.js`: config mapping, `session/event` + `session/flush` capture, `system-prompt/assemble` recall injection on `agent.ctx`, tool registration, lifecycle |
+| Fallback | `recall-inject.js`: preset-row recall injection (used when mounted inside an agent preset) |
+
+Hard-won wiring details:
+
+- **Capture**: `session/flush` listener (await semantics; must complete before
+  headless exits); `turn/start` timestamps as the L0 cursor floor; turn-id dedup
+- **Headless one-shot runs**: wait for `core.handleSessionEnd()` inside flush
+  (L1 extraction finishes before exit; otherwise the 5s shutdown timeout kills it)
+- **Recall injection**: must be registered on **`agent.ctx`** (assembly runs in
+  the agent scope; root listeners never see it); attach one tick after
+  `session/created` by resolving the agent from the `agents` service
+
+## Configuration (profile patch + settings)
+
+Configuration is **settings-namespace driven**: the profile patch is the base
+layer, and the `tdai-memory:` section of `$DSH_HOME/settings.yaml` overrides it
+(LLM/embedding keys live in settings.yaml). The **Web UI Settings → 记忆**
+section edits every field (v0.2.0, write-only keys); TdaiCore is built at
+startup, so changes apply **after a restart**.
+
+```yaml
+# $DSH_HOME/settings.yaml
+tdai-memory:
+  llm:
+    apiKey: 'sk-...'
+  embedding:
+    apiKey: 'local-no-key'
+```
+
+```yaml
+# profile patch (base layer)
+- id: tdai-memory
+  name: 'dsh-tdai-memory'
+  config:
+    extraction:
+      enabled: true
+      enableDedup: false      # dedup LLM output parsing is flaky; off by default
+    llm:                      # L1/L2/L3 extraction model (OpenAI-compatible)
+      baseUrl: 'https://opencode.ai/zen/go/v1'
+      model: 'mimo-v2.5'      # deepseek-v4-flash produces invalid extraction JSON
+    embedding:                # vectors (OpenAI-compatible /v1/embeddings)
+      baseUrl: 'http://127.0.0.1:8088/v1'
+      model: 'Qwen3-Embedding-0.6B'
+      dimensions: 1024
+      sendDimensions: false
+```
+
+## Install
+
+```bash
+dsh plugin --profile web add dsh-tdai-memory
+```
+
+then mount it in `$DSH_HOME/profiles/web/cordis.patch.yml`:
+
+```yaml
+- insert:
+    - id: tdai-memory
+      name: 'dsh-tdai-memory'
+      config: {}          # keys can live in settings.yaml instead
+```
+
+and restart `dsh web`. LLM/embedding API keys can be set in the Web UI
+settings page (记忆 / Memory) or directly in `settings.yaml` under
+`tdai-memory:`.
+
+> **Note for users**
+> - This plugin is a standard **profile bundle** (`dsh.bundle.patch`):
+>   `dsh plugin --profile web add dsh-tdai-memory` installs and mounts it in
+>   one step — no manual `cordis.patch.yml` edits needed.
+> - The settings section needs the `dsh-host-apiproxy` namespace allowlist;
+>   the plugin patches it automatically on first start — **restart `dsh web`
+>   once more** and the section appears. A dsh update overwrites the patch;
+>   the next plugin start re-applies it.
+> - Settings changes apply **after a restart** (TdaiCore is built at startup).
+> - Tested against DSH `0.1.0-rc.6`, `0.1.0-rc.7`, and `0.1.0-rc.8`.
+
+## Known trade-offs
+
+- **Extraction model**: `mimo-v2.5` extracts correctly but takes 20-30s per
+  call (background execution, does not block the conversation);
+  `deepseek-v4-flash` is fast but its JSON output is non-compliant (extracts 0)
+- **dedup**: LLM conflict-detection output parsing is unstable (once caused
+  stored=0); off by default; enable only with a more reliable model
+- **L1 memory vectors**: written with storage (8088 embedding is fast); L0
+  vectors run as a background task, drained by `destroy()` on headless exit
+- **Upgrades**: after pulling new upstream code, rerun
+  `npx tsc -p dsh-tsconfig.json` in the tdai project dir (output in `dist-dsh/`)
+
+## License
+
+MIT

package/README.zh.md

@@ -1,72 +1,72 @@
-# dsh-tdai-memory
-
-**GitHub**: [Scorp1o117/dsh-tdai-memory](https://github.com/Scorp1o117/dsh-tdai-memory) · **npm**: [dsh-tdai-memory](https://www.npmjs.com/package/dsh-tdai-memory) · [English](README.md)
-
-[![Enhancement Suite](https://img.shields.io/badge/part%20of-Enhancement%20Suite-3964fe)](https://github.com/Scorp1o117/dsh-enhancement-suite) [![npm](https://img.shields.io/npm/v/dsh-enhancement-suite)](https://www.npmjs.com/package/dsh-enhancement-suite)
-
-属于 [DeepSeek Harness Enhancement Suite](https://github.com/Scorp1o117/dsh-enhancement-suite) —— Vision · Soul/Persona · 长期记忆 · 插件市场。
-
-把 **TencentDB Agent Memory**（腾讯云开源的四层记忆系统，原为 OpenClaw 插件）移植进 DeepSeek Harness。
-
-## 能力
-
-- **L0 对话捕获**：每轮对话（turn 结束、请求边界）自动写入原始对话（JSONL + SQLite + FTS + 向量）
-- **L1 结构化记忆**：后台管线用 LLM 从对话中提取事实/偏好/事件（persona / episodic / instruction），写入 `records/` + SQLite + FTS + 向量
-- **L2 场景 / L3 画像**：场景块与用户画像生成（管线自动调度）
-- **自动召回注入**：每次组装提示词时，按当前用户消息检索相关记忆 + 画像，作为动态上下文注入（模型"凭空想起"）
-- **工具**：`tdai_memory_search`（L1 结构化检索）、`tdai_conversation_search`（L0 原文检索）
-
-数据目录复用现有 `~/.memory-tencentdb/memory-tdai`，**旧记忆无缝继承**。
-
-## 架构（移植方式）
-
-| 层 | 内容 |
-|---|---|
-| 核心 | `tdai-memory-openclaw-plugin` 的 host-neutral 核心（`src/core`、`src/utils`），tsc 编译为 ESM（`dist-dsh/`），零改动 |
-| 宿主适配 | `StandaloneHostAdapter`（官方 standalone 模式，OpenAI 兼容直调） |
-| dsh 壳 | `index.js`：配置映射、`session/event`+`session/flush` 捕获、`agent.ctx` 上的 `system-prompt/assemble` waterfall 召回注入、工具注册、生命周期 |
-| 备用 | `recall-inject.js`：preset 行形态的召回注入（挂在 agent preset 内时用） |
-
-关键接线（都是踩坑换来的）：
-
-- **捕获**：`session/flush` 监听器（await 语义，headless 退出前必完成）；`turn/start` 时间戳做 L0 cursor 下限；turn id 去重
-- **headless 一次性任务**：flush 内再等 `core.handleSessionEnd()`（L1 提取跑完才退出；否则 5s 关闭超时会杀掉提取）
-- **召回注入**：必须注册在 **`agent.ctx`** 上（组装在 agent 作用域进行，root 监听器收不到）；`session/created` 后延迟一 tick 从 `agents` 服务拿 agent
-
-## 配置（profile patch + settings）
-
-配置以 **settings 命名空间**驱动：profile patch 作为 base 层，`$DSH_HOME/settings.yaml` 的 `tdai-memory:` 节覆盖（LLM/embedding 密钥已迁到 settings.yaml）。Web UI 设置 → 记忆 可编辑全部字段（v0.2.0，含写-only 密钥）；TdaiCore 启动时构建，改动**重启后生效**。
-
-```yaml
-# $DSH_HOME/settings.yaml
-tdai-memory:
-  llm:
-    apiKey: 'sk-...'
-  embedding:
-    apiKey: 'local-no-key'
-```
-
-```yaml
-# profile patch（base 层）
-- id: tdai-memory
-  name: 'dsh-tdai-memory'
-  config:
-    extraction:
-      enabled: true
-      enableDedup: false      # dedup 的 LLM 输出解析不稳，先关
-    llm:                      # L1/L2/L3 提取模型（OpenAI 兼容）
-      baseUrl: 'https://opencode.ai/zen/go/v1'
-      model: 'mimo-v2.5'      # deepseek-v4-flash 对提取 JSON 输出不合格
-    embedding:                # 向量（OpenAI 兼容 /v1/embeddings）
-      baseUrl: 'http://127.0.0.1:8088/v1'
-      model: 'Qwen3-Embedding-0.6B'
-      dimensions: 1024
-      sendDimensions: false
-```
-
-## 已知取舍
-
-- **提取模型**：`mimo-v2.5` 提取正确但单次 20-30s（后台执行，不阻塞对话）；`deepseek-v4-flash` 快但 JSON 输出不合规（提取 0 条）
-- **dedup**：LLM 冲突检测输出解析不稳（曾导致 stored=0），默认关闭；开启需换更稳的模型
-- **L1 记忆向量**：随存储写入（8088 embedding 快）；L0 向量走后台任务，headless 退出时由 `destroy()` drain
-- **升级**：上游拉新代码后，在 tdai 项目目录重跑 `npx tsc -p dsh-tsconfig.json`（产物在 `dist-dsh/`）
+# dsh-tdai-memory
+
+**GitHub**: [Scorp1o117/dsh-tdai-memory](https://github.com/Scorp1o117/dsh-tdai-memory) · **npm**: [dsh-tdai-memory](https://www.npmjs.com/package/dsh-tdai-memory) · [English](README.md)
+
+[![Enhancement Suite](https://img.shields.io/badge/part%20of-Enhancement%20Suite-3964fe)](https://github.com/Scorp1o117/dsh-enhancement-suite) [![npm](https://img.shields.io/npm/v/dsh-enhancement-suite)](https://www.npmjs.com/package/dsh-enhancement-suite)
+
+属于 [DeepSeek Harness Enhancement Suite](https://github.com/Scorp1o117/dsh-enhancement-suite) —— Vision · Soul/Persona · 长期记忆 · 插件市场。
+
+把 **TencentDB Agent Memory**（腾讯云开源的四层记忆系统，原为 OpenClaw 插件）移植进 DeepSeek Harness。
+
+## 能力
+
+- **L0 对话捕获**：每轮对话（turn 结束、请求边界）自动写入原始对话（JSONL + SQLite + FTS + 向量）
+- **L1 结构化记忆**：后台管线用 LLM 从对话中提取事实/偏好/事件（persona / episodic / instruction），写入 `records/` + SQLite + FTS + 向量
+- **L2 场景 / L3 画像**：场景块与用户画像生成（管线自动调度）
+- **自动召回注入**：每次组装提示词时，按当前用户消息检索相关记忆 + 画像，作为动态上下文注入（模型"凭空想起"）
+- **工具**：`tdai_memory_search`（L1 结构化检索）、`tdai_conversation_search`（L0 原文检索）
+
+数据目录复用现有 `~/.memory-tencentdb/memory-tdai`，**旧记忆无缝继承**。
+
+## 架构（移植方式）
+
+| 层 | 内容 |
+|---|---|
+| 核心 | `tdai-memory-openclaw-plugin` 的 host-neutral 核心（`src/core`、`src/utils`），tsc 编译为 ESM（`dist-dsh/`），零改动 |
+| 宿主适配 | `StandaloneHostAdapter`（官方 standalone 模式，OpenAI 兼容直调） |
+| dsh 壳 | `index.js`：配置映射、`session/event`+`session/flush` 捕获、`agent.ctx` 上的 `system-prompt/assemble` waterfall 召回注入、工具注册、生命周期 |
+| 备用 | `recall-inject.js`：preset 行形态的召回注入（挂在 agent preset 内时用） |
+
+关键接线（都是踩坑换来的）：
+
+- **捕获**：`session/flush` 监听器（await 语义，headless 退出前必完成）；`turn/start` 时间戳做 L0 cursor 下限；turn id 去重
+- **headless 一次性任务**：flush 内再等 `core.handleSessionEnd()`（L1 提取跑完才退出；否则 5s 关闭超时会杀掉提取）
+- **召回注入**：必须注册在 **`agent.ctx`** 上（组装在 agent 作用域进行，root 监听器收不到）；`session/created` 后延迟一 tick 从 `agents` 服务拿 agent
+
+## 配置（profile patch + settings）
+
+配置以 **settings 命名空间**驱动：profile patch 作为 base 层，`$DSH_HOME/settings.yaml` 的 `tdai-memory:` 节覆盖（LLM/embedding 密钥已迁到 settings.yaml）。Web UI 设置 → 记忆 可编辑全部字段（v0.2.0，含写-only 密钥）；TdaiCore 启动时构建，改动**重启后生效**。
+
+```yaml
+# $DSH_HOME/settings.yaml
+tdai-memory:
+  llm:
+    apiKey: 'sk-...'
+  embedding:
+    apiKey: 'local-no-key'
+```
+
+```yaml
+# profile patch（base 层）
+- id: tdai-memory
+  name: 'dsh-tdai-memory'
+  config:
+    extraction:
+      enabled: true
+      enableDedup: false      # dedup 的 LLM 输出解析不稳，先关
+    llm:                      # L1/L2/L3 提取模型（OpenAI 兼容）
+      baseUrl: 'https://opencode.ai/zen/go/v1'
+      model: 'mimo-v2.5'      # deepseek-v4-flash 对提取 JSON 输出不合格
+    embedding:                # 向量（OpenAI 兼容 /v1/embeddings）
+      baseUrl: 'http://127.0.0.1:8088/v1'
+      model: 'Qwen3-Embedding-0.6B'
+      dimensions: 1024
+      sendDimensions: false
+```
+
+## 已知取舍
+
+- **提取模型**：`mimo-v2.5` 提取正确但单次 20-30s（后台执行，不阻塞对话）；`deepseek-v4-flash` 快但 JSON 输出不合规（提取 0 条）
+- **dedup**：LLM 冲突检测输出解析不稳（曾导致 stored=0），默认关闭；开启需换更稳的模型
+- **L1 记忆向量**：随存储写入（8088 embedding 快）；L0 向量走后台任务，headless 退出时由 `destroy()` drain
+- **升级**：上游拉新代码后，在 tdai 项目目录重跑 `npx tsc -p dsh-tsconfig.json`（产物在 `dist-dsh/`）

package/THIRD-PARTY-NOTICES.md

@@ -1,20 +1,20 @@
-# Third-party notices
-
-## TencentDB Agent Memory core (vendored in `vendor/tdai`)
-
-`vendor/tdai` is a TypeScript-compiled copy of the host-neutral core of
-[TencentCloud/TencentDB-Agent-Memory](https://github.com/TencentCloud/TencentDB-Agent-Memory)
-(`tdai-memory-openclaw-plugin`, npm: `@tencentdb-agent-memory/memory-tencentdb`),
-compiled with `tsc -p dsh-tsconfig.json` (see the upstream repo for source).
-Its runtime dependencies are declared in this package's `dependencies`.
-
-MIT License — Copyright (c) 2026 TencentCloud
-
-## Runtime dependencies
-
-- `ai` / `@ai-sdk/openai` — Vercel AI SDK (Apache-2.0)
-- `@node-rs/jieba` — Rust jieba bindings (MIT)
-- `sqlite-vec` — vector search extension for SQLite (Apache-2.0 / MIT)
-- `json5` — JSON5 parser (MIT)
-- `undici` — HTTP client (MIT)
-- `@tencentdb-agent-memory/tcvdb-text` — TencentDB text utilities (MIT)
+# Third-party notices
+
+## TencentDB Agent Memory core (vendored in `vendor/tdai`)
+
+`vendor/tdai` is a TypeScript-compiled copy of the host-neutral core of
+[TencentCloud/TencentDB-Agent-Memory](https://github.com/TencentCloud/TencentDB-Agent-Memory)
+(`tdai-memory-openclaw-plugin`, npm: `@tencentdb-agent-memory/memory-tencentdb`),
+compiled with `tsc -p dsh-tsconfig.json` (see the upstream repo for source).
+Its runtime dependencies are declared in this package's `dependencies`.
+
+MIT License — Copyright (c) 2026 TencentCloud
+
+## Runtime dependencies
+
+- `ai` / `@ai-sdk/openai` — Vercel AI SDK (Apache-2.0)
+- `@node-rs/jieba` — Rust jieba bindings (MIT)
+- `sqlite-vec` — vector search extension for SQLite (Apache-2.0 / MIT)
+- `json5` — JSON5 parser (MIT)
+- `undici` — HTTP client (MIT)
+- `@tencentdb-agent-memory/tcvdb-text` — TencentDB text utilities (MIT)