dsh-patch-edit-plus 0.2.3 → 0.3.0

package/CHANGELOG.md

@@ -1,17 +1,11 @@
 # Changelog
 
-## [0.2.3] — 2026-09-29
-
-### Fixed
-- **Delete/Move silently degraded to UNSUPPORTED on real 0.1.7 hosts** (defect shipped in 0.2.1): the shell duck-detect looked for `run()`, but DSH renamed `ShellExecutor.run(spec)` → `execute(spec)` (returning a `ShellProcess` handle with a `result()` foreground projection) between 0.1.2 and 0.1.7 — so the detect never matched and Delete/Move always fell back to a structured UNSUPPORTED error. `shellops` now calls `shell.execute(...)` + `await execution.result()` and duck-detects `execute`; shell test mocks moved to the `execute()`/`result()` shape.
+## [0.3.0] — 2026-09-29
 
 ### Changed
-- devDependencies 4x `@deepseek-ai/dsh-*` `0.1.2-rc.1` → `0.1.7-rc.2`: the type baseline now matches the hosts this line serves (the stale pin was the "fake green" pattern — it masked the rename above).
-- Docs x4 (README/INSTALL): compatibility re-based to the `0.1.7` segment; ja/ko matrices were stale at the 0.1.2~0.1.5 wide claim.
-
-## [0.2.1] — 2026-09-25
 
-- First release of the 0.1.7 line (`dsh-0.1.7` dist-tag): declarative settings — `allowCodexPatch` marked `.volatile()`, settings form auto-rendered, tool re-registered in place via `loader/volatile-update` (no remount, no registration call).
+- **DSH 0.2.0 line support (`compat/0.2.0` branch).** Peer ranges and `engines.dsh` (both manifests) now declare `>=0.2.0-rc.1 <0.2.1-0`; version 0.3.0. devDependencies pin the real `0.2.0-rc.1` type baseline, and the cross-check script is upgraded to `npm run typecheck:0.2.0` (installs the real peer packages from the registry). 0.1.x hosts remain served by the `compat/0.1.7` branch / `dsh-0.1.7` dist-tag.
+- **Delete/Move migrated to the current shell executor API.** `ShellExecutor.run(spec)` was renamed `execute(spec)` — returning a `ShellProcess` handle with a `result()` foreground projection — between the 0.1.2 and 0.1.7 host lines. The old devDependency pin (`0.1.2-rc.1`) masked this: the 0.1.7-line package (0.2.1) typechecked green against a stale baseline, and at runtime on real 0.1.7+ hosts its `run`-based duck-typing never matched, so Delete/Move degraded to the structured UNSUPPORTED error. This line calls `shell.execute(...)` and awaits `execution.result()`; the executor is detected via `execute`.
 
 ## [0.1.2] — 2026-09-19
 

package/CHANGELOG.zh.md

@@ -1,17 +1,11 @@
 # 更新日志
 
-## [0.2.3] — 2026-09-29
-
-### 修复
-- **Delete/Move 在真实 0.1.7 宿主上被静默降级为 UNSUPPORTED**（0.2.1 携带的缺陷）：shell 鸭子探测查的是 `run()`，但 DSH 在 0.1.2→0.1.7 之间把 `ShellExecutor.run(spec)` 改名为 `execute(spec)`（返回 `ShellProcess` 句柄 + `result()` 前台投影）——探测永不命中，Delete/Move 一直落到结构化 UNSUPPORTED 错误。`shellops` 现改用 `shell.execute(...)` + `await execution.result()`，鸭子探测改查 `execute`；shell 测试 mock 同步迁移到 `execute()`/`result()` 形态。
+## [0.3.0] — 2026-09-29
 
 ### 变更
-- devDependencies 4 项 `@deepseek-ai/dsh-*` `0.1.2-rc.1` → `0.1.7-rc.2`：类型基线与本线服务的宿主对齐（过期的钉版正是「假绿」形态——它掩盖了上述改名）。
-- 文档 ×4（README/INSTALL）：兼容矩阵重基于 `0.1.7` 线段；ja/ko 矩阵此前停留在 0.1.2~0.1.5 旧态。
-
-## [0.2.1] — 2026-09-25
 
