dsh-plugin-lcu 0.3.6 → 0.3.7

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.3.7
+
+Documentation only; no behaviour change.
+
+The preset recipe now describes DSH 0.2.1's presentation modes: `heavy` uses `native`, because the old `both`
+mode was removed and a preset declares exactly one of `native | ptc`. It also records that the official
+`subagent_codex` is a global Host tool since 0.2.1, and that `dsh-subagent-codex-pro` shadows it per Agent for the
+generated presets rather than a per-preset disabled row switching it off.
+
 ## 0.3.6
 
 Metadata only; no behaviour change.

package/README.md

@@ -91,16 +91,19 @@ This writes a marked block into that profile's `cordis.patch.yml` containing two
 | Preset | Base | Adds |
 |---|---|---|
 | `daily` | the shipped `ptc` preset | a Codex delegation provider of its own |
-| `heavy` | the same, with `tool-presentation: both` | everything above, and this plugin attaches |
+| `heavy` | the same, with `tool-presentation: native` | everything above, and this plugin attaches |
 
 Re-run it after a DSH upgrade so the copies keep up. `--daily-only` emits just `daily`, `--dry-run`
-prints without writing, and `--out FILE` writes somewhere else. The official `tool-subagent-codex` row
-stays disabled, as the base ships it: a separate provider registers its own `subagent_codex`, and two
-rows registering that name in one scope collide.
-
-> `heavy` sets the tool presentation to `both` on purpose. In pure `ptc` presentation the model only
-> sees `run_code`, so `js` would have to be nested as a JavaScript string inside another JavaScript
-> program. `both` keeps `js` directly callable.
+prints without writing, and `--out FILE` writes somewhere else. The official Codex tool is no longer
+a per-preset row: since DSH 0.2.1 the official bundle contributes a **global** `subagent_codex`, and
+a separate provider registers its own same-named tool per Agent for the generated presets, shadowing
+the global one. Two registrations in one scope still collide, so nothing may enable a same-name
+`tool-subagent` row beside that provider.
+
+> `heavy` sets the tool presentation to `native` on purpose. DSH 0.2.1 removed the old `both` mode —
+> a preset declares one presentation, `native` or `ptc` — and in pure `ptc` presentation the model
+> only sees `run_code`, so `js` would have to be nested as a JavaScript string inside another
+> JavaScript program. `native` keeps `js` directly callable and gives up PTC for that preset.
 
 ### 3. Configure which modes get the capability
 

package/docs/README.zh.md

@@ -79,11 +79,11 @@ node dsh-preset-generator/src/gen-presets.mjs --profile ~/.dsh/profiles/<profile
 | preset | 基底 | 增加 |
 |---|---|---|
 | `daily` | 自带的 `ptc` preset | 一套自己的 Codex 委派 provider |
-| `heavy` | 同上，且 `tool-presentation: both` | 以上全部，且本插件接入 |
+| `heavy` | 同上，且 `tool-presentation: native` | 以上全部，且本插件接入 |
 
-DSH 升级后重跑一次，让副本跟上。`--daily-only` 只生成 `daily`；`--dry-run` 只打印不写；`--out FILE` 写到别处。官方的 `tool-subagent-codex` 行保持**禁用**（和基底一致）：另有一套 provider 自己注册 `subagent_codex`，而两行在同一个 scope 里注册同名工具会冲突。
+DSH 升级后重跑一次，让副本跟上。`--daily-only` 只生成 `daily`；`--dry-run` 只打印不写；`--out FILE` 写到别处。官方的 Codex 工具不再是 per-preset 行：从 DSH 0.2.1 起官方 bundle 提供的是**全局** `subagent_codex`，独立 provider 在这些生成的 preset 里按 Agent 注册同名工具，遮蔽全局那个。同一个 scope 内的两次注册仍会冲突，所以不能在这个 provider 之外再启用同名的 `tool-subagent` 行。
 
-> `heavy` 特意把工具呈现设为 `both`。纯 `ptc` 呈现下模型只看得到 `run_code`，`js` 就得嵌成另一个 JavaScript 程序里的字符串。`both` 让 `js` 可以被直接调用。
+> `heavy` 特意把工具呈现设为 `native`。DSH 0.2.1 移除了旧的 `both` 模式 —— 一个 preset 只能声明一种呈现，`native` 或 `ptc` —— 而纯 `ptc` 呈现下模型只看得到 `run_code`，`js` 就得嵌成另一个 JavaScript 程序里的字符串。`native` 让 `js` 可以被直接调用，代价是该 preset 放弃 PTC。
 
 ### 3. 配置哪些模式能用
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-lcu",
-  "version": "0.3.6",
+  "version": "0.3.7",
   "description": "Drive the desktop and Chrome from DeepSeek Harness using the computer-use runtime inside the ChatGPT desktop application.",
   "keywords": [
     "dsh-plugin",