@xmoon76/dsh-pi-tui 0.4.0-alpha.2 → 0.4.0

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.
Files changed (4) hide show
  1. package/README.en.md +15 -13
  2. package/README.md +12 -10
  3. package/dist/startup.mjs +25 -14
  4. package/package.json +88 -88
package/README.en.md CHANGED
@@ -18,7 +18,7 @@ dsh --profile pi-tui
18
18
 
19
19
  ## DSH compatibility and source validation
20
20
 
21
- The published package declares the lower-bound-only DSH peer contract `>=0.1.2-alpha.4`. Source validation does not change that contract or vendor DSH into this repository.
21
+ The published package declares the lower-bound-only DSH peer contract `>=0.1.2-rc.1`. Source validation does not change that contract or vendor DSH into this repository.
22
22
 
23
23
  When the target DSH version is not yet available from npm, validate against the official checkout pinned by commit SHA:
24
24
 
@@ -26,7 +26,7 @@ When the target DSH version is not yet available from npm, validate against the
26
26
  pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
27
27
  ```
28
28
 
29
- CI uses Source Mode for `next` and npm Mode for `main` and every tag. The source lane validates the complete official DSH tarball family, TUI presets, and the old-runtime boundary; the published `pi2dsh` ecosystem check is explicitly marked skipped until a compatible published combination exists. See [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md) for the full workflow.
29
+ CI follows the tracked `test/compat/dsh-mode.json` policy for pushes to `next` and pull requests targeting `next`; `main` and every tag use npm Mode. Both `next` lanes use `test/compat/dsh-source.json` for the current validated DSH target; Source Mode validates the complete official DSH tarball family, TUI presets, and the old-runtime boundary, while npm Mode runs the frozen registry lane. The published `pi2dsh` ecosystem check is explicitly marked skipped for an unpublished source family. See [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md) for the full workflow.
30
30
 
31
31
  ## Features
32
32
 
@@ -319,7 +319,8 @@ dsh-pi-tui:
319
319
 
320
320
  | TUI package line | Matching DSH line | Notes |
321
321
  |---|---|---|
322
- | `0.4.x-alpha` (`@next`) | `>=0.1.2-alpha.4` | Current prerelease; each release validates its concrete DSH family |
322
+ | `0.4.0` (`@latest`) | `>=0.1.2-rc.1` | Current stable; validated against the rc.1 family |
323
+ | `0.4.x-alpha` (`@next`) | `>=0.1.2-rc.1` | Subsequent prerelease; each release validates its concrete DSH family |
323
324
  | `0.4.0-alpha.2` (published) | `>=0.1.2-alpha.4` | Previous 0.4 prerelease; its releases validated the alpha.4/alpha.5 family |
324
325
  | `0.4.0-alpha.1` (published) | `>=0.1.2-alpha.2` | Earlier 0.4 prerelease; accepts the alpha.2/alpha.3 runtime |
325
326
  | `0.3.x` (`@0.3`) | `0.1.1-rc.2` | Legacy runtime line |
@@ -329,12 +330,14 @@ normal incompatible-runtime boundary will fail. The startup row prints upgrade
329
330
  and rollback guidance when concurrent Loader ordering allows it, but that
330
331
  friendly notice is best-effort rather than a startup-order guarantee. If you
331
332
  keep DSH 0.1.1, use the 0.3 TUI line; if you keep the alpha.2/alpha.3
332
- baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.1`. For the current 0.4
333
- prerelease, install DSH first and then add the TUI to a profile:
333
+ baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.1`; if you keep the
334
+ alpha.4/alpha.5 baseline, use `@xmoon76/dsh-pi-tui@0.4.0-alpha.2`. For the
335
+ current 0.4 stable release, install the matching DSH first and then add the
336
+ TUI to a profile:
334
337
 
335
338
  ```sh
336
- npm install -g @deepseek-ai/dsh@0.1.2-alpha.5
337
- dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
339
+ npm install -g @deepseek-ai/dsh@0.1.2-rc.1
340
+ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
338
341
  dsh --profile pi-tui
