@omdp/dsh-archived-sessions 0.3.6 → 0.3.8
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/README.md +47 -13
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# @omdp/dsh-archived-sessions
|
|
2
2
|
|
|
3
|
-
> Archived-sessions manager for the DeepSeek Harness web UI — fork of [`@muwinds/dsh-archived-sessions`](https://github.com/MuWinds/dsh-archived-sessions) (0.2.0), adapted for DSH **0.1.5-rc.1** through **0.
|
|
3
|
+
> Archived-sessions manager for the DeepSeek Harness web UI — fork of [`@muwinds/dsh-archived-sessions`](https://github.com/MuWinds/dsh-archived-sessions) (0.2.0), adapted for DSH **0.1.5-rc.1** through **0.2.0-rc.1**.
|
|
4
4
|
|
|
5
|
-
DSH 归档会话管理:在 设置 → 归档会话管理 中查看、释放、删除已归档会话(支持按树删除子会话、清理孤儿会话)。自 0.3.4 起与 DSH 0.1.6 内置的「已归档会话」设置页共存、互不冲突。0.3.6 起 `ctx.shell` 双时代自适应(`run()` / `execute()`),**0.1.5-rc.1 → 0.1.7-rc.1
|
|
5
|
+
DSH 归档会话管理:在 设置 → 归档会话管理 中查看、释放、删除已归档会话(支持按树删除子会话、清理孤儿会话)。自 0.3.4 起与 DSH 0.1.6 内置的「已归档会话」设置页共存、互不冲突。0.3.6 起 `ctx.shell` 双时代自适应(`run()` / `execute()`),**0.1.5-rc.1 → 0.2.0-rc.1 全区间删除可用**(0.3.7 追加 rc.2 声明、0.3.8 追加 0.2.0-rc.1 声明)。
|
|
6
6
|
|
|
7
7
|
[English](#english) · [中文](#中文)
|
|
8
8
|
|
|
@@ -48,8 +48,8 @@ pnpm add @omdp/dsh-archived-sessions -w
|
|
|
48
48
|
|
|
49
49
|
### 要求 / Requirements
|
|
50
50
|
|
|
51
|
-
- DeepSeek Harness **0.1.5-rc.1**、**0.1.5-rc.2**、**0.1.6-alpha.1**、**0.1.7-rc.1**(实测版本;**0.3.6
|
|
52
|
-
- `@deepseek-ai/dsh` `0.1.7-rc.1`(peer,逐版本枚举,0.3.6
|
|
51
|
+
- DeepSeek Harness **0.1.5-rc.1**、**0.1.5-rc.2**、**0.1.6-alpha.1**、**0.1.7-rc.1**、**0.1.7-rc.2**、**0.2.0-rc.1**(实测版本;**0.3.6 起全兼容**,0.3.7 追加 rc.2 声明、0.3.8 追加 0.2.0-rc.1,0.3.5 与 0.1.5/0.1.6 系列**静默不兼容**——见变更记录)
|
|
52
|
+
- `@deepseek-ai/dsh` `0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1`(peer,逐版本枚举,0.3.6 起新增、0.3.7 追加 rc.2、0.3.8 追加 0.2.0-rc.1;语义见下方「兼容性门禁」)
|
|
53
53
|
- `@deepseek-ai/cordis` `4.0.1` / `4.0.2` / `4.0.4`(peer,逐版本枚举)
|
|
54
54
|
- `@deepseek-ai/dsh-session-persistence-jsonl`(可选,随 DSH 自带;缺失时回退到内置路径编码)
|
|
55
55
|
|
|
@@ -73,13 +73,18 @@ pnpm add @omdp/dsh-archived-sessions -w
|
|
|
73
73
|
|
|
74
74
|
### 兼容性门禁(0.3.6 起声明)
|
|
75
75
|
|
|
76
|
-
0.3.6 起在 `peerDependencies` 显式声明 `"@deepseek-ai/dsh": "0.1.7-rc.1"
|
|
76
|
+
0.3.6 起在 `peerDependencies` 显式声明 `"@deepseek-ai/dsh": "0.1.7-rc.1"`(0.3.7 追加 rc.2、0.3.8 追加 `0.2.0-rc.1`,当前枚举为 `0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1`)。
|
|
77
|
+
该声明由 DSH 自己的
|
|
77
78
|
**`evaluatePluginCompatibility()`**(`dsh-app-boot` 的公开导出)在安装与每次启动时校验:命中未实测
|
|
78
79
|
的新版本时会**整包优雅跳过**(stderr 打 `skipping profile bundle`,DSH 照常启动),命中实测版本
|
|
79
|
-
|
|
80
|
+
则正常加载。声明从 `0.1.7-rc.1` 起是因为**这个门禁本身是 0.1.7 才引入的**(逐版解包核对
|
|
80
81
|
`dsh-app-boot`:`0.1.5-rc.2`/`0.1.5-rc.3`/`0.1.6-alpha.1`/`0.1.6-alpha.2`/`0.1.7-alpha.1`/`0.1.7-alpha.2`
|
|
81
|
-
里 `evaluatePluginCompatibility` 出现 0
|
|
82
|
+
里 `evaluatePluginCompatibility` 出现 0 次)——旧运行时读到这条 peer
|
|
82
83
|
只是不认识的声明,**不影响加载**,所以老用户不会因为这条声明而失去插件。
|
|
84
|
+
0.3.7 追加 `0.1.7-rc.2` 的依据:rc.1→rc.2 tarball 逐文件 diff 显示 `dsh-shell`(本插件删除功能的
|
|
85
|
+
唯一 shell 依赖面)的 `lib/` **逐字节零变化**;再用 rc.2 的门禁跑新声明 → 放行;并在 scratch
|
|
86
|
+
profile(`dsh@0.1.7-rc.2` + 插件 0.3.6 + 精确版本豁免)上**真机实测完整删除链路**:
|
|
87
|
+
`POST /dsh-archived/delete` → `{"ok":true}` + 磁盘目录消失 + 归档集合清空。
|
|
83
88
|
|
|
84
89
|
### API
|
|
85
90
|
|
|
@@ -94,6 +99,24 @@ pnpm add @omdp/dsh-archived-sessions -w
|
|
|
94
99
|
|
|
95
100
|
### 变更记录
|
|
96
101
|
|
|
102
|
+
- **0.3.8**(2026-09-28):**追加 DSH `0.2.0-rc.1` 支持**(peer 枚举 `0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1`,代码零改动)。
|
|
103
|
+
背景:DSH 桌面端升到 `0.2.0-rc.1` 后,门禁把只声明到 `0.1.7-rc.2` 的 0.3.7 拦下(设置页里本插件整项消失、
|
|
104
|
+
`POST /dsh-archived/list` → **405** 且 `/dsh-archived/` 前缀未注册;**是优雅跳过而非崩溃**)。
|
|
105
|
+
核查:`0.1.7-rc.2 → 0.2.0-rc.1` 全量 tarball 逐文件 diff——本插件依赖面 **零破坏**:
|
|
106
|
+
`dsh-shell`(唯一 shell 依赖面,`execute`/`resolve`/`result` 三件套)`lib/` **逐字节零变化**;
|
|
107
|
+
`dsh-session` 的 5 个变化文件为**附加式**(新增 `ToolCallRecovery` / `TOOL_NOT_STARTED` /
|
|
108
|
+
`TOOL_OUTCOME_UNKNOWN`,`SessionStore` 等既有导出全保留,导出集合比对只有「新增」无「删除」)。
|
|
109
|
+
另:`0.2.0-rc.1` 门禁对新声明判**放行**、对 0.3.7 旧声明判**拦截**;沙箱安装官方
|
|
110
|
+
`@deepseek-ai/dsh@0.2.0-rc.1` + 独立 `DSH_HOME` 跑 `--dump-config` → 插件入树、零拦截;
|
|
111
|
+
`npm pack` 产物复核含新枚举。
|
|
112
|
+
|
|
113
|
+
- **0.3.7**(2026-09-25):**追加 DSH `0.1.7-rc.2` 支持**(peer 枚举 `0.1.7-rc.1 || 0.1.7-rc.2`,代码零改动)。
|
|
114
|
+
背景:DSH 桌面版 0.1.7-rc.2 上线后,门禁把只声明 `0.1.7-rc.1` 的 0.3.6 拦下(插件列表「异常」)。
|
|
115
|
+
核查:`dsh-shell` 的 `lib/` 在 rc.1→rc.2 **逐字节零变化**(本插件唯一 shell 依赖面);rc.2 门禁执行
|
|
116
|
+
新声明 → 放行;scratch profile(`dsh@0.1.7-rc.2` + 0.3.6 + 豁免)**真机删除实测通过**——
|
|
117
|
+
`POST /dsh-archived/delete {"sessionId":"session-f71d25a2-…"}` → `{"ok":true,"deleted":true}` +
|
|
118
|
+
磁盘目录消失 + `archivedSessionIds` 清空 + `list` 回 `{items:[]}`(测试会话已从备份还原)。
|
|
119
|
+
|
|
97
120
|
- **0.3.6**(2026-09-24):**`ctx.shell` 双时代自适应 + 声明 DSH 版本支持**。
|
|
98
121
|
1. **修复 0.3.5 对 rc.x 的静默回归**:0.3.5 改用 `execute()` 修好了 0.1.7,但 `run()` 在
|
|
99
122
|
0.1.5/0.1.6 上才是唯一存在的方法,于是 0.3.5 在那些版本上**每次删除都抛**
|
|
@@ -162,8 +185,8 @@ pnpm add @omdp/dsh-archived-sessions -w
|
|
|
162
185
|
|
|
163
186
|
### Requirements
|
|
164
187
|
|
|
165
|
-
- DeepSeek Harness **0.1.5-rc.1**, **0.1.5-rc.2**, **0.1.6-alpha.1**, **0.1.7-rc.1** (tested; **0.3.6+ works on all
|
|
166
|
-
- `@deepseek-ai/dsh` `0.1.7-rc.1` (peer, enumerated per version
|
|
188
|
+
- DeepSeek Harness **0.1.5-rc.1**, **0.1.5-rc.2**, **0.1.6-alpha.1**, **0.1.7-rc.1**, **0.1.7-rc.2**, **0.2.0-rc.1** (tested; **0.3.6+ works on all of them** — 0.3.7 adds the rc.2 declaration and 0.3.8 adds 0.2.0-rc.1, 0.3.5 is *silently broken* on the 0.1.5/0.1.6 line, see changelog)
|
|
189
|
+
- `@deepseek-ai/dsh` `0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1` (peer, enumerated per version: new in 0.3.6, rc.2 added in 0.3.7, 0.2.0-rc.1 added in 0.3.8)
|
|
167
190
|
- `@deepseek-ai/cordis` `4.0.1` / `4.0.2` / `4.0.4` (peer, enumerated per version)
|
|
168
191
|
- `@deepseek-ai/dsh-session-persistence-jsonl` (optional, ships with DSH; falls back to the built-in path encoding when absent)
|
|
169
192
|
|
|
@@ -189,15 +212,22 @@ it as the red "删除失败" banner) — both were bets on a single era.
|
|
|
189
212
|
|
|
190
213
|
### Compatibility gate (declared since 0.3.6)
|
|
191
214
|
|
|
192
|
-
Since 0.3.6 the plugin declares `"@deepseek-ai/dsh": "0.1.7-rc.1"` in `peerDependencies
|
|
215
|
+
Since 0.3.6 the plugin declares `"@deepseek-ai/dsh": "0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1"` in `peerDependencies`
|
|
216
|
+
(rc.2 added in 0.3.7, 0.2.0-rc.1 added in 0.3.8). DSH's own
|
|
193
217
|
**`evaluatePluginCompatibility()`** (a public export of `dsh-app-boot`) checks it at install time and on
|
|
194
218
|
every boot: on an untested newer runtime the **whole bundle is gracefully skipped** (stderr prints
|
|
195
219
|
`skipping profile bundle`; DSH still boots), and on the tested runtime it loads normally. The declaration
|
|
196
|
-
|
|
220
|
+
starts at `0.1.7-rc.1` because **the gate itself only exists from 0.1.7** (verified per version by
|
|
197
221
|
unpacking `dsh-app-boot` tarballs: `evaluatePluginCompatibility` appears 0 times in
|
|
198
|
-
`0.1.5-rc.2`/`0.1.5-rc.3`/`0.1.6-alpha.1`/`0.1.6-alpha.2`/`0.1.7-alpha.1`/`0.1.7-alpha.2
|
|
199
|
-
|
|
222
|
+
`0.1.5-rc.2`/`0.1.5-rc.3`/`0.1.6-alpha.1`/`0.1.6-alpha.2`/`0.1.7-alpha.1`/`0.1.7-alpha.2`) — older
|
|
223
|
+
runtimes simply see an unrecognized peer declaration, so **existing users on older
|
|
200
224
|
DSH versions do not lose the plugin** because of it.
|
|
225
|
+
The `0.1.7-rc.2` addition (0.3.7) is based on: a file-by-file tarball diff showing `dsh-shell`'s `lib/`
|
|
226
|
+
(**this plugin's only shell surface**) is **byte-identical** rc.1 → rc.2; running the rc.2 gate against the
|
|
227
|
+
new declaration → pass; and a **live end-to-end delete test** on a scratch profile
|
|
228
|
+
(`dsh@0.1.7-rc.2` + 0.3.6 + exact-version exemption): `POST /dsh-archived/delete
|
|
229
|
+
{"sessionId":"session-f71d25a2-…"}` → `{"ok":true,"deleted":true}` + directory gone from disk +
|
|
230
|
+
archive set emptied + `list` returning `{items:[]}` (the test session was restored from backup).
|
|
201
231
|
|
|
202
232
|
### API
|
|
203
233
|
|
|
@@ -212,6 +242,10 @@ DSH versions do not lose the plugin** because of it.
|
|
|
212
242
|
|
|
213
243
|
### Changelog
|
|
214
244
|
|
|
245
|
+
- **0.3.7** (2026-09-25): **adds DSH `0.1.7-rc.2` support** (peer enumeration `0.1.7-rc.1 || 0.1.7-rc.2`, zero code changes). Background: the DSH **desktop** app ships runtime `0.1.7-rc.2`, so the gate skipped 0.3.6's exact-`rc.1` declaration (plugin list badge 异常). Verification: `dsh-shell`'s `lib/` is **byte-identical** rc.1 → rc.2 (this plugin's only shell surface); the rc.2 gate passes the new declaration; and a live delete test on a scratch profile (`dsh@0.1.7-rc.2` + 0.3.6 + exemption) succeeded end-to-end — `POST /dsh-archived/delete {"sessionId":"session-f71d25a2-…"}` → `{"ok":true,"deleted":true}` + directory gone + archive set emptied + `list` → `{items:[]}` (test session restored from backup).
|
|
246
|
+
|
|
247
|
+
- **0.3.8** (2026-09-28): **adds DSH `0.2.0-rc.1` support** (peer enumeration `0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1`, zero code changes). Background: after the desktop app moved to `0.2.0-rc.1` the gate skipped the bundle declared only up to `0.1.7-rc.2` (the settings-page item disappeared and `POST /dsh-archived/list` returned **405** with the `/dsh-archived/` prefix unregistered — a graceful skip, not a crash). Verification: full file-by-file tarball diff `0.1.7-rc.2 → 0.2.0-rc.1` over every `lib/` file — nothing this plugin uses broke: `dsh-shell` (its only shell surface: the `execute`/`resolve`/`result` trio) is **byte-identical**, and `dsh-session`'s 5 changed files are **additive** (new exports `ToolCallRecovery` / `TOOL_NOT_STARTED` / `TOOL_OUTCOME_UNKNOWN`; `SessionStore` and every pre-existing export kept — the export-set diff shows additions only, no removals). Also: the `0.2.0-rc.1` gate **passes** the new manifest and **blocks** the old 0.3.7 one; a sandbox with the official `@deepseek-ai/dsh@0.2.0-rc.1` + isolated `DSH_HOME` ran `--dump-config` → plugin present in the tree, no gate skip; the `npm pack` artifact was re-checked to carry the new enumeration.
|
|
248
|
+
|
|
215
249
|
- **0.3.6** (2026-09-24): **dual-era `ctx.shell` adaptation + declared DSH version support**.
|
|
216
250
|
1. **Fixes a silent rc.x regression from 0.3.5**: 0.3.5 switched to `execute()` and thereby fixed 0.1.7, but `run()` is the only method that exists on 0.1.5/0.1.6, so on those versions 0.3.5 threw `shell executor unavailable; cannot delete from disk` on **every** delete (0.3.4's use of `run()` was conversely fine on rc.x and dead on 0.1.7). 0.3.6 probes at runtime: prefer `execute()` (0.1.7+, awaiting `execution.result()`), else fall back to `run()` (≤0.1.6), and only error when neither exists ⇒ **deletes work across 0.1.5-rc.1 → 0.1.7-rc.1**. Basis: unpacked `@deepseek-ai/dsh-shell` `lib/types/index.d.ts` per version (see "Dual-era `ctx.shell` adaptation" above).
|
|
217
251
|
2. Added the `@deepseek-ai/dsh` peer declaration `0.1.7-rc.1` (enumerated per version; see "Compatibility gate" above).
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@omdp/dsh-archived-sessions",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.8",
|
|
4
4
|
"description": "Archived-sessions manager for the DeepSeek Harness web UI: list / unarchive / delete / detail from Settings. · DSH 归档会话管理:设置页查看、释放、删除已归档会话(含按树删除子会话与孤儿清理)。",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "lib/index.js",
|
|
@@ -44,6 +44,6 @@
|
|
|
44
44
|
},
|
|
45
45
|
"peerDependencies": {
|
|
46
46
|
"@deepseek-ai/cordis": "4.0.1 || 4.0.2 || 4.0.4",
|
|
47
|
-
"@deepseek-ai/dsh": "0.1.7-rc.1"
|
|
47
|
+
"@deepseek-ai/dsh": "0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1"
|
|
48
48
|
}
|
|
49
49
|
}
|