dsh-memento 0.4.3 → 0.4.4

package/CHANGELOG.md

@@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.4.4] - 2026-08-22
+
+### Changed
+
+- DeepSeek Harness compatibility baseline raised to **0.1.1-rc.2**: `@deepseek-ai/dsh-session` / `@deepseek-ai/dsh-tools` dev dependencies pinned to `0.1.1-rc.2`, `dshWorkshop.compatibility.dshVersions` updated to `["0.1.1-rc.2"]`, and the `compat.yml` probe pins raised to `0.1.1-rc.2`. Peer ranges stay `>=0.1.0-rc.8 <0.2.0` (no rc.2-only API is required).
+- Adaptive session-event gate re-verified on rc.2 and kept closed: rc.2 still ships no plugin event registration surface (`KNOWN_SESSION_EVENT_TYPES` has no `memory/*`) and `Session.append` still offers no writer-side `ignorable` marker (its third arg is surface intent only), so appending unregistered types would still make a session unloadable. The two-arg `session.append(type, data)` shape remains correct for non-surface events. Comments in `index.mjs` / `types.d.ts` / `AGENTS.md` and the five-language READMEs now record this rc.2 verification. All gates pass against rc.2 (141 tests, protocol conformance 22/22, typecheck, lint, coverage, five-language README check, self-contained/artifact verification).
+
 ## [0.4.3] - 2026-08-21
 
 ### Changed

package/README.es.md

@@ -24,7 +24,7 @@
 
 | Surface | Status |
 |---|---|
-| Harness | DeepSeek Harness `0.1.0-rc.6` |
+| Harness | DeepSeek Harness `0.1.1-rc.2` |
 | Node | `^22.19.0 || >=24.0.0` |
 | Platforms | Windows / macOS / Linux (solo host; sin código nativo, sin red) |
 | Model | Cualquiera |