339
342
  ```
340
343
 
@@ -346,7 +349,7 @@ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
346
349
  dsh --profile pi-tui
347
350
  ```
348
351
 
349
- The current 0.4 line declares `>=0.1.2-alpha.4`; each release validates
352
+ The current 0.4 line declares `>=0.1.2-rc.1`; each release validates
350
353
  its concrete DSH family. Running only `npm install -g @xmoon76/dsh-pi-tui` does
351
354
  not install the plugin into a DSH profile; the `dsh plugin` command is still
352
355
  required.
@@ -358,12 +361,11 @@ only after the roster proves that no custom `code` preset exists.
358
361
 
359
362
  ### npm
360
363
 
361
- Using a dedicated `pi-tui` profile is recommended. Once a stable 0.4 release
362
- exists, use the matching stable TUI channel (`@latest`); use `@next` for the
363
- prerelease channel:
364
+ Using a dedicated `pi-tui` profile is recommended. Use the TUI channel that
365
+ matches your DSH line: `@latest` for stable releases, `@next` for prereleases:
364
366
 
365
367
  ```sh
366
- dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
368
+ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
367
369
  dsh --profile pi-tui
368
370
  ```
369
371
 
@@ -375,7 +377,7 @@ dsh --profile pi-tui --session <session-id>
375
377
 
376
378
  ### Source Mode (validation only)
377
379
 
378
- Source Mode is only for `next` CI and local compatibility validation. It reads the full commit pin in `test/compat/dsh-source.json`, builds the official DSH tarball family, installs it through temporary pnpm overrides, and removes the temporary state afterward. Do not write DSH source paths, `file:` dependencies, or workspace symlinks into a published package.
380
+ Source Mode is the validation-only distribution selected by the tracked policy for `next` CI and available for local compatibility checks. It reads the full commit pin in `test/compat/dsh-source.json`, builds the official DSH tarball family, installs it through temporary pnpm overrides, and removes the temporary state afterward. Do not write DSH source paths, `file:` dependencies, or workspace symlinks into a published package.
379
381
 
380
382
  ```sh
381
383
  pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
package/README.md CHANGED
@@ -18,7 +18,7 @@ dsh --profile pi-tui
18
18
 
19
19
  ## DSH 兼容性与源码验证
20
20
 
21
- 发布包通过 `package.json` peer contract 使用 DSH `>=0.1.2-alpha.4`；源码验证不会修改这个发布契约，也不会把 DSH vendor 进本仓库。
21
+ 发布包通过 `package.json` peer contract 使用 DSH `>=0.1.2-rc.1`；源码验证不会修改这个发布契约，也不会把 DSH vendor 进本仓库。
22
22
 
23
23
  当目标 DSH 版本尚未发布到 npm 时，可以用固定 commit 的官方源码包做本地验证：
24
24
 
@@ -26,7 +26,7 @@ dsh --profile pi-tui
26
26
  pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
27
27
  ```
28
28
 
29
- CI 中 `next` 使用 Source Mode，`main` 和所有 tag 使用 npm Mode。源码 lane 会验证完整的官方 DSH tarball family、TUI 预设和旧 runtime 边界；依赖已发布 `pi2dsh` 的生态检查会明确标记为 skipped。详细流程见 [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md)。
29
+ CI 对 push 到 `next` 以及目标为 `next` 的 PR 遵循跟踪的 `test/compat/dsh-mode.json` 策略；`main` 和所有 tag 使用 npm Mode。`next` 的两种 lane 都从 `test/compat/dsh-source.json` 读取当前 validated DSH target；Source Mode 会验证完整的官方 DSH tarball family、TUI 预设和旧 runtime 边界，npm Mode 则运行冻结的 registry lane。对于尚未发布的 source family，已发布 `pi2dsh` 的生态检查会明确标记为 skipped。详细流程见 [`docs/dsh-compatibility.md`](docs/dsh-compatibility.md)。
30
30
 
31
31
  ## 功能
32
32
 
@@ -308,7 +308,8 @@ dsh-pi-tui:
308
308
 
309
309
  | TUI 包版本 | 对应 DSH 版本 | 说明 |