-- 0.1.7 线首发（`dsh-0.1.7` dist-tag）：声明式设置——`allowCodexPatch` 标记 `.volatile()`，设置表单自动生成，工具经 `loader/volatile-update` 原位重注册（不 remount、无注册调用）。
+- **支持 DSH 0.2.0 线（`compat/0.2.0` 分支）。** peer 范围与两份清单的 `engines.dsh` 改为 `>=0.2.0-rc.1 <0.2.1-0`；版本 0.3.0。devDependencies 钉住真实的 `0.2.0-rc.1` 类型基线，交叉校验脚本升级为 `npm run typecheck:0.2.0`（从 registry 干净安装真实 peer 包做核验）。0.1.x 宿主继续由 `compat/0.1.7` 分支 / `dsh-0.1.7` dist-tag 服务。
+- **Delete/Move 迁移到现行 shell 执行器 API。** 宿主在 0.1.2 → 0.1.7 线之间把 `ShellExecutor.run(spec)` 改名为 `execute(spec)`——返回 `ShellProcess` 句柄，前台结果经 `result()` 获取。旧的 devDependency 钉版（`0.1.2-rc.1`）掩盖了这一点：0.1.7 线的包（0.2.1）对过期基线假绿，且在真实 0.1.7+ 宿主上运行时基于 `run` 的鸭子探测永不命中，Delete/Move 实际降级为结构化 UNSUPPORTED 错误。本线改为调用 `shell.execute(...)` 并等待 `execution.result()`；执行器经 `execute` 做结构探测。
 
 ## [0.1.2] — 2026-09-19
 

package/README.ja.md

@@ -6,12 +6,11 @@
 
 | DSH バージョン | ステータス | 備考 |
 |---|---|---|
-| `0.1.7-rc.1+` | ✅ サポート対象（本ライン、v0.2.1+） | 宣言的設定：`allowCodexPatch` を `.volatile()` とマーク — 設定フォームは自動生成され、`loader/volatile-update` が remount なしでツールをその場で再登録します。v0.2.3 は Delete/Move を修正：shell のダックタイピング検出が `run()` を見ていましたが、実 0.1.7 ホストでは決して一致しません（`run` は 0.1.2→0.1.7 の間に `execute` に改名）、Delete/Move は UNSUPPORTED にサイレント降格していました。現在は `execute()` + `result()` を使用。 |
-| `0.1.2-rc.1` ~ `0.1.4` | ↗ メンテナンスライン | 公開済みの `0.1.2`（main ブランチ）が担います。 |
-| `0.1.5-rc.x` | ↗ メンテナンスライン | `dsh-0.1.5` dist-tag（v0.2.2+）が担います。 |
-| `0.2.0-rc.1+` | ↗ 次ライン | `dsh-0.2.0` dist-tag（v0.3.0+）が担います。 |
+| `0.2.0-rc.1+` | ✅ サポート対象（本ライン、v0.3.0+） | 宣言的設定：`allowCodexPatch` は `.volatile()` 付きで、設定フォームは自動生成され、`loader/volatile-update` が再マウントなしでツールをその場で再登録します。登録呼び出しは不要。Delete/Move は `ShellExecutor.execute()` + `result()` フォアグラウンド API に移行済み。 |
+| `0.1.7-rc.1+` | ↗ メンテナンスライン | `compat/0.1.7` ブランチ / `dsh-0.1.7` dist-tag が担当（同ラインの v0.2.1）。0.2.0 より前にシェル実行器の `run` が `execute` に改名されており（0.1.2 → 0.1.7 の間）、1 つのコードベースで両ラインを型安全に支えることはできません。 |
+| `0.1.2-rc.1` ~ `0.1.5-rc.2` | ↗ メンテナンスライン | 0.1.7 以前のブランチ / `dsh-0.1.5` dist-tag が担当。0.1.7 はデュアル API フォールバックが依存する命令型登録 API を削除しました。 |
 
-本ラインの設定は宣言的です：`Config` で `.volatile()` とマークされたフィールドが設定フォームになり、プラグインは登録 hooks を受け取る代わりに `loader/volatile-update` を購読します。
+本ラインの設定は宣言的です：`Config` 内で `.volatile()` を付けたフィールドがそのまま設定フォームになり、プラグインは登録フックの代わりに `loader/volatile-update` を購読します。
 
 ## そもそもなぜパッチなのか？（ツールルーティングガイド）
 
