dsh-memento 0.5.15 → 0.5.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +13 -1
- package/README-es.md +2 -1
- package/README-hi.md +2 -1
- package/README-pt.md +2 -1
- package/README-zh.md +2 -1
- package/README.md +10 -1
- package/package.json +7 -6
package/CHANGELOG.md
CHANGED
|
@@ -5,7 +5,19 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
-
## [
|
|
8
|
+
## [0.5.17] - 2026-09-24
|
|
9
|
+
### Changed
|
|
10
|
+
|
|
11
|
+
- Move the `@deepseek-ai/dsh-*` pins from `0.1.7-alpha.2` to `0.1.7-rc.1` and re-verify against that host line. `dshWorkshop.compatibility.dshVersions` records `0.1.7-rc.1` alongside the earlier lines, the five READMEs name `dsh-v0.1.7-rc.1`, and the compat workflow installs the `0.1.7-rc.1` host (`@deepseek-ai/dsh`, `dsh-base`, `dsh-headless`). The declared peer ranges and `engines.dsh` are deliberately **unchanged**: the existing four-clause union already admits `0.1.7-rc.1`, and the family convention keeps the declared range wider than the verified line. `0.1.7-rc.1` carries no plugin-facing seam change over `0.1.7-alpha.2` — the host's core packages differ only in their version fields — so no source or test expectation had to change. `pnpm-workspace.yaml` is deliberately unchanged: its `minimumReleaseAgeExclude` rows are a version-exception list rather than pins, and its `overrides` rows pin `cordis`/`cosmokit`/`schemastery`, not the host line.
|
|
12
|
+
|
|
13
|
+
## [0.5.16] - 2026-09-23
|
|
14
|
+
|
|
15
|
+
### Changed
|
|
16
|
+
|
|
17
|
+
- **Re-verified against the `0.1.7-alpha.2` host; the `@deepseek-ai/dsh-*` host pins move to `0.1.7-alpha.2`.** The `alpha.2` wave removes nothing this plugin consumes: the published type surface of every host package it resolves is either byte-identical to `0.1.7-alpha.1` (`@deepseek-ai/cordis` `4.0.3`≡`4.0.4`, `@deepseek-ai/schemastery` `3.18.3`≡`3.18.4`) or strictly additive (`ToolDefinition.projectContent?`, `ClientModuleLoader.importError()`, six added `dsh-client-locale` keys). The wave's only removals are internals no plugin in this family references — `dsh-subprocess-local` privates and its non-entry `bindManagedProcess`, `dsh-client-web` `assertEntriesActive`, `dsh-app-boot`'s `unhandledRejection` event, `dsh-client-ui-plugin-manager` `apply()`, a refined `dsh-client-ui-primitives` `CodeBlock` signature, and the `diff.files.one`/`diff.files.other` locale key pair. Both rulers therefore stay green on the moved pin: `typecheck` against the checkout, `typecheck:ci` against the published `0.1.7-alpha.2` faces.
|
|
18
|
+
- The declared host range is deliberately **unchanged**. It already admits `0.1.7-alpha.2` (`0.1.7-alpha.2` satisfies the `>=0.1.7-0 <0.2.0` clause), and the family convention keeps peer ranges wider than the verified line rather than narrowing them to it; a range is what the manifest accepts, not what has been tested.
|
|
19
|
+
- Repo documentation (`AGENTS.md`), the workspace graph pin (`pnpm-workspace.yaml`) and the published-line workflow pins move with the manifest, so no file still claims the previous line.
|
|
20
|
+
|
|
9
21
|
|
|
10
22
|
## [0.5.15] - 2026-09-22
|
|
11
23
|
|
package/README-es.md
CHANGED
|
@@ -17,6 +17,7 @@
|
|
|
17
17
|
[](https://github.com/PerryLink/dsh-memento/releases)
|
|
18
18
|
[](https://www.npmjs.com/package/dsh-memento)
|
|
19
19
|
[](https://www.npmjs.com/package/dsh-memento)
|
|
20
|
+
[](https://dshfind.com/es/plugins/PerryLink/dsh-memento?ref=badge)
|
|
20
21
|
|
|
21
22
|
[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
|
|
22
23
|
|
|
@@ -28,7 +29,7 @@
|
|
|
28
29
|
|
|
29
30
|
| Surface | Status |
|
|
30
31
|
|---|---|
|
|
31
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
32
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1` (adaptado el 2026-09-22): la línea `0.1.7` sustituyó toda la superficie de registro de ajustes (`installSettingsSection` / `SettingsProvider.installSection` / `SettingsNamespace` / `SettingsScope`) por formularios de config en vivo, así que ambas mitades siguen el contrato nuevo — el namespace de un formulario es el id de la entrada del perfil (`memento`), sus campos editables son los marcados `.volatile()` y una edición aceptada se confirma **dentro del plugin en ejecución** en lugar de remontarlo. La mitad de navegador lee ese formulario con `ctx.configForms.get(entryId)` (el servicio `ctx.settingsScope` ya no existe). Ambas mitades conservan sus ramas `installSection` / `settingsScope` para las líneas `0.1.2-rc.1`, `0.1.5-alpha.1` y `0.1.6-0` que el rango de peers sigue anunciando, y la nueva cláusula `>=0.1.7-0 <0.2.0` es lo que hace instalable al propio host objetivo (el rango anterior lo excluía por la regla de semver sobre versiones preliminares). Sigue sin haber superficie de registro de eventos para plugins — `KNOWN_SESSION_EVENT_TYPES` no incluye `memory/*` y el tercer argumento de `Session.append` solo lleva un `SurfaceIntent` para tipos de superficie, así que la puerta de auditoría sigue siendo adaptativa y se salta igual (lo dice una vez por proceso y en `/memory audit`). La evidencia de tipos viene de tres caras: los tipos ya compilados del checkout local, la línea publicada fijada en `node_modules` y la mitad de navegador bajo una lib DOM. |
|
|
32
33
|
| Node | `^22.19.0 || >=24.0.0` |
|
|
33
34
|
| Platforms | Windows / macOS / Linux (solo host; sin código nativo, sin red) |
|
|
34
35
|
| Model | Cualquiera |
|
package/README-hi.md
CHANGED
|
@@ -17,6 +17,7 @@
|
|
|
17
17
|
[](https://github.com/PerryLink/dsh-memento/releases)
|
|
18
18
|
[](https://www.npmjs.com/package/dsh-memento)
|
|
19
19
|
[](https://www.npmjs.com/package/dsh-memento)
|
|
20
|
+
[](https://dshfind.com/hi/plugins/PerryLink/dsh-memento?ref=badge)
|
|
20
21
|
|
|
21
22
|
[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
|
|
22
23
|
|
|
@@ -28,7 +29,7 @@
|
|
|
28
29
|
|
|
29
30
|
| Surface | Status |
|
|
30
31
|
|---|---|
|
|
31
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
32
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1` (2026-09-22 को अनुकूलित): `0.1.7` लाइन ने पूरी सेटिंग्स पंजीकरण सतह (`installSettingsSection` / `SettingsProvider.installSection` / `SettingsNamespace` / `SettingsScope`) को लाइव कॉन्फ़िग फ़ॉर्म से बदल दिया, इसलिए दोनों आधे नया अनुबंध अपनाते हैं — फ़ॉर्म का namespace प्रोफ़ाइल प्रविष्टि की id (`memento`) है, संपादन-योग्य फ़ील्ड `.volatile()` वाले हैं, और स्वीकृत संपादन प्लगइन को रीमाउंट करने के बजाय **चल रहे प्लगइन में** लागू होता है। ब्राउज़र आधा वही फ़ॉर्म `ctx.configForms.get(entryId)` से पढ़ता है (`ctx.settingsScope` सेवा हट चुकी है)। दोनों आधे `installSection` / `settingsScope` शाखाएँ उन `0.1.2-rc.1`, `0.1.5-alpha.1` और `0.1.6-0` लाइनों के लिए बनाए रखते हैं जिन्हें peer रेंज अब भी घोषित करती है, और नई `>=0.1.7-0 <0.2.0` शर्त ही लक्ष्य होस्ट को स्थापित-योग्य बनाती है (पुरानी रेंज semver के प्रीरिलीज़ नियम से उसे बाहर कर देती थी)। प्लगइन इवेंट पंजीकरण सतह अब भी नहीं है — `KNOWN_SESSION_EVENT_TYPES` में `memory/*` नहीं है, और `Session.append` का तीसरा तर्क केवल सरफ़ेस-योग्य प्रकारों के लिए `SurfaceIntent` ले जाता है, इसलिए ऑडिट द्वार अनुकूली रहता है और पहले जैसे छोड़ देता है (यह प्रति प्रोसेस एक बार और `/memory audit` में बताता है)। टाइप प्रमाण तीन फ़ेस से आता है: स्थानीय checkout के बने टाइप, `node_modules` में पिन की गई प्रकाशित लाइन, और DOM लाइब्रेरी के अंतर्गत ब्राउज़र आधा। |
|
|
32
33
|
| Node | `^22.19.0 || >=24.0.0` |
|
|
33
34
|
| Platforms | Windows / macOS / Linux (केवल host; कोई नेटिव कोड नहीं, कोई नेटवर्क नहीं) |
|
|
34
35
|
| Model | कोई भी |
|
package/README-pt.md
CHANGED
|
@@ -17,6 +17,7 @@
|
|
|
17
17
|
[](https://github.com/PerryLink/dsh-memento/releases)
|
|
18
18
|
[](https://www.npmjs.com/package/dsh-memento)
|
|
19
19
|
[](https://www.npmjs.com/package/dsh-memento)
|
|
20
|
+
[](https://dshfind.com/pt/plugins/PerryLink/dsh-memento?ref=badge)
|
|
20
21
|
|
|
21
22
|
[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
|
|
22
23
|
|
|
@@ -28,7 +29,7 @@
|
|
|
28
29
|
|
|
29
30
|
| Surface | Status |
|
|
30
31
|
|---|---|
|
|
31
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
32
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1` (adaptado em 2026-09-22): a linha `0.1.7` substituiu toda a superfície de registro de configurações (`installSettingsSection` / `SettingsProvider.installSection` / `SettingsNamespace` / `SettingsScope`) por formulários de config ao vivo, então as duas metades seguem o contrato novo — o namespace de um formulário é o id da entrada do perfil (`memento`), seus campos editáveis são os marcados `.volatile()` e uma edição aceita é confirmada **dentro do plugin em execução** em vez de remontá-lo. A metade de navegador lê esse formulário por `ctx.configForms.get(entryId)` (o serviço `ctx.settingsScope` deixou de existir). As duas metades mantêm seus ramos `installSection` / `settingsScope` para as linhas `0.1.2-rc.1`, `0.1.5-alpha.1` e `0.1.6-0` que o intervalo de peers ainda anuncia, e a nova cláusula `>=0.1.7-0 <0.2.0` é o que torna o próprio host alvo instalável (o intervalo antigo o excluía pela regra de semver para versões preliminares). Ainda não há superfície de registro de eventos para plugins — `KNOWN_SESSION_EVENT_TYPES` não inclui `memory/*` e o terceiro argumento de `Session.append` só carrega um `SurfaceIntent` para tipos de superfície, então a porta de auditoria continua adaptativa e pula como antes (diz isso uma vez por processo e em `/memory audit`). A evidência de tipos vem de três faces: os tipos já compilados do checkout local, a linha publicada fixada em `node_modules` e a metade de navegador sob uma lib DOM. |
|
|
32
33
|
| Node | `^22.19.0 || >=24.0.0` |
|
|
33
34
|
| Platforms | Windows / macOS / Linux (somente host; sem código nativo, sem rede) |
|
|
34
35
|
| Model | Qualquer |
|
package/README-zh.md
CHANGED
|
@@ -17,6 +17,7 @@
|
|
|
17
17
|
[](https://github.com/PerryLink/dsh-memento/releases)
|
|
18
18
|
[](https://www.npmjs.com/package/dsh-memento)
|
|
19
19
|
[](https://www.npmjs.com/package/dsh-memento)
|
|
20
|
+
[](https://dshfind.com/zh/plugins/PerryLink/dsh-memento?ref=badge)
|
|
20
21
|
|
|
21
22
|
[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
|
|
22
23
|
|
|
@@ -28,7 +29,7 @@
|
|
|
28
29
|
|
|
29
30
|
| Surface | Status |
|
|
30
31
|
|---|---|
|
|
31
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
32
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1`（2026-09-22 适配）：`0.1.7` 线把整条设置注册面（`installSettingsSection` / `SettingsProvider.installSection` / `SettingsNamespace` / `SettingsScope`）换成 live config 表单——表单的 namespace 就是 profile entry id（`memento`），可编辑字段就是标了 `.volatile()` 的那些，被接受的编辑**提交进运行中的插件**而不是重挂它。浏览器半经 `ctx.configForms.get(entryId)` 读同一份表单（`ctx.settingsScope` 服务已删）。两侧都保留了 `installSection` / `settingsScope` 分支，peer 区间仍声明支持 `0.1.2-rc.1`、`0.1.5-alpha.1`、`0.1.6-0` 三条线；新增的 `>=0.1.7-0 <0.2.0` 这一段是修 bug——旧范围按 semver 预发布规则把目标宿主本身排除在外。仍无插件事件注册面——`KNOWN_SESSION_EVENT_TYPES` 不含 `memory/*`，且 `Session.append` 第三参只承载 surface 类型的 `SurfaceIntent`，故审计门保持自适应、行为不变（会在进程内告警一次，并在 `/memory audit` 输出里明示缺口）。类型证据来自三个面：本机 checkout 的已构建类型、`node_modules` 里钉住的已发布线、以及 DOM 库下的浏览器半侧。 |
|
|
32
33
|
| Node | `^22.19.0 || >=24.0.0` |
|
|
33
34
|
| Platforms | Windows / macOS / Linux（纯 host；无原生代码、无网络） |
|
|
34
35
|
| Model | 任意 |
|
package/README.md
CHANGED
|
@@ -3,6 +3,7 @@
|
|
|
3
3
|
# dsh-memento
|
|
4
4
|
- **1024 store channel**: `npm i -g dsh1024` once, then `dsh1024 plugin --profile web add dsh-memento` (counts toward the [deepseek1024.com](https://deepseek1024.com) install ranking).
|
|
5
5
|
[](https://gitee.com/perrylink/dsh-memento)
|
|
6
|
+
[](https://dshfind.com/plugins/PerryLink/dsh-memento?ref=badge)
|
|
6
7
|
[](https://api.securityscorecards.dev/projects/github.com/PerryLink/dsh-memento)
|
|
7
8
|
|
|
8
9
|
**Bounded, layered, approval-gated, auditable cross-session memory for DeepSeek Harness.**
|
|
@@ -25,11 +26,19 @@
|
|
|
25
26
|
|
|
26
27
|
---
|
|
27
28
|
|
|
29
|
+
<!-- star-cta -->
|
|
30
|
+
## ⭐ 如果它帮到了你
|
|
31
|
+
|
|
32
|
+
这个插件是 [DSH 插件家族](https://github.com/PerryLink)的一员（40+ 个，全部 Apache-2.0）。如果你在用，**给个 star** —— 它不会解锁任何功能，但会让下一个人在搜索里更容易找到它。
|
|
33
|
+
|
|
34
|
+
*English:* part of a 40+ plugin family for DeepSeek Harness. If it is useful, **a star helps the next person find it** — nothing is gated behind it.
|
|
35
|
+
|
|
36
|
+
|
|
28
37
|
## Compatibility
|
|
29
38
|
|
|
30
39
|
| Surface | Status |
|
|
31
40
|
|---|---|
|
|
32
|
-
| Harness | DeepSeek Harness `dsh-v0.1.7-
|
|
41
|
+
| Harness | DeepSeek Harness `dsh-v0.1.7-rc.1` (adapted 2026-09-22): the `0.1.7` line replaced the whole settings registration surface (`installSettingsSection` / `SettingsProvider.installSection` / `SettingsNamespace` / `SettingsScope`) with live Config forms, so both halves follow the new contract — a form's namespace is the profile entry id (`memento`), its editable fields are the `.volatile()` ones, and an accepted edit is committed into the running plugin instead of remounting it. The browser half reads that form through `ctx.configForms.get(entryId)` (the `ctx.settingsScope` service is gone). Both halves keep their `installSection` / `settingsScope` branches for the `0.1.2-rc.1`, `0.1.5-alpha.1` and `0.1.6-0` lines the peer range still advertises, and the new `>=0.1.7-0 <0.2.0` clause is what makes the target host itself installable (the old range excluded it by semver's prerelease rule). Still no plugin event-registration surface — `KNOWN_SESSION_EVENT_TYPES` does not carry `memory/*`, and `Session.append`'s third argument only carries a `SurfaceIntent` for surface-eligible types, so the audit gate stays adaptive and skips as before (it says so once per process and in `/memory audit`). Type evidence comes from three faces: the local checkout's built types, the pinned published line in `node_modules`, and the browser half under a DOM lib. |
|
|
33
42
|
| Node | `^22.19.0 || >=24.0.0` |
|
|
34
43
|
| Platforms | Windows / macOS / Linux (pure host; no native code, no network) |
|
|
35
44
|
| Model | Any |
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dsh-memento",
|
|
3
3
|
"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",
|
|
4
|
-
"version": "0.5.
|
|
4
|
+
"version": "0.5.17",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./index.mjs",
|
|
7
7
|
"types": "./types.d.ts",
|
|
@@ -94,7 +94,8 @@
|
|
|
94
94
|
"dshVersions": [
|
|
95
95
|
"0.1.2-rc.1",
|
|
96
96
|
"0.1.5-rc.2",
|
|
97
|
-
"0.1.7-alpha.
|
|
97
|
+
"0.1.7-alpha.2",
|
|
98
|
+
"0.1.7-rc.1"
|
|
98
99
|
]
|
|
99
100
|
},
|
|
100
101
|
"capability": {
|
|
@@ -118,13 +119,13 @@
|
|
|
118
119
|
"@deepseek-ai/schemastery": "^3.18.3"
|
|
119
120
|
},
|
|
120
121
|
"devDependencies": {
|
|
121
|
-
"@deepseek-ai/dsh-attachment": "0.1.7-
|
|
122
|
+
"@deepseek-ai/dsh-attachment": "0.1.7-rc.1",
|
|
122
123
|
"@deepseek-ai/cordis": "^4.0.3",
|
|
123
124
|
"@deepseek-ai/cordis-plugin-include": "^1.0.8",
|
|
124
125
|
"@deepseek-ai/cordis-plugin-loader": "^1.0.4",
|
|
125
|
-
"@deepseek-ai/dsh-session": "0.1.7-
|
|
126
|
-
"@deepseek-ai/dsh-settings": "0.1.7-
|
|
127
|
-
"@deepseek-ai/dsh-tools": "0.1.7-
|
|
126
|
+
"@deepseek-ai/dsh-session": "0.1.7-rc.1",
|
|
127
|
+
"@deepseek-ai/dsh-settings": "0.1.7-rc.1",
|
|
128
|
+
"@deepseek-ai/dsh-tools": "0.1.7-rc.1",
|
|
128
129
|
"@deepseek-ai/schemastery": "^3.18.3",
|
|
129
130
|
"@types/node": "^26.2.0",
|
|
130
131
|
"oxlint": "^0.18.1",
|