310
310
  |---|---|---|
311
- | `0.4.x-alpha`（`@next`） | `>=0.1.2-alpha.4` | 当前预发布线；按每个发布版本的具体 DSH family 验证 |
311
+ | `0.4.0`（`@latest`） | `>=0.1.2-rc.1` | 当前稳定版；按 0.1.2-rc.1 family 验证 |
312
+ | `0.4.x-alpha`（`@next`） | `>=0.1.2-rc.1` | 后续预发布线；按每个发布版本的具体 DSH family 验证 |
312
313
  | `0.4.0-alpha.2`（已发布） | `>=0.1.2-alpha.4` | 上一条 0.4 预发布线；其发布版本按 alpha.4/alpha.5 family 验证 |
313
314
  | `0.4.0-alpha.1`（已发布） | `>=0.1.2-alpha.2` | 更早的 0.4 预发布线；接受 alpha.2/alpha.3 运行时 |
314
315
  | `0.3.x`（`@0.3`） | `0.1.1-rc.2` | 旧运行时兼容线 |
@@ -317,12 +318,13 @@ dsh-pi-tui:
317
318
  正常的不兼容边界以非零状态失败。启动行会在 Loader 并发挂载顺序允许时打印
318
319
  升级和回退提示，但该友好提示是 best-effort，不是启动顺序保证；保留 DSH
319
320
  0.1.1 时请使用 0.3，保留 alpha.2/alpha.3 时请使用
320
- `@xmoon76/dsh-pi-tui@0.4.0-alpha.1`。当前 0.4 预发布线的推荐安装顺序如下
321
+ `@xmoon76/dsh-pi-tui@0.4.0-alpha.1`，保留 alpha.4/alpha.5 时请使用
322
+ `@xmoon76/dsh-pi-tui@0.4.0-alpha.2`。当前 0.4 稳定版的推荐安装顺序如下
321
323
  （先装 DSH，再把 TUI 装入 profile）：
322
324
 
323
325
  ```sh
324
- npm install -g @deepseek-ai/dsh@0.1.2-alpha.5
325
- dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
326
+ npm install -g @deepseek-ai/dsh@0.1.2-rc.1
327
+ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
326
328
  dsh --profile pi-tui
327
329
  ```
328
330
 
@@ -334,7 +336,7 @@ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@0.3
334
336
  dsh --profile pi-tui
335
337
  ```
336
338
 
337
- `0.4` 当前线的声明支持范围是 `>=0.1.2-alpha.4`；每个发布版本都会验证
339
+ `0.4` 当前线的声明支持范围是 `>=0.1.2-rc.1`；每个发布版本都会验证
338
340
  具体的 DSH family。仅执行 `npm install -g @xmoon76/dsh-pi-tui` 不会把插件安装进
339
341
  DSH profile，实际使用仍应执行上面的 `dsh plugin` 命令。
340
342
 
@@ -345,11 +347,11 @@ DSH profile，实际使用仍应执行上面的 `dsh plugin` 命令。
345
347
 
346
348
  ### npm
347
349
 
348
- 推荐使用单独的 `pi-tui` profile。稳定版发布后，使用与 DSH 版本匹配的
350
+ 推荐使用单独的 `pi-tui` profile。使用与 DSH 版本匹配的
349
351
  TUI channel（稳定版用 `@latest`，预发布版用 `@next`）：
350
352
 
351
353
  ```sh
352
- dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@next
354
+ dsh plugin --profile pi-tui -- add @xmoon76/dsh-pi-tui@latest
353
355
  dsh --profile pi-tui
354
356
  ```
355
357
 
@@ -361,7 +363,7 @@ dsh --profile pi-tui --session <session-id>
361
363
 
362
364
  ### Source Mode（仅验证）
363
365
 
364
- Source Mode 只用于 `next` 的 CI 和本地兼容性验证，不是发布或用户安装方式。它从 `test/compat/dsh-source.json` 的完整 commit SHA 构建官方 DSH tarball family，通过临时 pnpm overrides 安装，并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace symlink 写入发布 package。
366
+ Source Mode 是 `next` CI 按跟踪策略选用的、并可用于本地兼容性检查的验证专用 distribution。它从 `test/compat/dsh-source.json` 的完整 commit SHA 构建官方 DSH tarball family，通过临时 pnpm overrides 安装，并在完成后清理临时状态。不要把 DSH 源码路径、`file:` 依赖或 workspace symlink 写入发布 package。
365
367
 
366
368
  ```sh