@@ -110,9 +109,9 @@ dsh web --dump-config   # verify the plugin row appears
 
 ```bash
 npm install
-npm run typecheck        # against 0.1.7-rc.2 peers (devDependencies)
-npm run typecheck:0.1.5  # 実在の 0.1.5-rc.2 ピアに対するレガシー交叉検証
-npm test                 # vitest, 90 tests
+npm run typecheck        # against 0.2.0-rc.1 peers (devDependencies)
+npm run typecheck:0.2.0  # against real 0.2.0-rc.1 peer packages installed from the registry (dual-baseline proof)
+npm test                 # vitest, 92 tests
 npm run lint
 npm run build            # lib/
 npm run verify:source    # static safety assertions (intent dance, no node:fs, …)

package/README.ko.md

@@ -6,12 +6,11 @@
 
 | DSH 버전 | 상태 | 비고 |
 |---|---|---|
-| `0.1.7-rc.1+` | ✅ 지원됨(본 라인, v0.2.1+) | 선언적 설정: `allowCodexPatch`에 `.volatile()` 마크 — 설정 폼이 자동 생성되고, `loader/volatile-update`가 remount 없이 도구를 그 자리에서 재등록합니다. v0.2.3은 Delete/Move를 수정: shell 덕 타이핑 감지가 `run()`을 보았으나 실 0.1.7 호스트에서는 결코 일치하지 않았고(`run`은 0.1.2→0.1.7 사이에 `execute`로 개명), Delete/Move가 UNSUPPORTED로 조용히 강등되었습니다. 이제 `execute()` + `result()` 사용. |
-| `0.1.2-rc.1` ~ `0.1.4` | ↗ 유지보수 라인 | 게시된 `0.1.2`(main 브랜치)가 담당합니다. |
-| `0.1.5-rc.x` | ↗ 유지보수 라인 | `dsh-0.1.5` dist-tag(v0.2.2+)가 담당합니다. |
-| `0.2.0-rc.1+` | ↗ 다음 라인 | `dsh-0.2.0` dist-tag(v0.3.0+)가 담당합니다. |
+| `0.2.0-rc.1+` | ✅ 지원됨(본 라인, v0.3.0+) | 선언적 설정: `allowCodexPatch`에 `.volatile()`가 표시되어 설정 폼이 자동 생성되고, `loader/volatile-update`가 리마운트 없이 도구를 그 자리에서 재등록합니다. 등록 호출이 없습니다. Delete/Move는 `ShellExecutor.execute()` + `result()` 포그라운드 API로 이전되었습니다. |
+| `0.1.7-rc.1+` | ↗ 유지보수 라인 | `compat/0.1.7` 브랜치 / `dsh-0.1.7` dist-tag가 담당(해당 라인의 v0.2.1). 0.2.0 이전에 셸 실행기의 `run`이 `execute`로 이름이 바뀌었고(0.1.2 → 0.1.7 사이), 하나의 코드베이스로 두 라인을 타입 안전하게 지원할 수 없습니다. |
+| `0.1.2-rc.1` ~ `0.1.5-rc.2` | ↗ 유지보수 라인 | 0.1.7 이전 브랜치 / `dsh-0.1.5` dist-tag가 담당. 0.1.7은 이중 API 폴백이 의존하던 명령형 등록 API를 제거했습니다. |
 
-본 라인의 설정은 선언적입니다: `Config`에서 `.volatile()`로 마크된 필드가 설정 폼이 되고, 플러그인은 등록 hooks를 받는 대신 `loader/volatile-update`를 구독합니다.
+본 라인의 설정은 선언적입니다: `Config`에서 `.volatile()`로 표시된 필드가 곧 설정 폼이며, 플러그인은 등록 훅 대신 `loader/volatile-update`를 구독합니다.
 
 ## 왜 굳이 패치인가? (도구 라우팅 가이드)
 
@@ -110,9 +109,9 @@ dsh web --dump-config   # verify the plugin row appears
 
 ```bash
 npm install
-npm run typecheck        # against 0.1.7-rc.2 peers (devDependencies)
-npm run typecheck:0.1.5  # 실제 0.1.5-rc.2 peer 대상 레거시 교차 검증
-npm test                 # vitest, 90 tests
+npm run typecheck        # against 0.2.0-rc.1 peers (devDependencies)
+npm run typecheck:0.2.0  # against real 0.2.0-rc.1 peer packages installed from the registry (dual-baseline proof)
+npm test                 # vitest, 92 tests
 npm run lint
 npm run build            # lib/
 npm run verify:source    # static safety assertions (intent dance, no node:fs, …)

package/README.md