@@ -151,7 +151,7 @@ El nombre es **`dsh-memento`** (publicado en npm y GitHub). No `dsh-recall` (con
 
 ## Known limitations
 
-- **Los eventos de sesión están declarados, aún no emitidos (rc.6).** `memory/added|updated|removed|recalled|snapshot` están declarados por fusión, pero rc.6 no tiene superficie de registro para tipos de evento fuera del repo; la emisión se activa cuando una build del harness los registre.
+- **Los eventos de sesión están declarados, aún no emitidos (rc.2).** `memory/added|updated|removed|recalled|snapshot` están declarados por fusión, pero rc.2 no tiene superficie de registro para tipos de evento fuera del repo; la emisión se activa cuando una build del harness los registre.
 - **La política `ask` necesita un answerer.** Sin un answerer UI/ACP compuesto, las escrituras fallan cerradas.
 - **Sin indexado FTS5.** La búsqueda por subcadena usa `instr` insensible a mayúsculas (correcto para CJK).
 

package/README.hi.md

@@ -24,7 +24,7 @@
 
 | Surface | Status |
 |---|---|
-| Harness | DeepSeek Harness `0.1.0-rc.6` |
+| Harness | DeepSeek Harness `0.1.1-rc.2` |
 | Node | `^22.19.0 || >=24.0.0` |
 | Platforms | Windows / macOS / Linux (केवल host; कोई नेटिव कोड नहीं, कोई नेटवर्क नहीं) |
 | Model | कोई भी |
@@ -151,7 +151,7 @@ dsh --profile web --dump-config | grep -A3 'id: memento'
 
 ## Known limitations
 
-- **सत्र घटनाएँ घोषित हैं, अभी उत्सर्जित नहीं (rc.6)।** `memory/added|updated|removed|recalled|snapshot` मर्ज-घोषित हैं, परंतु rc.6 में रेपो-बाहर घटना प्रकारों के लिए कोई पंजीकरण सतह नहीं है; harness बिल्ड उन्हें पंजीकृत करते ही उत्सर्जन चालू हो जाता है।
+- **सत्र घटनाएँ घोषित हैं, अभी उत्सर्जित नहीं (rc.2)।** `memory/added|updated|removed|recalled|snapshot` मर्ज-घोषित हैं, परंतु rc.2 में रेपो-बाहर घटना प्रकारों के लिए कोई पंजीकरण सतह नहीं है; harness बिल्ड उन्हें पंजीकृत करते ही उत्सर्जन चालू हो जाता है।
 - **`ask` नीति को answerer चाहिए।** बिना UI/ACP answerer के, लेखन बंद-विफल होते हैं।
 - **कोई FTS5 अनुक्रमण नहीं।** सबस्ट्रिंग खोज केस-असंवेदी `instr` पर चलती है (CJK के लिए सही)।
 

package/README.md

@@ -1,6 +1,7 @@
 <div align="center">
 
 # dsh-memento
+[![Gitee](https://img.shields.io/badge/Gitee-mirror-c71d23?logo=gitee)](https://gitee.com/perrylink/dsh-memento)
 
 **Bounded, layered, approval-gated, auditable cross-session memory for DeepSeek Harness.**
 
@@ -24,7 +25,7 @@
 
 | Surface | Status |
 |---|---|
-| Harness | DeepSeek Harness `0.1.0-rc.6` |
+| Harness | DeepSeek Harness `0.1.1-rc.2` |
 | Node | `^22.19.0 || >=24.0.0` |
 | Platforms | Windows / macOS / Linux (pure host; no native code, no network) |
 | Model | Any |
@@ -151,7 +152,7 @@ The name is **`dsh-memento`** (published on npm and GitHub). Not `dsh-recall` (c
 
 ## Known limitations
 
-- **Session events are declared, not yet emitted (rc.6).** `memory/added|updated|removed|recalled|snapshot` are merge-declared, but rc.6 has no registration surface for out-of-repo event types; emission turns on once a harness build registers them.
+- **Session events are declared, not yet emitted (rc.2).** `memory/added|updated|removed|recalled|snapshot` are merge-declared, but rc.2 has no registration surface for out-of-repo event types; emission turns on once a harness build registers them.
 - **`ask` policy needs an answerer.** With no UI/ACP answerer composed, writes fail closed.
 - **No FTS5 indexing.** Substring search runs on case-insensitive `instr` (correct for CJK).
 

package/README.pt.md

@@ -24,7 +24,7 @@
 
 | Surface | Status |
 |---|---|
-| Harness | DeepSeek Harness `0.1.0-rc.6` |
+| Harness | DeepSeek Harness `0.1.1-rc.2` |
 | Node | `^22.19.0 || >=24.0.0` |
 | Platforms | Windows / macOS / Linux (somente host; sem código nativo, sem rede) |
 | Model | Qualquer |
@@ -151,7 +151,7 @@ O `dsh-memento` é o ensaio comunitário do protocolo de memória DSH — uma fo
 
 ## Known limitations
 
-- **Eventos de sessão declarados, ainda não emitidos (rc.6).** `memory/added|updated|removed|recalled|snapshot` são declarados por fusão, mas o rc.6 não tem superfície de registro para tipos de evento fora do repo; a emissão é ativada quando uma build do harness os registrar.
+- **Eventos de sessão declarados, ainda não emitidos (rc.2).** `memory/added|updated|removed|recalled|snapshot` são declarados por fusão, mas o rc.2 não tem superfície de registro para tipos de evento fora do repo; a emissão é ativada quando uma build do harness os registrar.
 - **A política `ask` precisa de um answerer.** Sem um answerer UI/ACP composto, as escritas falham fechadas.
 - **Sem indexação FTS5.** A busca por substring usa `instr` insensível a maiúsculas (correto para CJK).
 

package/README.zh.md

@@ -24,7 +24,7 @@
 
 | Surface | Status |
 |---|---|
-| Harness | DeepSeek Harness `0.1.0-rc.6` |
+| Harness | DeepSeek Harness `0.1.1-rc.2` |
 | Node | `^22.19.0 || >=24.0.0` |
 | Platforms | Windows / macOS / Linux（纯 host；无原生代码、无网络） |
 | Model | 任意 |
@@ -151,7 +151,7 @@ dsh --profile web --dump-config | grep -A3 'id: memento'
 
 ## Known limitations
 
-- **会话事件已声明、尚未发出（rc.6）。** `memory/added|updated|removed|recalled|snapshot` 已合并声明，但 rc.6 没有仓库外事件类型的注册面；一旦 harness 构建收录这些类型即自动开启发出。
+- **会话事件已声明、尚未发出（rc.2）。** `memory/added|updated|removed|recalled|snapshot` 已合并声明，但 rc.2 没有仓库外事件类型的注册面；一旦 harness 构建收录这些类型即自动开启发出。
 - **`ask` 策略需要 answerer。** 未组合 UI/ACP answerer 时，写入失败关闭。
 - **无 FTS5 索引。** 子串搜索走大小写不敏感的 `instr`（对 CJK 正确）。
 

package/index.mjs

@@ -219,10 +219,10 @@ async function askApproval(approval, payload, write) {
  * Session.append 无法标记 ignorable）：append 未注册类型会让该会话下次加载
  * 被持久化层拒绝。因此默认跳过，审计由审批审计对 + 审计表承担；未来 harness
  * 收录 memory/* 进已知集合后自动开启。
- * rc.8 复核（2026-08-21）：读取端已有 ignorable 信封容忍未知类型，但
- * Session.append 写入面仍不接受 ignorable 标记、插件事件注册面仍被官方
- * 推迟（known-event-types 生成文件明文说明），故本门在 rc.8 下保持关闭，
- * 行为不变。
+ * rc.2 复核（2026-08-22）：KNOWN_SESSION_EVENT_TYPES 仍不含 memory/*，
+ * Session.append 写入面仍只接受 surface intent 可选参（非 surface 类型
+ * 保持两参调用形态）、仍无 writer 侧 ignorable 标记；读取端已有 ignorable
+ * 信封容忍未知类型。故本门在 rc.2 下保持关闭，行为不变。
  * @param {{append?: (type: string, data: object) => unknown} | null | undefined} session - Session。
  * @param {string} type - 事件类型。
  * @param {object} data - 载荷。

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-memento",
   "description": "Bounded, layered, approval-gated, auditable cross-session memory for DeepSeek Harness — a capability seam (ctx.memory service + local SQLite provider + memory tool + frozen snapshot injection), not another memory warehouse",
-  "version": "0.4.3",
+  "version": "0.4.4",
   "type": "module",
   "main": "./index.mjs",
   "types": "./types.d.ts",
@@ -87,7 +87,7 @@
     ],
     "compatibility": {
       "dshVersions": [
-        "0.1.0-rc.8"
+        "0.1.1-rc.2"
       ]
     },
     "capability": {
@@ -113,8 +113,8 @@
     "@deepseek-ai/cordis": "^4.0.1",
     "@deepseek-ai/cordis-plugin-include": "^1.0.6",
     "@deepseek-ai/cordis-plugin-loader": "^1.0.2",
-    "@deepseek-ai/dsh-session": "0.1.0-rc.8",
-    "@deepseek-ai/dsh-tools": "0.1.0-rc.8",
+    "@deepseek-ai/dsh-session": "0.1.1-rc.2",
+    "@deepseek-ai/dsh-tools": "0.1.1-rc.2",
     "@deepseek-ai/schemastery": ">=3.0.0",
     "@types/node": "^26.2.0",
     "oxlint": "^0.18.1",

package/types.d.ts

@@ -4,7 +4,7 @@
 // - `declare module '@deepseek-ai/cordis'`：ctx.memory 服务（F1，三角色 seam 的
 //   Service Definition 面）。
 // - `declare module '@deepseek-ai/dsh-session'`：memory/* 会话事件词汇（F7）。
-//   rc.8 复核（2026-08-21）：harness 仍无插件事件注册面
+//   rc.2 复核（2026-08-22）：harness 仍无插件事件注册面
 //   （KNOWN_SESSION_EVENT_TYPES 不含 memory/*，Session.append 写入面也仍不接受
 //   ignorable 标记），运行时按已知集合自适应派发——未被 harness 收录时跳过
 //   append，审计由审批审计对 + 插件审计表承担；词汇与载荷形状在本文件定死，
@@ -202,7 +202,7 @@ declare module '@deepseek-ai/dsh-session' {
     /**
      * 一条记忆条目已落盘（审批通过后的写成功）。日志只读事件，非 surface；
      * 审计链 = approval/asked + approval/decided + 本事件 + 插件审计表。
-     * rc.8 无插件事件注册面时运行时跳过 append（见 types.d.ts 头注）。
+     * rc.2 无插件事件注册面时运行时跳过 append（见 types.d.ts 头注）。
      */
     'memory/added': {
       entry: MemoryEntry