367
369
  pnpm compat:dsh:source -- --dsh-dir "$HOME/project/deepseek-harness"
package/dist/startup.mjs CHANGED
@@ -67,20 +67,31 @@ const name = "tui-startup";
67
67
  /** Services required before the flags can be resolved. */
68
68
  const inject = ["cmdlineArgs"];
69
69
  /** The compatibility table. */
70
- const HARNESS_COMPAT = [{
71
- min: "0.1.2-alpha.2",
72
- max: "0.1.2-alpha.4",
73
- since: "0.4.0-alpha.2",
74
- requires: "DeepSeek Harness 0.1.2-alpha.4 or later",
75
- upgradeDsh: "0.1.2-alpha.5",
76
- fallbackTui: "0.4.0-alpha.1"
77
- }, {
78
- max: "0.1.2-alpha.2",
79
- since: "0.4.0-alpha.1",
80
- requires: "DeepSeek Harness 0.1.2-alpha.2 or later",
81
- upgradeDsh: "0.1.2-alpha.5",
82
- fallbackTui: "0.3"
83
- }];
70
+ const HARNESS_COMPAT = [
71
+ {
72
+ min: "0.1.2-alpha.4",
73
+ max: "0.1.2-rc.1",
74
+ since: "0.4.0",
75
+ requires: "DeepSeek Harness 0.1.2-rc.1 or later",
76
+ upgradeDsh: "0.1.2-rc.1",
77
+ fallbackTui: "0.4.0-alpha.2"
78
+ },
79
+ {
80
+ min: "0.1.2-alpha.2",
81
+ max: "0.1.2-alpha.4",
82
+ since: "0.4.0-alpha.2",
83
+ requires: "DeepSeek Harness 0.1.2-alpha.4 or later",
84
+ upgradeDsh: "0.1.2-rc.1",
85
+ fallbackTui: "0.4.0-alpha.1"
86
+ },
87
+ {
88
+ max: "0.1.2-alpha.2",
89
+ since: "0.4.0-alpha.1",
90
+ requires: "DeepSeek Harness 0.1.2-alpha.2 or later",
91
+ upgradeDsh: "0.1.2-rc.1",
92
+ fallbackTui: "0.3"
93
+ }
94
+ ];
84
95
  /** The compat entry covering the installed dsh version, or undefined when
85
96
  * the harness is supported. */
86
97
  function harnessCompatEntryFor(installed) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xmoon76/dsh-pi-tui",
3
- "version": "0.4.0-alpha.2",
3
+ "version": "0.4.0",
4
4
  "description": "The dsh-pi-tui bundle: a TUI surface for DeepSeek Harness profiles (dsh --profile pi-tui)",
5
5
  "license": "MIT",
6
6
  "author": "XMoon <xmoonox@gmail.com>",