@@ -6,10 +6,9 @@ Patch-style file editing for [DeepSeek Harness (DSH)](https://github.com/deepsee
 
 | DSH version | Status | Notes |
 |---|---|---|
-| `0.1.7-rc.1+` | ✅ supported (this line, v0.2.1+) | Declarative settings: `allowCodexPatch` is marked `.volatile()` — the settings form renders automatically and `loader/volatile-update` re-registers the tool without a remount. v0.2.3 fixes Delete/Move: the shell `run()` duck-detect never matched real 0.1.7 hosts (`run` was renamed `execute` between 0.1.2 and 0.1.7), silently degrading them to UNSUPPORTED; now uses `execute()` + `result()`. |
-| `0.1.2-rc.1` ~ `0.1.4` | ↗ maintenance line | Served by the published `0.1.2` (main branch). |
-| `0.1.5-rc.x` | ↗ maintenance line | Served by the `dsh-0.1.5` dist-tag (v0.2.2+). |
-| `0.2.0-rc.1+` | ↗ next line | Served by the `dsh-0.2.0` dist-tag (v0.3.0+). |
+| `0.2.0-rc.1+` | ✅ supported (this line, v0.3.0+) | Declarative settings: `allowCodexPatch` is marked `.volatile()` — the settings form renders automatically and `loader/volatile-update` re-registers the tool without a remount. No registration call. Delete/Move migrated to the `ShellExecutor.execute()` + `result()` foreground API. |
+| `0.1.7-rc.1+` | ↗ maintenance line | Served by the `compat/0.1.7` branch / `dsh-0.1.7` dist-tag (v0.2.1 there). 0.2.0's shell executor renamed `run` → `execute` (introduced between 0.1.2 and 0.1.7), so one codebase cannot serve both lines type-safely. |
+| `0.1.2-rc.1` ~ `0.1.5-rc.2` | ↗ maintenance line | Served by the pre-0.1.7 branch / `dsh-0.1.5` dist-tag. 0.1.7 removed the imperative settings APIs the dual-API fallback relied on. |
 
 Settings are declarative on this line: fields marked `.volatile()` in `Config` become the settings form; the plugin subscribes to `loader/volatile-update` instead of receiving registration hooks.
 
@@ -110,9 +109,9 @@ Enable with `allowCodexPatch: true`. When a Codex patch arrives while disabled,
 
 ```bash
 npm install
-npm run typecheck        # against 0.1.7-rc.2 peers (devDependencies)
-npm run typecheck:0.1.5  # legacy cross-proof against real 0.1.5-rc.2 peers
-npm test                 # vitest, 90 tests
+npm run typecheck        # against 0.2.0-rc.1 peers (devDependencies)
+npm run typecheck:0.2.0  # against real 0.2.0-rc.1 peer packages installed from the registry (dual-baseline proof)
+npm test                 # vitest, 92 tests
 npm run lint
 npm run build            # lib/
 npm run verify:source    # static safety assertions (intent dance, no node:fs, …)

package/README.zh.md

@@ -6,10 +6,9 @@
 
 | DSH 版本 | 状态 | 说明 |
 |---|---|---|
-| `0.1.7-rc.1+` | ✅ 支持（本线，v0.2.1+） | 声明式设置：`allowCodexPatch` 标记 `.volatile()`——设置表单自动生成，`loader/volatile-update` 驱动工具原位重注册（不 remount）。v0.2.3 修复 Delete/Move：shell 鸭子探测查 `run()` 在真实 0.1.7 宿主永不命中（`run` 在 0.1.2→0.1.7 间改名为 `execute`），Delete/Move 被静默降级为 UNSUPPORTED；现改用 `execute()` + `result()`。 |
-| `0.1.2-rc.1` ~ `0.1.4` | ↗ 维护线 | 由已发布的 `0.1.2`（main 分支）服务。 |
-| `0.1.5-rc.x` | ↗ 维护线 | 由 `dsh-0.1.5` dist-tag（v0.2.2+）服务。 |
-| `0.2.0-rc.1+` | ↗ 下一线 | 由 `dsh-0.2.0` dist-tag（v0.3.0+）服务。 |
+| `0.2.0-rc.1+` | ✅ 支持（本线，v0.3.0+） | 声明式设置：`allowCodexPatch` 标记 `.volatile()`——设置表单自动生成，`loader/volatile-update` 驱动工具原位重注册（不 remount），无任何注册调用。Delete/Move 已迁移到 `ShellExecutor.execute()` + `result()` 前台 API。 |
+| `0.1.7-rc.1+` | ↗ 维护线 | 由 `compat/0.1.7` 分支 / `dsh-0.1.7` dist-tag 服务（该线 v0.2.1）。0.2.0 之前 shell 执行器已把 `run` 改名为 `execute`（发生在 0.1.2 → 0.1.7 之间），一份代码无法对两条线同时类型安全。 |
+| `0.1.2-rc.1` ~ `0.1.5-rc.2` | ↗ 维护线 | 由 0.1.7 前的分支 / `dsh-0.1.5` dist-tag 服务。0.1.7 删除了双 API 回退所依赖的命令式注册 API。 |
 
 本线的 settings 是声明式的：`Config` 中标记 `.volatile()` 的字段即设置表单；插件订阅 `loader/volatile-update`，不再接收注册 hooks。
 
@@ -109,9 +108,9 @@ dsh web --dump-config   # 确认插件行出现
 
 ```bash
 npm install
-npm run typecheck        # 针对 0.1.7-rc.2 peer 包（devDependencies）
-npm run typecheck:0.1.5  # 对真实 0.1.5-rc.2 peer 包的遗留交叉核验
-npm test                 # vitest，90 个用例
+npm run typecheck        # 针对 0.2.0-rc.1 peer 包（devDependencies）
+npm run typecheck:0.2.0  # 从 registry 干净安装真实 0.2.0-rc.1 peer 包做类型核验（双基线证明）
+npm test                 # vitest，92 个用例
 npm run lint
 npm run build            # lib/
 npm run verify:source    # 静态安全断言（intent 舞蹈、无 node:fs 等）

package/dsh.plugin.json

@@ -1,7 +1,7 @@
 {
   "id": "dsh-patch-edit-plus",
   "name": "dsh-patch-edit-plus",
-  "version": "0.2.3",
+  "version": "0.3.0",
   "description": {
     "en": "Patch-style file editing: one apply_patch tool for git/unified diff (default) and Codex apply_patch syntax (opt-in), with all-or-nothing application and sandbox-aware delete/move.",
     "zh": "补丁风格文件编辑：单个 apply_patch 工具，接受 git/unified diff（默认）与 Codex apply_patch 语法（可选开启），全量验证后原子应用，删除/移动走沙箱感知 shell。"
@@ -13,7 +13,7 @@
   },
   "license": "MIT",
   "engines": {
-    "dsh": ">=0.1.7-rc.1 <0.1.8-0"
+    "dsh": ">=0.2.0-rc.1 <0.2.1-0"
   },
   "components": {
     "host": "lib/index.js"

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-patch-edit-plus",
-  "version": "0.2.3",
-  "description": "Patch-style file editing for DeepSeek Harness: one apply_patch tool accepting git/unified diff (default) and Codex apply_patch syntax (opt-in), with all-or-nothing application, read-before-write intent dance, sandbox-aware delete/move, with a DSH 0.1.7+ line (declarative volatile settings).",
+  "version": "0.3.0",
+  "description": "Patch-style file editing for DeepSeek Harness: one apply_patch tool accepting git/unified diff (default) and Codex apply_patch syntax (opt-in), with all-or-nothing application, read-before-write intent dance, sandbox-aware delete/move, targeting the DSH 0.2.0 line (declarative volatile settings).",
   "type": "module",
   "repository": {
     "type": "git",
@@ -37,7 +37,7 @@
     "build": "tsc -p tsconfig.build.json",
     "prepublishOnly": "npm run build",
     "typecheck": "tsc -p tsconfig.json",
-    "typecheck:0.1.5": "node scripts/typecheck-0.1.5.mjs",
+    "typecheck:0.2.0": "node scripts/typecheck-0.2.0.mjs",
     "lint": "eslint src tests scripts _smoke",
     "lint:fix": "eslint src tests scripts _smoke --fix",
     "test": "vitest run",
@@ -47,7 +47,7 @@
   },
   "engines": {
     "node": ">=20",
-    "dsh": ">=0.1.7-rc.1 <0.1.8-0"
+    "dsh": ">=0.2.0-rc.1 <0.2.1-0"
   },
   "license": "MIT",
   "keywords": [
@@ -62,10 +62,10 @@
   ],
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-fs": ">=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-sandbox": ">=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-shell": ">=0.1.7-rc.1 <0.1.8-0",
-    "@deepseek-ai/dsh-tools": ">=0.1.7-rc.1 <0.1.8-0"
+    "@deepseek-ai/dsh-fs": ">=0.2.0-rc.1 <0.2.1-0",
+    "@deepseek-ai/dsh-sandbox": ">=0.2.0-rc.1 <0.2.1-0",
+    "@deepseek-ai/dsh-shell": ">=0.2.0-rc.1 <0.2.1-0",
+    "@deepseek-ai/dsh-tools": ">=0.2.0-rc.1 <0.2.1-0"
   },
   "peerDependenciesMeta": {
     "@deepseek-ai/cordis": {
@@ -89,10 +89,10 @@
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.2",
-    "@deepseek-ai/dsh-fs": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-sandbox": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-shell": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-tools": "0.1.7-rc.2",
+    "@deepseek-ai/dsh-fs": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-sandbox": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-shell": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-tools": "0.2.0-rc.1",
     "@eslint/js": "^9.0.0",
     "@types/node": "^22.0.0",
     "eslint": "^9.0.0",