@@ -77,71 +77,71 @@
77
77
  "peerDependencies": {
78
78
  "@deepseek-ai/cordis": "^4.0.2",
79
79
  "@deepseek-ai/cordis-plugin-loader": "^1.0.2",
80
- "@deepseek-ai/dsh-agent": ">=0.1.2-alpha.4",
81
- "@deepseek-ai/dsh-agent-default-model": ">=0.1.2-alpha.4",
82
- "@deepseek-ai/dsh-agent-presets": ">=0.1.2-alpha.4",
83
- "@deepseek-ai/dsh-authorization": ">=0.1.2-alpha.4",
84
- "@deepseek-ai/dsh-cmdline": ">=0.1.2-alpha.4",
85
- "@deepseek-ai/dsh-commands": ">=0.1.2-alpha.4",
86
- "@deepseek-ai/dsh-credentials": ">=0.1.2-alpha.4",
87
- "@deepseek-ai/dsh-goal": ">=0.1.2-alpha.4",
88
- "@deepseek-ai/dsh-jobs": ">=0.1.2-alpha.4",
89
- "@deepseek-ai/dsh-llm": ">=0.1.2-alpha.4",
90
- "@deepseek-ai/dsh-llm-retry": ">=0.1.2-alpha.4",
91
- "@deepseek-ai/dsh-permission-presets": ">=0.1.2-alpha.4",
92
- "@deepseek-ai/dsh-plan-mode": ">=0.1.2-alpha.4",
93
- "@deepseek-ai/dsh-sandbox-policy": ">=0.1.2-alpha.4",
94
- "@deepseek-ai/dsh-session": ">=0.1.2-alpha.4",
95
- "@deepseek-ai/dsh-session-persistence": ">=0.1.2-alpha.4",
96
- "@deepseek-ai/dsh-session-title": ">=0.1.2-alpha.4",
97
- "@deepseek-ai/dsh-settings": ">=0.1.2-alpha.4",
98
- "@deepseek-ai/dsh-shell": ">=0.1.2-alpha.4",
99
- "@deepseek-ai/dsh-skill": ">=0.1.2-alpha.4",
100
- "@deepseek-ai/dsh-subagent": ">=0.1.2-alpha.4",
101
- "@deepseek-ai/dsh-token-meter": ">=0.1.2-alpha.4",
102
- "@deepseek-ai/dsh-tool-todo": ">=0.1.2-alpha.4",
103
- "@deepseek-ai/dsh-tool-workflow": ">=0.1.2-alpha.4",
104
- "@deepseek-ai/dsh-tools": ">=0.1.2-alpha.4",
105
- "@deepseek-ai/dsh-user-approval": ">=0.1.2-alpha.4",
106
- "@deepseek-ai/dsh-user-questions": ">=0.1.2-alpha.4",
80
+ "@deepseek-ai/dsh-agent": ">=0.1.2-rc.1",
81
+ "@deepseek-ai/dsh-agent-default-model": ">=0.1.2-rc.1",
82
+ "@deepseek-ai/dsh-agent-presets": ">=0.1.2-rc.1",
83
+ "@deepseek-ai/dsh-authorization": ">=0.1.2-rc.1",
84
+ "@deepseek-ai/dsh-cmdline": ">=0.1.2-rc.1",
85
+ "@deepseek-ai/dsh-commands": ">=0.1.2-rc.1",
86
+ "@deepseek-ai/dsh-credentials": ">=0.1.2-rc.1",
87
+ "@deepseek-ai/dsh-goal": ">=0.1.2-rc.1",
88
+ "@deepseek-ai/dsh-jobs": ">=0.1.2-rc.1",
89
+ "@deepseek-ai/dsh-llm": ">=0.1.2-rc.1",
90
+ "@deepseek-ai/dsh-llm-retry": ">=0.1.2-rc.1",
91
+ "@deepseek-ai/dsh-permission-presets": ">=0.1.2-rc.1",
92
+ "@deepseek-ai/dsh-plan-mode": ">=0.1.2-rc.1",
93
+ "@deepseek-ai/dsh-sandbox-policy": ">=0.1.2-rc.1",
94
+ "@deepseek-ai/dsh-session": ">=0.1.2-rc.1",
95
+ "@deepseek-ai/dsh-session-persistence": ">=0.1.2-rc.1",
96
+ "@deepseek-ai/dsh-session-title": ">=0.1.2-rc.1",
97
+ "@deepseek-ai/dsh-settings": ">=0.1.2-rc.1",
98
+ "@deepseek-ai/dsh-shell": ">=0.1.2-rc.1",
99
+ "@deepseek-ai/dsh-skill": ">=0.1.2-rc.1",
100
+ "@deepseek-ai/dsh-subagent": ">=0.1.2-rc.1",
101
+ "@deepseek-ai/dsh-token-meter": ">=0.1.2-rc.1",
102
+ "@deepseek-ai/dsh-tool-todo": ">=0.1.2-rc.1",
103
+ "@deepseek-ai/dsh-tool-workflow": ">=0.1.2-rc.1",
104
+ "@deepseek-ai/dsh-tools": ">=0.1.2-rc.1",
105
+ "@deepseek-ai/dsh-user-approval": ">=0.1.2-rc.1",
106
+ "@deepseek-ai/dsh-user-questions": ">=0.1.2-rc.1",
107
107
  "@deepseek-ai/schemastery": "^3.18.1"
108
108
  },
109
109
  "devDependencies": {
110
110
  "@deepseek-ai/cordis-plugin-loader": "^1.0.2",
111
- "@deepseek-ai/dsh-agent": "0.1.2-alpha.5",
112
- "@deepseek-ai/dsh-agent-default-model": "0.1.2-alpha.5",
113
- "@deepseek-ai/dsh-agent-loop": "0.1.2-alpha.5",
114
- "@deepseek-ai/dsh-agent-presets": "0.1.2-alpha.5",
115
- "@deepseek-ai/dsh-attachment": "0.1.2-alpha.5",
116
- "@deepseek-ai/dsh-authorization": "0.1.2-alpha.5",
117
- "@deepseek-ai/dsh-brand": "0.1.2-alpha.5",
118
- "@deepseek-ai/dsh-cmdline": "0.1.2-alpha.5",
119
- "@deepseek-ai/dsh-commands": "0.1.2-alpha.5",
120
- "@deepseek-ai/dsh-credentials": "0.1.2-alpha.5",
121
- "@deepseek-ai/dsh-goal": "0.1.2-alpha.5",
122
- "@deepseek-ai/dsh-invariants": "0.1.2-alpha.5",
123
- "@deepseek-ai/dsh-jobs": "0.1.2-alpha.5",
124
- "@deepseek-ai/dsh-llm": "0.1.2-alpha.5",
125
- "@deepseek-ai/dsh-llm-retry": "0.1.2-alpha.5",
126
- "@deepseek-ai/dsh-permission-presets": "0.1.2-alpha.5",
127
- "@deepseek-ai/dsh-plan-mode": "0.1.2-alpha.5",
128
- "@deepseek-ai/dsh-sandbox-policy": "0.1.2-alpha.5",
129
- "@deepseek-ai/dsh-scope": "0.1.2-alpha.5",
130
- "@deepseek-ai/dsh-session": "0.1.2-alpha.5",
131
- "@deepseek-ai/dsh-session-persistence": "0.1.2-alpha.5",
132
- "@deepseek-ai/dsh-session-title": "0.1.2-alpha.5",
133
- "@deepseek-ai/dsh-settings": "0.1.2-alpha.5",
134
- "@deepseek-ai/dsh-shell": "0.1.2-alpha.5",
135
- "@deepseek-ai/dsh-skill": "0.1.2-alpha.5",
136
- "@deepseek-ai/dsh-subagent": "0.1.2-alpha.5",
137
- "@deepseek-ai/dsh-system-prompt": "0.1.2-alpha.5",
138
- "@deepseek-ai/dsh-timeout": "0.1.2-alpha.5",
139
- "@deepseek-ai/dsh-token-meter": "0.1.2-alpha.5",
140
- "@deepseek-ai/dsh-tool-todo": "0.1.2-alpha.5",
141
- "@deepseek-ai/dsh-tool-workflow": "0.1.2-alpha.5",
142
- "@deepseek-ai/dsh-tools": "0.1.2-alpha.5",
143
- "@deepseek-ai/dsh-user-approval": "0.1.2-alpha.5",
144
- "@deepseek-ai/dsh-user-questions": "0.1.2-alpha.5",
111
+ "@deepseek-ai/dsh-agent": "0.1.2-rc.1",
112
+ "@deepseek-ai/dsh-agent-default-model": "0.1.2-rc.1",
113
+ "@deepseek-ai/dsh-agent-loop": "0.1.2-rc.1",
114
+ "@deepseek-ai/dsh-agent-presets": "0.1.2-rc.1",
115
+ "@deepseek-ai/dsh-attachment": "0.1.2-rc.1",
116
+ "@deepseek-ai/dsh-authorization": "0.1.2-rc.1",
117
+ "@deepseek-ai/dsh-brand": "0.1.2-rc.1",
118
+ "@deepseek-ai/dsh-cmdline": "0.1.2-rc.1",
119
+ "@deepseek-ai/dsh-commands": "0.1.2-rc.1",
120
+ "@deepseek-ai/dsh-credentials": "0.1.2-rc.1",
121
+ "@deepseek-ai/dsh-goal": "0.1.2-rc.1",
122
+ "@deepseek-ai/dsh-invariants": "0.1.2-rc.1",
123
+ "@deepseek-ai/dsh-jobs": "0.1.2-rc.1",
124
+ "@deepseek-ai/dsh-llm": "0.1.2-rc.1",
125
+ "@deepseek-ai/dsh-llm-retry": "0.1.2-rc.1",
126
+ "@deepseek-ai/dsh-permission-presets": "0.1.2-rc.1",
127
+ "@deepseek-ai/dsh-plan-mode": "0.1.2-rc.1",
128
+ "@deepseek-ai/dsh-sandbox-policy": "0.1.2-rc.1",
129
+ "@deepseek-ai/dsh-scope": "0.1.2-rc.1",
130
+ "@deepseek-ai/dsh-session": "0.1.2-rc.1",
131
+ "@deepseek-ai/dsh-session-persistence": "0.1.2-rc.1",
132
+ "@deepseek-ai/dsh-session-title": "0.1.2-rc.1",
133
+ "@deepseek-ai/dsh-settings": "0.1.2-rc.1",
134
+ "@deepseek-ai/dsh-shell": "0.1.2-rc.1",
135
+ "@deepseek-ai/dsh-skill": "0.1.2-rc.1",
136
+ "@deepseek-ai/dsh-subagent": "0.1.2-rc.1",
137
+ "@deepseek-ai/dsh-system-prompt": "0.1.2-rc.1",
138
+ "@deepseek-ai/dsh-timeout": "0.1.2-rc.1",
139
+ "@deepseek-ai/dsh-token-meter": "0.1.2-rc.1",
140
+ "@deepseek-ai/dsh-tool-todo": "0.1.2-rc.1",
141
+ "@deepseek-ai/dsh-tool-workflow": "0.1.2-rc.1",
142
+ "@deepseek-ai/dsh-tools": "0.1.2-rc.1",
143
+ "@deepseek-ai/dsh-user-approval": "0.1.2-rc.1",
144
+ "@deepseek-ai/dsh-user-questions": "0.1.2-rc.1",
145
145
  "@deepseek-ai/schemastery": "^3.18.1",
146
146
  "@types/node": "^22.0.0",
147
147
  "@xmoon76/pi-tui": "^0.84.4",
@@ -151,32 +151,32 @@
151
151
  "tsdown": "0.22.0",
152
152
  "tsx": "^4.23.12",
153
153
  "typescript": "^5.9.0",
154
- "@deepseek-ai/dsh-session-projection": "0.1.2-alpha.5",
155
- "@deepseek-ai/dsh-persona": "0.1.2-alpha.5",
156
- "@deepseek-ai/dsh-agent-instructions": "0.1.2-alpha.5",
157
- "@deepseek-ai/dsh-tool-fs": "0.1.2-alpha.5",
158
- "@deepseek-ai/dsh-tool-fs-search": "0.1.2-alpha.5",
159
- "@deepseek-ai/dsh-tool-jobs": "0.1.2-alpha.5",
160
- "@deepseek-ai/dsh-skill-filesystem": "0.1.2-alpha.5",
161
- "@deepseek-ai/dsh-tool-skill": "0.1.2-alpha.5",
162
- "@deepseek-ai/dsh-command-goal": "0.1.2-alpha.5",
163
- "@deepseek-ai/dsh-tool-goal": "0.1.2-alpha.5",
164
- "@deepseek-ai/dsh-compaction-basic": "0.1.2-alpha.5",
165
- "@deepseek-ai/dsh-command-compact": "0.1.2-alpha.5",
166
- "@deepseek-ai/dsh-compaction-tool-result-pruner": "0.1.2-alpha.5",
167
- "@deepseek-ai/dsh-tool-subagent-control": "0.1.2-alpha.5",
168
- "@deepseek-ai/dsh-tool-subagent": "0.1.2-alpha.5",
169
- "@deepseek-ai/dsh-workflow-worker-thread": "0.1.2-alpha.5",
170
- "@deepseek-ai/dsh-tool-ralph": "0.1.2-alpha.5",
171
- "@deepseek-ai/dsh-tool-ask-user": "0.1.2-alpha.5",
172
- "@deepseek-ai/dsh-tool-web": "0.1.2-alpha.5",
173
- "@deepseek-ai/dsh-agent-tool-presentation": "0.1.2-alpha.5",
174
- "@deepseek-ai/dsh-terminal": "0.1.2-alpha.5",
175
- "@deepseek-ai/dsh-fs-local": "0.1.2-alpha.5",
176
- "@deepseek-ai/dsh-tool-str-replace-editor": "0.1.2-alpha.5",
177
- "@deepseek-ai/dsh-tool-cordis": "0.1.2-alpha.5",
178
- "@deepseek-ai/dsh-agent-loop-testkit": "0.1.2-alpha.5",
179
- "@deepseek-ai/dsh-subagent-spawn-in-process": "0.1.2-alpha.5"
154
+ "@deepseek-ai/dsh-session-projection": "0.1.2-rc.1",
155
+ "@deepseek-ai/dsh-persona": "0.1.2-rc.1",
156
+ "@deepseek-ai/dsh-agent-instructions": "0.1.2-rc.1",
157
+ "@deepseek-ai/dsh-tool-fs": "0.1.2-rc.1",
158
+ "@deepseek-ai/dsh-tool-fs-search": "0.1.2-rc.1",
159
+ "@deepseek-ai/dsh-tool-jobs": "0.1.2-rc.1",
160
+ "@deepseek-ai/dsh-skill-filesystem": "0.1.2-rc.1",
161
+ "@deepseek-ai/dsh-tool-skill": "0.1.2-rc.1",
162
+ "@deepseek-ai/dsh-command-goal": "0.1.2-rc.1",
163
+ "@deepseek-ai/dsh-tool-goal": "0.1.2-rc.1",
164
+ "@deepseek-ai/dsh-compaction-basic": "0.1.2-rc.1",
165
+ "@deepseek-ai/dsh-command-compact": "0.1.2-rc.1",
166
+ "@deepseek-ai/dsh-compaction-tool-result-pruner": "0.1.2-rc.1",
167
+ "@deepseek-ai/dsh-tool-subagent-control": "0.1.2-rc.1",
168
+ "@deepseek-ai/dsh-tool-subagent": "0.1.2-rc.1",
169
+ "@deepseek-ai/dsh-workflow-worker-thread": "0.1.2-rc.1",
170
+ "@deepseek-ai/dsh-tool-ralph": "0.1.2-rc.1",
171
+ "@deepseek-ai/dsh-tool-ask-user": "0.1.2-rc.1",
172
+ "@deepseek-ai/dsh-tool-web": "0.1.2-rc.1",
173
+ "@deepseek-ai/dsh-agent-tool-presentation": "0.1.2-rc.1",
174
+ "@deepseek-ai/dsh-terminal": "0.1.2-rc.1",
175
+ "@deepseek-ai/dsh-fs-local": "0.1.2-rc.1",
176
+ "@deepseek-ai/dsh-tool-str-replace-editor": "0.1.2-rc.1",
177
+ "@deepseek-ai/dsh-tool-cordis": "0.1.2-rc.1",
178
+ "@deepseek-ai/dsh-agent-loop-testkit": "0.1.2-rc.1",
179
+ "@deepseek-ai/dsh-subagent-spawn-in-process": "0.1.2-rc.1"
180
180
  },
181
181
  "engines": {
182
182
  "node": "^22.19.0 || >=24"