dsh-patch-edit-plus 0.2.6 → 0.3.1

package/CHANGELOG.md

@@ -1,20 +1,16 @@
 # Changelog
 
 
-## [0.2.6] — 2026-10-01
+## [0.3.1] — 2026-10-01
 
 ### Fixed
-- **A bare multi-file unified diff collapsed into one file section** (ported from the 0.1.7 line, 0.2.5): with no `diff --git` separators, the second file's `--- `/`+++ ` headers rewrote the previous section's paths and its hunks were matched against the wrong content, failing every section after the first with "the context does not match the file". `--- ` now opens a new section whenever the current one is already claimed; parser-level and end-to-end regression tests added.
-## [0.2.2] — 2026-09-29
+- **A bare multi-file unified diff collapsed into one file section** (same defect fixed on the 0.1.7 line in 0.2.5): with no `diff --git` separators, the second file's `--- `/`+++ ` headers rewrote the previous section's paths and its hunks were matched against the wrong content, failing every section after the first with `the context does not match the file`. `--- ` now opens a new section whenever the current one is already claimed; parser-level and end-to-end regression tests added.
+## [0.3.0] — 2026-09-29
 
 ### Changed
-- **DSH line split**: this release serves the `0.1.5-rc` segment only — `peerDependencies`/`engines.dsh` capped to `>=0.1.5-rc.1 <0.1.6-0` (both manifests), published under the `dsh-0.1.5` dist-tag. `0.1.2-rc.1` ~ `0.1.4` remain served by the published `0.1.2` (main); `0.1.7` by `dsh-0.1.7` (v0.2.1+); `0.2.0` by `dsh-0.2.0` (v0.3.0+).
-- devDependencies 4x `@deepseek-ai/dsh-*` `0.1.2-rc.1` → `0.1.5-rc.3`: the type baseline now matches the hosts this line serves (the stale `0.1.2` pin was the "fake green" pattern — a baseline older than the served line can mask real contract breaks).
-- Docs x4 (README/INSTALL): compatibility matrix re-based to the `0.1.5-rc` segment.
 
-### Verified
-- No source changes required: `ShellExecutor.run(spec)` is intact across `0.1.5-rc.1`–`rc.3` (the `run` → `execute` rename lands in the 0.1.6→0.1.7 window), and the imperative settings fallback (`settings.register` / `installSection`) still exists on 0.1.5 hosts.
-- build / typecheck / test (94) / lint / smoke / `typecheck:0.1.5` (static proof against real `0.1.5-rc.2` peers) all green; lockfile regenerated against `0.1.5-rc.3`.
+- **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,20 +1,16 @@
 # 更新日志
 
 
-## [0.2.6] — 2026-10-01
+## [0.3.1] — 2026-10-01
 
 ### 修复
-- **裸多文件 unified diff 被折叠进同一个文件 section**（自 0.1.7 线 0.2.5 移植）：没有 `diff --git` 分隔时，第二个文件的 `--- `/`+++ ` 头改写前一个 section 的路径，其 hunk 被拿到错误内容上匹配，第一个文件之后的每个 section 都报 "the context does not match the file"。现在当前 section 已被认领时 `--- ` 即开新 section；新增解析层与端到端回归测试。
-## [0.2.2] — 2026-09-29
+- **裸多文件 unified diff 被折叠进同一个文件 section**（与 0.1.7 线 0.2.5 修复的同一缺陷）：没有 `diff --git` 分隔时，第二个文件的 `--- `/`+++ ` 头改写前一个 section 的路径，其 hunk 被拿到错误内容上匹配，第一个文件之后的每个 section 都报 `the context does not match the file`。现在当前 section 已被认领时 `--- ` 即开新 section；新增解析层与端到端回归测试。
+## [0.3.0] — 2026-09-29
 
 ### 变更
-- **DSH 线拆分**：本版本只服务 `0.1.5-rc` 线段——`peerDependencies`/`engines.dsh` 封顶到 `>=0.1.5-rc.1 <0.1.6-0`（双清单），经 `dsh-0.1.5` dist-tag 发布。`0.1.2-rc.1` ~ `0.1.4` 仍由已发布的 `0.1.2`（main）服务；`0.1.7` 由 `dsh-0.1.7`（v0.2.1+）服务；`0.2.0` 由 `dsh-0.2.0`（v0.3.0+）服务。
-- devDependencies 4 项 `@deepseek-ai/dsh-*` `0.1.2-rc.1` → `0.1.5-rc.3`：类型基线与本线服务的宿主对齐（过期的 `0.1.2` 钉版正是「假绿」形态——基线早于服务线会掩盖真实契约断裂）。
-- 文档 ×4（README/INSTALL）：兼容矩阵重基于 `0.1.5-rc` 线段。
 
-### 验证
-- 无需源码改动：`ShellExecutor.run(spec)` 在 `0.1.5-rc.1`–`rc.3` 全程未变（`run` → `execute` 改名落在 0.1.6→0.1.7 区间），且 0.1.5 宿主仍有命令式设置回退（`settings.register` / `installSection`）。
-- build / typecheck / test（94）/ lint / smoke / `typecheck:0.1.5`（对真实 `0.1.5-rc.2` peer 静态核验）全绿；lockfile 按 `0.1.5-rc.3` 重新生成。
+- **支持 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.de.md

@@ -0,0 +1,127 @@
+# dsh-patch-edit-plus
+
+Deutsch | [English](./README.md) | [简体中文](./README.zh.md) | [日本語](./README.ja.md) | [한국어](./README.ko.md) | [Français](./README.fr.md) | [Italiano](./README.it.md) | [Русский](./README.ru.md) | [Español](./README.es.md)
+
+Patch-basierte Dateibearbeitung für [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness): ein einzelnes, dem Modell zugängliches `apply_patch`-Werkzeug, das **git/unified diff** (Standard) und die **Codex-`apply_patch`-Syntax** (Opt-in) akzeptiert, jede Änderung nach dem **Alles-oder-Nichts**-Prinzip anwendet und DSH dabei vollständig aus dem Weg geht.
+
+## DSH-Versionskompatibilität
+
+| DSH-Version | Status | Hinweise |
+|---|---|---|
+| `0.2.0-rc.1+` | ✅ unterstützt (diese Linie, v0.3.0+) | Deklarative Einstellungen: `allowCodexPatch` ist mit `.volatile()` markiert — das Einstellungsformular wird automatisch gerendert, und `loader/volatile-update` registriert das Werkzeug ohne Remount neu. Kein Registrierungsaufruf. Delete/Move wurde auf die Foreground-API `ShellExecutor.execute()` + `result()` migriert. |
+| `0.1.7-rc.1+` | ↗ Wartungslinie | Wird vom Zweig `compat/0.1.7` / dem Dist-Tag `dsh-0.1.7` bedient (dort v0.2.1). Der Shell-Executor von 0.2.0 benannte `run` → `execute` um (eingeführt zwischen 0.1.2 und 0.1.7), daher kann eine einzige Codebasis nicht typsicher beide Linien bedienen. |
+| `0.1.2-rc.1` ~ `0.1.5-rc.2` | ↗ Wartungslinie | Wird vom Zweig vor 0.1.7 / dem Dist-Tag `dsh-0.1.5` bedient. 0.1.7 entfernte die imperativen Einstellungs-APIs, auf die der Dual-API-Fallback angewiesen war. |
+
+Einstellungen sind auf dieser Linie deklarativ: In `Config` mit `.volatile()` markierte Felder werden zum Einstellungsformular; das Plugin abonniert `loader/volatile-update`, statt Registrierungs-Hooks zu empfangen.
+
+## Warum überhaupt Patches? (Tool-Routing-Leitfaden)
+
+Die Werkzeugbeschreibung leitet das Modell ausdrücklich:
+
+- **Einzelne kleine Änderung in einer bereits gelesenen Datei** → bevorzugen Sie das native `edit`-Werkzeug (ein Patch kostet mehr Tokens als eine wörtliche Bearbeitung).
+- **Kleine Änderung in einer GROSSEN Datei** → `apply_patch` (die ganze Datei muss nicht zurückgeschickt werden).
+- **Gebündelte Änderungen über VIELE Dateien** → `apply_patch` (ein Aufruf, atomar verifiziert).
+- **Neue Datei mit substanziellem Inhalt / Löschen / Umbenennen** → `apply_patch`.
+
+## Installation
+
+```bash
+dsh plugin --profile web add <path-to-dsh-patch-edit-plus>
+dsh web --dump-config   # verify the plugin row appears
+# restart DSH
+```
+
+## Verwendung
+
+### Unified Diff (Standard, aktiviert)
+
+```text
+--- a/src/app.ts
++++ b/src/app.ts
+@@ -10,4 +10,4 @@ export function main() {
+   init()
+-  start(oldPort)
++  start(newPort)
+   await shutdown()
+ }
+```
+
+### Codex apply_patch-Syntax (Opt-in)
+
+```text
+*** Begin Patch
+*** Update File: src/app.ts
+@@
+   init()
+-  start(oldPort)
++  start(newPort)
+*** Add File: docs/notes.md
++# Notes
+*** Delete File: tmp/junk.txt
+*** Move to: src/app.ts   (via `*** Move to:` after *** Update File:)
+*** End Patch
+```
+
+Aktivieren mit `allowCodexPatch: true`. Trifft ein Codex-Patch ein, während die Option deaktiviert ist, liefert das Werkzeug einen **umsetzbaren Hinweis** (wie man sie aktiviert oder wie man im Unified-Diff-Format wiederholt) statt eines generischen Parse-Fehlers — die Codex-Syntax ist ein starker Prior für Modelle der GPT-Familie, und ein stilles Scheitern fängt sie in Wiederholungsschleifen.
+
+### Operationen
+
+| Operation | Unified Diff | Codex | Ausführungspfad |
+|---|---|---|---|
+| Hinzufügen | `new file mode` + `/dev/null` | `*** Add File:` | `ctx.fs.writeText` (offizieller Intent-Ablauf) |
+| Aktualisieren (multi-hunk) | `@@` hunks | `@@` hunks | `ctx.fs.writeText` |
+| Löschen | `deleted file mode` + `/dev/null` | `*** Delete File:` | `ctx.shell` (sandbox-bewusst, Pfad per env übergeben) |
+| Verschieben / Umbenennen | `rename from/to` | `*** Move to:` | `ctx.shell` |
+
+## Garantien
+
+- **Alles-oder-Nichts**: Der gesamte Patch wird zuerst gegen den aktuellen Dateiinhalt verifiziert (Kontextlokalisierung, Workspace-Eingrenzung, Symlink-Richtlinie, doppelte Pfade); jeder Fehler bricht ab, ohne dass ein einziges Byte geschrieben wurde.
+- **Einhaltung der Read-before-Write-Schranke**: Jeder Schreibvorgang reproduziert den Intent-Ablauf des offiziellen `write`-Werkzeugs — `fs/write-intent`-Wasserfall → geschütztes `writeText` → `fs/observed`-Emission. Ein nacktes `writeText` würde die Schranke still umgehen, da DSH-Provider `fs/*`-Ereignisse nie selbst dispatchen.
+- **Präzise Fehlerdiagnostik**: Bei einer Hunk-Fehlanpassung trägt der Fehler Datei + Hunk-Index, Ursprungszeile der Suche, Vorschau der erwarteten Zeile (Whitespace sichtbar gemacht), den tatsächlichen Dateiauszug sowie einen gezielten Hinweis.
+- **Zeilenende-Treue**: CRLF-Dateien werden als CRLF zurückgeschrieben; Enden ohne abschließenden Zeilenumbruch bleiben erhalten, sofern der Patch das Ende nicht ändert.
+- **Reine Ergänzung**: Das Plugin registriert genau ein Werkzeug, ruft nie `tools.restrict()` auf, überschreibt nie ein natives Werkzeug, registriert keine globalen Dienste und entfernt beim Entladen alles. Namenskonflikte mit anderen `apply_patch`-Providern (`bainianlaoyao/dsh-codex-mode`, `shuind/dsh-codex-harness`, …) werden durch Umbenennungs-Vermeidung gelöst (`apply_patch_1`, `…_2`, …), sodass DSH beim Start nie scheitert.
+
+## Konfiguration
+
+| Option | Standard | Beschreibung |
+|---|---|---|
+| `toolName` | `apply_patch` | Name des dem Modell zugänglichen Werkzeugs. |
+| `conflictPolicy` | `rename` | `rename` / `skip` / `fail`, wenn der Werkzeugname bereits vergeben ist. |
+| `renameSuffix` | `_1` | Suffix, das von der Umbenennungs-Vermeidung verwendet wird. |
+| `allowUnifiedDiff` | `true` | Akzeptiert git/unified diffs. |
+| `allowCodexPatch` | `false` | Akzeptiert die Codex-`apply_patch`-Syntax. Auch im DSH-Einstellungspanel änderbar; Änderungen wirken sofort, kein Neustart nötig. |
+| `deleteBackend` | `shell` | `shell` oder `none` (Delete/Move liefern einen strukturierten Fehler). |
+| `shellDialect` | `auto` | `auto` (pwsh unter win32) / `posix` / `pwsh`. |
+| `deleteCommand` / `moveCommand` | built-in | Eigene Befehlsvorlagen. Pfade kommen weiterhin **ausschließlich per env** an (`DSH_PATCH_TARGET` / `DSH_PATCH_SOURCE`); interpolieren Sie sie nie in den Befehlsstring. |
+| `dryRunByDefault` | `false` | Aufrufe als Probelauf (Dry Run) behandeln, außer bei `dryRun: false`. |
+| `followSymlinks` | `false` | Erlauben, dass Patch-Pfade Symlinks folgen. |
+| `maxFiles` | `50` | Maximale Anzahl Dateiabschnitte pro Patch. |
+| `maxPatchBytes` | `524288` | Maximale Größe des Patch-Texts in Bytes. |
+| `maxDiffBytes` | `16384` | Maximale Größe des je Datei in den Ergebnis-Metadaten behaltenen Diffs (größere Diffs werden geleert und mit `truncated` markiert). |
+
+## Einschränkungen (offengelegt)
+
+- **Delete/Move laufen über `ctx.shell`.** Die Sandbox-Stärke ist genau die, die der geladene Shell-Executor durchsetzt (`bash-sandbox` grenzt ab; `bash-local` nicht) — dieselbe Risikoposition wie beim nativen bash-Werkzeug. Jede Anfrage trägt eine `sandboxPolicy` und berichtet Sandbox-Fakten, damit „Richtlinie verweigert“ von „Befehl fehlgeschlagen“ unterscheidbar ist.
+- **Jeder Schreibvorgang und jeder Delete/Move trägt die Sitzungsbezogene Richtlinie.** `apply_patch` löst `ctx.sandboxPolicy.resolve({ session })` pro Aufruf auf — die Modus-Übersteuerung der Sitzung plus deren cwd als Workspace-Wurzel — genau wie die nativen `write`/`edit`-Werkzeuge, und löst die Planknotenpfade gegen dieselbe Wurzel auf. Ohne sie fällt das durchsetzende Dateisystem auf die Deployment-Wurzel zurück, wodurch Schreibvorgänge im Workspace als `workspace-write`-Verweigerungen fehlschlagen, selbst in einer `danger-full-access`-Sitzung. Eine `workspace-write`-Verweigerung tritt als `PatchError` auf, deren Nachricht den Backend-Text trägt (der strukturierte `[sandbox: …]`-Marker und die Same-Turn-Escalation-Felder sind nicht implementiert; benutzen Sie die nativen `write`/`edit`-Werkzeuge, wenn Sie eskalieren müssen).
+- **Add erzeugt keine übergeordneten Verzeichnisse.** Das entspricht dem nativen `write`-Werkzeug (`ctx.fs` hat kein mkdir); der Fehler nennt das fehlende Verzeichnis.
+- Kein unscharfes/Offset-basiertes Matching: Die Hunk-Lokalisierung ist exakt → `trimEnd` → `trim`, und das absichtlich (unscharfes Matching ist bei destruktiven Operationen unsicher; es steht auf der Roadmap).
+- Binär-Patches werden mit einer klaren Fehlermeldung abgelehnt.
+
+## Entwicklung
+
+```bash
+npm install
+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, …)
+npm run smoke            # load-level smoke against a stub host
+```
+
+Die manuelle Verifikation auf einem laufenden DSH (`dsh plugin --profile web add` → Neustart → Aufruf des Werkzeugs in einer Sitzung) ist bewusst dem Betreiber überlassen.
+
+## Lizenz
+
+MIT

package/README.es.md

@@ -0,0 +1,127 @@
+# dsh-patch-edit-plus
+
+Español | [English](./README.md) | [简体中文](./README.zh.md) | [日本語](./README.ja.md) | [한국어](./README.ko.md) | [Français](./README.fr.md) | [Deutsch](./README.de.md) | [Italiano](./README.it.md) | [Русский](./README.ru.md)
+
+Edición de archivos estilo parche para [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness): una única herramienta `apply_patch` expuesta al modelo, que acepta **diff git/unificado** (por defecto) y la **sintaxis `apply_patch` de Codex** (opcional), aplica cada cambio bajo el principio de **todo-o-nada** y no estorba en absoluto a DSH.
+
+## Compatibilidad de versiones de DSH
+
+| Versión de DSH | Estado | Notas |
+|---|---|---|
+| `0.2.0-rc.1+` | ✅ compatible (esta línea, v0.3.0+) | Ajustes declarativos: `allowCodexPatch` está marcado con `.volatile()` — el formulario de ajustes se genera automáticamente y `loader/volatile-update` vuelve a registrar la herramienta sin remontaje. Sin llamada de registro. Delete/Move migrados a la API de primer plano `ShellExecutor.execute()` + `result()`. |
+| `0.1.7-rc.1+` | ↗ línea de mantenimiento | Atendida por la rama `compat/0.1.7` / el dist-tag `dsh-0.1.7` (v0.2.1 allí). El ejecutor de shell de 0.2.0 renombró `run` → `execute` (cambio introducido entre 0.1.2 y 0.1.7), así que una sola base de código no puede atender ambas líneas de forma type-safe. |
+| `0.1.2-rc.1` ~ `0.1.5-rc.2` | ↗ línea de mantenimiento | Atendida por la rama anterior a 0.1.7 / el dist-tag `dsh-0.1.5`. La 0.1.7 eliminó las API imperativas de ajustes de las que dependía el fallback de doble API. |
+
+En esta línea los ajustes son declarativos: los campos marcados con `.volatile()` en `Config` se convierten en el formulario de ajustes; el plugin se suscribe a `loader/volatile-update` en lugar de recibir hooks de registro.
+
+## ¿Por qué usar parches? (guía de enrutamiento de herramientas)
+
+La descripción de la herramienta dirige explícitamente al modelo:
+
+- **Un único cambio pequeño en un archivo ya leído** → prefiere la herramienta nativa `edit` (un parche cuesta más tokens que una edición literal).
+- **Cambio pequeño dentro de un archivo GRANDE** → `apply_patch` (no hace falta reenviar el archivo entero).
+- **Cambios por lotes en MUCHOS archivos** → `apply_patch` (una sola llamada, verificada atómicamente).
+- **Archivo nuevo con contenido sustancial / borrado / renombrado** → `apply_patch`.
+
+## Instalación
+
+```bash
+dsh plugin --profile web add <path-to-dsh-patch-edit-plus>
+dsh web --dump-config   # verify the plugin row appears
+# restart DSH
+```
+
+## Uso
+
+### Diff unificado (por defecto, activado)
+
+```text
+--- a/src/app.ts
++++ b/src/app.ts
+@@ -10,4 +10,4 @@ export function main() {
+   init()
+-  start(oldPort)
++  start(newPort)
+   await shutdown()
+ }
+```
+
+### Sintaxis apply_patch de Codex (opcional)
+
+```text
+*** Begin Patch
+*** Update File: src/app.ts
+@@
+   init()
+-  start(oldPort)
++  start(newPort)
+*** Add File: docs/notes.md
++# Notes
+*** Delete File: tmp/junk.txt
+*** Move to: src/app.ts   (via `*** Move to:` after *** Update File:)
+*** End Patch
+```
+
+Se activa con `allowCodexPatch: true`. Cuando llega un parche de Codex con la opción desactivada, la herramienta devuelve una **pista accionable** (cómo activarla o cómo reintentar en diff unificado) en lugar de un error genérico de análisis — la sintaxis de Codex es un prior fuerte para los modelos de la familia GPT, y un fallo silencioso los atrapa en bucles de reintentos.
+
+### Operaciones
+
+| Operación | Diff unificado | Codex | Ruta de ejecución |
+|---|---|---|---|
+| Añadir | `new file mode` + `/dev/null` | `*** Add File:` | `ctx.fs.writeText` (secuencia de intent oficial) |
+| Actualizar (multi-hunk) | `@@` hunks | `@@` hunks | `ctx.fs.writeText` |
+| Eliminar | `deleted file mode` + `/dev/null` | `*** Delete File:` | `ctx.shell` (consciente de la sandbox, ruta pasada por env) |
+| Mover / renombrar | `rename from/to` | `*** Move to:` | `ctx.shell` |
+
+## Garantías
+
+- **Todo-o-nada**: el parche completo se verifica primero contra el contenido actual de los archivos (localización del contexto, contención del workspace, política de symlinks, rutas duplicadas); cualquier fallo aborta sin escribir un solo byte.
+- **Se respeta la barrera de leer-antes-de-escribir**: cada escritura replica la secuencia de intent de la herramienta oficial `write` — cascada `fs/write-intent` → `writeText` protegido → emisión `fs/observed`. Un `writeText` a secas sortearía silenciosamente la barrera, porque los providers de DSH nunca despachan ellos mismos los eventos `fs/*`.
+- **Diagnóstico preciso de fallos**: ante un hunk que no coincide, el error incluye archivo + índice del hunk, línea de origen de la búsqueda, vista previa de la línea esperada (con los espacios hechos visibles), el extracto real del archivo y una pista concreta.
+- **Fidelidad de los finales de línea**: los archivos CRLF se reescriben como CRLF; los finales sin salto de línea final se preservan, salvo que el parche cambie el final.
+- **Adición pura**: el plugin registra exactamente una herramienta, nunca llama a `tools.restrict()`, nunca sobrescribe una herramienta nativa, no registra servicios globales y lo elimina todo al descargarse. Los conflictos de nombre con otros proveedores de `apply_patch` (`bainianlaoyao/dsh-codex-mode`, `shuind/dsh-codex-harness`, …) se resuelven evitando el renombrado (`apply_patch_1`, `…_2`, …), de modo que DSH nunca falle al arrancar.
+
+## Configuración
+
+| Opción | Predeterminado | Descripción |
+|---|---|---|
+| `toolName` | `apply_patch` | Nombre de la herramienta expuesta al modelo. |
+| `conflictPolicy` | `rename` | `rename` / `skip` / `fail` cuando el nombre de la herramienta ya está ocupado. |
+| `renameSuffix` | `_1` | Sufijo usado por la evitación del renombrado. |
+| `allowUnifiedDiff` | `true` | Aceptar diffs git/unificados. |
+| `allowCodexPatch` | `false` | Aceptar la sintaxis `apply_patch` de Codex. También editable en el panel de ajustes de DSH; los cambios surten efecto de inmediato, sin reinicio. |
+| `deleteBackend` | `shell` | `shell` o `none` (Delete/Move devuelven un error estructurado). |
+| `shellDialect` | `auto` | `auto` (pwsh en win32) / `posix` / `pwsh`. |
+| `deleteCommand` / `moveCommand` | built-in | Plantillas de comando personalizadas. Las rutas siguen llegando **solo por variables de entorno** (`DSH_PATCH_TARGET` / `DSH_PATCH_SOURCE`); nunca las interpole en la cadena de comando. |
+| `dryRunByDefault` | `false` | Tratar las llamadas como ensayos en seco (dry run) salvo `dryRun: false`. |
+| `followSymlinks` | `false` | Permitir que las rutas del parche atraviesen symlinks. |
+| `maxFiles` | `50` | Número máximo de secciones de archivo por parche. |
+| `maxPatchBytes` | `524288` | Tamaño máximo del texto del parche en bytes. |
+| `maxDiffBytes` | `16384` | Tamaño máximo del diff por archivo conservado en los metadatos del resultado (los diffs mayores se vacían y se marcan como `truncated`). |
+
+## Limitaciones (declaradas)
+
+- **Delete/Move se ejecutan a través de `ctx.shell`.** La fortaleza de la sandbox es la que haga cumplir el ejecutor de shell cargado (`bash-sandbox` aisla; `bash-local` no) — la misma postura de riesgo que la herramienta bash nativa. Cada petición lleva una `sandboxPolicy` e informa de los hechos de la sandbox, de modo que «política denegada» sea distinguible de «comando fallido».
+- **Cada escritura y cada Delete/Move llevan la política con alcance de sesión.** `apply_patch` resuelve `ctx.sandboxPolicy.resolve({ session })` en cada llamada — la anulación de modo de la sesión más su cwd como raíz del workspace — exactamente igual que las herramientas nativas `write`/`edit`, y resuelve las rutas del plan contra esa misma raíz. Sin ello, el sistema de archivos que hace cumplir la política retrocede a la raíz de despliegue, lo que hace que las escrituras dentro del workspace fallen como denegaciones `workspace-write` incluso en una sesión `danger-full-access`. Una denegación `workspace-write` se manifiesta como una `PatchError` cuyo mensaje incluye el texto del backend (el marcador estructurado `[sandbox: …]` y los campos de escalada del mismo turno no están implementados; use las herramientas nativas `write`/`edit` si necesita escalar).
+- **Add no crea los directorios padre.** Esto coincide con la herramienta nativa `write` (`ctx.fs` no tiene mkdir); el error nombra el directorio que falta.
+- Sin coincidencia difusa/por desplazamiento: la localización de los hunks es exacta → `trimEnd` → `trim`, deliberadamente (la coincidencia difusa no es segura para operaciones destructivas; está en la hoja de ruta).
+- Los parches binarios se rechazan con un error claro.
+
+## Desarrollo
+
+```bash
+npm install
+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, …)
+npm run smoke            # load-level smoke against a stub host
+```
+
+La verificación manual sobre un DSH en vivo (`dsh plugin --profile web add` → reinicio → llamada a la herramienta en una sesión) se deja deliberadamente al operador.
+
+## Licencia
+
+MIT

package/README.fr.md

@@ -0,0 +1,127 @@
+# dsh-patch-edit-plus
+
+Français | [English](./README.md) | [简体中文](./README.zh.md) | [日本語](./README.ja.md) | [한국어](./README.ko.md) | [Deutsch](./README.de.md) | [Italiano](./README.it.md) | [Русский](./README.ru.md) | [Español](./README.es.md)
+
+Édition de fichiers en mode patch pour [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness) : un outil unique `apply_patch` exposé au modèle, qui accepte les **diffs git/unifiés** (par défaut) et la **syntaxe `apply_patch` de Codex** (opt-in), applique chaque changement selon le principe du **tout-ou-rien** et reste totalement hors du chemin de DSH.
+
+## Compatibilité des versions de DSH
+
+| Version de DSH | Statut | Notes |
+|---|---|---|
+| `0.2.0-rc.1+` | ✅ pris en charge (cette ligne, v0.3.0+) | Paramètres déclaratifs : `allowCodexPatch` est marqué `.volatile()` — le formulaire de paramètres est généré automatiquement et `loader/volatile-update` réenregistre l'outil sans remontage (remount). Aucun appel d'enregistrement. Delete/Move migrés vers l'API de premier plan `ShellExecutor.execute()` + `result()`. |
+| `0.1.7-rc.1+` | ↗ ligne de maintenance | Assurée par la branche `compat/0.1.7` / le dist-tag `dsh-0.1.7` (v0.2.1 sur cette ligne). L'exécuteur shell de 0.2.0 a renommé `run` → `execute` (changement introduit entre 0.1.2 et 0.1.7) ; une seule base de code ne peut donc pas servir les deux lignes de manière type-safe. |
+| `0.1.2-rc.1` ~ `0.1.5-rc.2` | ↗ ligne de maintenance | Assurée par la branche antérieure à 0.1.7 / le dist-tag `dsh-0.1.5`. La 0.1.7 a supprimé les API impératives de paramétrage dont dépendait le repli bi-API (dual-API fallback). |
+
+Sur cette ligne, les paramètres sont déclaratifs : les champs marqués `.volatile()` dans `Config` constituent le formulaire de paramètres ; le plugin s'abonne à `loader/volatile-update` au lieu de recevoir des hooks d'enregistrement.
+
+## Pourquoi faire des patchs ? (guide de routage des outils)
+
+La description de l'outil oriente explicitement le modèle :
+
+- **Petite modification unique dans un fichier déjà lu** → privilégiez l'outil natif `edit` (un patch coûte plus de tokens qu'une édition littérale).
+- **Petite modification au sein d'un fichier VOLUMINEUX** → `apply_patch` (inutile de renvoyer l'intégralité du fichier).
+- **Modifications groupées sur DE NOMBREUX fichiers** → `apply_patch` (un seul appel, vérifié atomiquement).
+- **Nouveau fichier au contenu substantiel / suppression / renommage** → `apply_patch`.
+
+## Installation
+
+```bash
+dsh plugin --profile web add <path-to-dsh-patch-edit-plus>
+dsh web --dump-config   # verify the plugin row appears
+# restart DSH
+```
+
+## Utilisation
+
+### Diff unifié (par défaut, activé)
+
+```text
+--- a/src/app.ts
++++ b/src/app.ts
+@@ -10,4 +10,4 @@ export function main() {
+   init()
+-  start(oldPort)
++  start(newPort)
+   await shutdown()
+ }
+```
+
+### Syntaxe apply_patch de Codex (opt-in)
+
+```text
+*** Begin Patch
+*** Update File: src/app.ts
+@@
+   init()
+-  start(oldPort)
++  start(newPort)
+*** Add File: docs/notes.md
++# Notes
+*** Delete File: tmp/junk.txt
+*** Move to: src/app.ts   (via `*** Move to:` after *** Update File:)
+*** End Patch
+```
+
+Activez avec `allowCodexPatch: true`. Quand un patch Codex arrive alors que l'option est désactivée, l'outil renvoie une **aide actionnable** (comment l'activer ou comment réessayer en diff unifié) au lieu d'une erreur d'analyse générique — la syntaxe Codex est un prior fort pour les modèles de la famille GPT, et un échec silencieux les enferme dans des boucles de réessai.
+
+### Opérations
+
+| Opération | Diff unifié | Codex | Chemin d'exécution |
+|---|---|---|---|
+| Ajout | `new file mode` + `/dev/null` | `*** Add File:` | `ctx.fs.writeText` (séquence d'intent officielle) |
+| Mise à jour (multi-hunks) | `@@` hunks | `@@` hunks | `ctx.fs.writeText` |
+| Suppression | `deleted file mode` + `/dev/null` | `*** Delete File:` | `ctx.shell` (conscient de la sandbox, chemin passé par env) |
+| Déplacement / renommage | `rename from/to` | `*** Move to:` | `ctx.shell` |
+
+## Garanties
+
+- **Tout-ou-rien** : l'ensemble du patch est d'abord vérifié par rapport au contenu actuel des fichiers (localisation du contexte, confinement de l'espace de travail, politique des symlinks, chemins dupliqués) ; tout échec avorte sans écrire le moindre octet.
+- **Respect du verrou lecture-avant-écriture** : chaque écriture reproduit la séquence d'intent de l'outil `write` officiel — cascade `fs/write-intent` → `writeText` gardé → émission `fs/observed`. Un `writeText` brut contournerait silencieusement ce verrou, car les providers DSH n'émettent jamais eux-mêmes les événements `fs/*`.
+- **Diagnostics d'échec précis** : en cas de hunk non correspondant, l'erreur embarque fichier + index du hunk, ligne d'origine de la recherche, aperçu de la ligne attendue (espaces rendus visibles), extrait réel du fichier, ainsi qu'une indication ciblée.
+- **Fidélité des fins de ligne** : les fichiers CRLF sont réécrits en CRLF ; les fins sans nouvelle ligne finale sont préservées, sauf si le patch modifie la fin.
+- **Pure addition** : le plugin enregistre exactement un outil, n'appelle jamais `tools.restrict()`, ne surcharge jamais un outil natif, n'enregistre aucun service global et supprime tout au déchargement. Les conflits de noms avec d'autres fournisseurs d'`apply_patch` (`bainianlaoyao/dsh-codex-mode`, `shuind/dsh-codex-harness`, …) sont résolus par évitement de renommage (`apply_patch_1`, `…_2`, …), afin que DSH ne tombe jamais en échec au démarrage.
+
+## Configuration
+
+| Option | Par défaut | Description |
+|---|---|---|
+| `toolName` | `apply_patch` | Nom de l'outil exposé au modèle. |
+| `conflictPolicy` | `rename` | `rename` / `skip` / `fail` quand le nom de l'outil est déjà pris. |
+| `renameSuffix` | `_1` | Suffixe utilisé par l'évitement de renommage. |
+| `allowUnifiedDiff` | `true` | Accepte les diffs git/unifiés. |
+| `allowCodexPatch` | `false` | Accepte la syntaxe `apply_patch` de Codex. Également modifiable dans le panneau de paramètres DSH ; les changements prennent effet immédiatement, sans redémarrage. |
+| `deleteBackend` | `shell` | `shell` ou `none` (Delete/Move renvoient une erreur structurée). |
+| `shellDialect` | `auto` | `auto` (pwsh sous win32) / `posix` / `pwsh`. |
+| `deleteCommand` / `moveCommand` | built-in | Modèles de commandes personnalisés. Les chemins n'arrivent toujours **que via les variables d'environnement** (`DSH_PATCH_TARGET` / `DSH_PATCH_SOURCE`) ; ne les interpolez jamais dans la chaîne de commande. |
+| `dryRunByDefault` | `false` | Traiter les appels comme des essais à vide (dry run) sauf si `dryRun: false`. |
+| `followSymlinks` | `false` | Autoriser les chemins de patch à traverser les symlinks. |
+| `maxFiles` | `50` | Nombre maximal de sections de fichiers par patch. |
+| `maxPatchBytes` | `524288` | Taille maximale du texte de patch, en octets. |
+| `maxDiffBytes` | `16384` | Taille maximale du diff par fichier conservé dans les métadonnées du résultat (les diffs plus grands sont vidés et marqués `truncated`). |
+
+## Limitations (divulguées)
+
+- **Delete/Move passent par `ctx.shell`.** La force de la sandbox est celle que l'exécuteur shell chargé fait respecter (`bash-sandbox` cloisonne ; `bash-local` non) — la même posture de risque que l'outil bash natif. Chaque requête porte un `sandboxPolicy` et rapporte les faits relatifs à la sandbox, de sorte qu'un « refus de politique » soit distinguable d'un « échec de commande ».
+- **Chaque écriture et chaque Delete/Move porte la politique à la portée de la session.** `apply_patch` résout `ctx.sandboxPolicy.resolve({ session })` à chaque appel — la surcharge de mode de la session plus son cwd comme racine de l'espace de travail — exactement comme les outils natifs `write`/`edit`, et résout les chemins du plan par rapport à cette même racine. Sans cela, le système de fichiers contraignant retombe sur la racine de déploiement, ce qui fait échouer les écritures intra-espace de travail comme refus `workspace-write`, même dans une session `danger-full-access`. Un refus `workspace-write` se manifeste par une `PatchError` dont le message contient le texte du backend (le marqueur structuré `[sandbox: …]` et les champs d'escalade du même tour ne sont pas implémentés ; utilisez les outils natifs `write`/`edit` si vous devez escalader).
+- **Add ne crée pas les répertoires parents.** Cela correspond à l'outil natif `write` (`ctx.fs` n'a pas de mkdir) ; l'erreur nomme le répertoire manquant.
+- Pas de correspondance floue/avec décalage : la localisation des hunks est exacte → `trimEnd` → `trim`, volontairement (la correspondance floue n'est pas sûre pour les opérations destructrices ; elle figure sur la feuille de route).
+- Les patchs binaires sont rejetés avec une erreur claire.
+
+## Développement
+
+```bash
+npm install
+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, …)
+npm run smoke            # load-level smoke against a stub host
+```
+
+La vérification manuelle sur un DSH en fonctionnement (`dsh plugin --profile web add` → redémarrage → appel de l'outil dans une session) est volontairement laissée à l'opérateur.
+
+## Licence
+
+MIT

package/README.it.md

@@ -0,0 +1,127 @@
+# dsh-patch-edit-plus
+
+Italiano | [English](./README.md) | [简体中文](./README.zh.md) | [日本語](./README.ja.md) | [한국어](./README.ko.md) | [Français](./README.fr.md) | [Deutsch](./README.de.md) | [Русский](./README.ru.md) | [Español](./README.es.md)
+
+Modifica di file in stile patch per [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness): un unico strumento `apply_patch` esposto al modello, che accetta i **diff git/unificati** (predefinito) e la **sintassi `apply_patch` di Codex** (opt-in), applica ogni modifica secondo il principio del **tutto-o-nulla** e resta completamente fuori dai piedi di DSH.
+
+## Compatibilità delle versioni DSH
+
+| Versione DSH | Stato | Note |
+|---|---|---|
+| `0.2.0-rc.1+` | ✅ supportato (questa linea, v0.3.0+) | Impostazioni dichiarative: `allowCodexPatch` è contrassegnato con `.volatile()` — il modulo delle impostazioni viene generato automaticamente e `loader/volatile-update` registra nuovamente lo strumento senza remount. Nessuna chiamata di registrazione. Delete/Move sono migrati all'API in primo piano `ShellExecutor.execute()` + `result()`. |
+| `0.1.7-rc.1+` | ↗ linea di manutenzione | Servita dal ramo `compat/0.1.7` / dal dist-tag `dsh-0.1.7` (v0.2.1 lì). L'esecutore shell di 0.2.0 ha rinominato `run` → `execute` (modifica introdotta tra 0.1.2 e 0.1.7), quindi una singola codebase non può servire entrambe le linee in modo type-safe. |
+| `0.1.2-rc.1` ~ `0.1.5-rc.2` | ↗ linea di manutenzione | Servita dal ramo precedente a 0.1.7 / dal dist-tag `dsh-0.1.5`. La 0.1.7 ha rimosso le API imperative delle impostazioni da cui dipendeva il fallback dual-API. |
+
+Su questa linea le impostazioni sono dichiarative: i campi contrassegnati con `.volatile()` in `Config` diventano il modulo delle impostazioni; il plugin si iscrive a `loader/volatile-update` invece di ricevere hook di registrazione.
+
+## Perché proprio le patch? (guida al routing degli strumenti)
+
+La descrizione dello strumento indirizza esplicitamente il modello:
+
+- **Singola piccola modifica in un file già letto** → preferisci lo strumento nativo `edit` (una patch costa più token di una modifica letterale).
+- **Piccola modifica all'interno di un file GRANDE** → `apply_patch` (non serve rinviare l'intero file).
+- **Modifiche raggruppate su MOLTI file** → `apply_patch` (una sola chiamata, verificata atomicamente).
+- **Nuovo file con contenuto sostanzioso / cancellazione / rinomina** → `apply_patch`.
+
+## Installazione
+
+```bash
+dsh plugin --profile web add <path-to-dsh-patch-edit-plus>
+dsh web --dump-config   # verify the plugin row appears
+# restart DSH
+```
+
+## Utilizzo
+
+### Diff unificato (predefinito, attivo)
+
+```text
+--- a/src/app.ts
++++ b/src/app.ts
+@@ -10,4 +10,4 @@ export function main() {
+   init()
+-  start(oldPort)
++  start(newPort)
+   await shutdown()
+ }
+```
+
+### Sintassi apply_patch di Codex (opt-in)
+
+```text
+*** Begin Patch
+*** Update File: src/app.ts
+@@
+   init()
+-  start(oldPort)
++  start(newPort)
+*** Add File: docs/notes.md
++# Notes
+*** Delete File: tmp/junk.txt
+*** Move to: src/app.ts   (via `*** Move to:` after *** Update File:)
+*** End Patch
+```
+
+Si abilita con `allowCodexPatch: true`. Quando arriva una patch Codex mentre l'opzione è disattivata, lo strumento restituisce un **suggerimento azionabile** (come abilitarla o come riprovare in diff unificato) invece di un generico errore di parsing — la sintassi Codex è un forte prior per i modelli della famiglia GPT, e un fallimento silenzioso li intrappola in cicli di tentativi.
+
+### Operazioni
+
+| Operazione | Diff unificato | Codex | Percorso di esecuzione |
+|---|---|---|---|
+| Aggiunta | `new file mode` + `/dev/null` | `*** Add File:` | `ctx.fs.writeText` (sequenza di intent ufficiale) |
+| Aggiornamento (multi-hunk) | `@@` hunks | `@@` hunks | `ctx.fs.writeText` |
+| Cancellazione | `deleted file mode` + `/dev/null` | `*** Delete File:` | `ctx.shell` (consapevole della sandbox, percorso passato via env) |
+| Spostamento / rinomina | `rename from/to` | `*** Move to:` | `ctx.shell` |
+
+## Garanzie
+
+- **Tutto-o-nulla**: l'intera patch viene prima verificata rispetto al contenuto attuale dei file (localizzazione del contesto, contenimento del workspace, politica dei symlink, percorsi duplicati); qualsiasi fallimento interrompe l'operazione senza scrivere un solo byte.
+- **Rispetto del cancello leggi-prima-di-scrivere**: ogni scrittura replica la sequenza di intent dello strumento `write` ufficiale — cascata `fs/write-intent` → `writeText` protetto → emissione `fs/observed`. Un `writeText` nudo bypasserebbe silenziosamente il cancello, perché i provider DSH non dispatchano mai da soli gli eventi `fs/*`.
+- **Diagnostica dei guasti precisa**: in caso di hunk non corrispondente, l'errore riporta file + indice dell'hunk, riga di origine della ricerca, anteprima della riga attesa (con spazi resi visibili), l'estratto reale del file e un suggerimento mirato.
+- **Fedeltà dei fine riga**: i file CRLF vengono riscritti come CRLF; le code senza newline finale sono preservate, a meno che la patch non modifichi la coda.
+- **Pura aggiunta**: il plugin registra esattamente uno strumento, non chiama mai `tools.restrict()`, non sovrascrive mai uno strumento nativo, non registra servizi globali e rimuove tutto allo scaricamento. I conflitti di nome con altri provider di `apply_patch` (`bainianlaoyao/dsh-codex-mode`, `shuind/dsh-codex-harness`, …) sono risolti evitando la rinomina (`apply_patch_1`, `…_2`, …), così che DSH non fallisca mai l'avvio.
+
+## Configurazione
+
+| Opzione | Predefinito | Descrizione |
+|---|---|---|
+| `toolName` | `apply_patch` | Nome dello strumento esposto al modello. |
+| `conflictPolicy` | `rename` | `rename` / `skip` / `fail` quando il nome dello strumento è già occupato. |
+| `renameSuffix` | `_1` | Suffisso usato dall'evitamento della rinomina. |
+| `allowUnifiedDiff` | `true` | Accetta i diff git/unificati. |
+| `allowCodexPatch` | `false` | Accetta la sintassi `apply_patch` di Codex. Modificabile anche nel pannello delle impostazioni DSH; le modifiche hanno effetto immediato, senza riavvio. |
+| `deleteBackend` | `shell` | `shell` oppure `none` (Delete/Move restituiscono un errore strutturato). |
+| `shellDialect` | `auto` | `auto` (pwsh su win32) / `posix` / `pwsh`. |
+| `deleteCommand` / `moveCommand` | built-in | Modelli di comando personalizzati. I percorsi arrivano comunque **solo tramite le variabili d'ambiente** (`DSH_PATCH_TARGET` / `DSH_PATCH_SOURCE`); non interpolarli mai nella stringa di comando. |
+| `dryRunByDefault` | `false` | Tratta le chiamate come prove a vuoto (dry run) salvo `dryRun: false`. |
+| `followSymlinks` | `false` | Consente ai percorsi delle patch di attraversare i symlink. |
+| `maxFiles` | `50` | Numero massimo di sezioni file per patch. |
+| `maxPatchBytes` | `524288` | Dimensione massima del testo della patch in byte. |
+| `maxDiffBytes` | `16384` | Dimensione massima del diff per file conservato nei metadati del risultato (i diff più grandi vengono svuotati e marcati `truncated`). |
+
+## Limitazioni (dichiarate)
+
+- **Delete/Move passano attraverso `ctx.shell`.** La robustezza della sandbox è quella che l'esecutore shell caricato fa rispettare (`bash-sandbox` isola; `bash-local` no) — la stessa postura di rischio dello strumento bash nativo. Ogni richiesta porta una `sandboxPolicy` e riporta i fatti della sandbox, così che un «rifiuto della politica» sia distinguibile da un «fallimento del comando».
+- **Ogni scrittura e ogni Delete/Move porta la politica nell'ambito della sessione.** `apply_patch` risolve `ctx.sandboxPolicy.resolve({ session })` a ogni chiamata — l'override di modalità della sessione più il suo cwd come radice del workspace — esattamente come gli strumenti nativi `write`/`edit`, e risolve i percorsi del piano rispetto alla stessa radice. Senza di essa, il filesystem di applicazione ricade sulla radice di deployment, il che fa fallire le scritture nel workspace come rifiuti `workspace-write`, persino in una sessione `danger-full-access`. Un rifiuto `workspace-write` emerge come `PatchError` il cui messaggio contiene il testo del backend (il marcatore strutturato `[sandbox: …]` e i campi di escalation nello stesso turno non sono implementati; usate gli strumenti nativi `write`/`edit` quando dovete escalare).
+- **Add non crea le directory madri.** Questo rispecchia lo strumento nativo `write` (`ctx.fs` non ha mkdir); l'errore nomina la directory mancante.
+- Nessuna corrispondenza fuzzy/per offset: la localizzazione degli hunk è esatta → `trimEnd` → `trim`, deliberatamente (il matching fuzzy non è sicuro per le operazioni distruttive; è nella roadmap).
+- Le patch binarie vengono rifiutate con un errore chiaro.
+
+## Sviluppo
+
+```bash
+npm install
+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, …)
+npm run smoke            # load-level smoke against a stub host
+```
+
+La verifica manuale su un DSH in esecuzione (`dsh plugin --profile web add` → riavvio → chiamata dello strumento in una sessione) è lasciata deliberatamente all'operatore.
+
+## Licenza
+
+MIT

package/README.ja.md

@@ -1,15 +1,18 @@
 # dsh-patch-edit-plus
 
+[English](./README.md) | [简体中文](./README.zh.md) | 日本語 | [한국어](./README.ko.md) | [Français](./README.fr.md) | [Deutsch](./README.de.md) | [Italiano](./README.it.md) | [Русский](./README.ru.md) | [Español](./README.es.md)
+
 [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness) 向けのパッチ形式ファイル編集。モデルに公開される単一の `apply_patch` ツールが **git/unified diff**（既定）と **Codex `apply_patch` 構文**（オプトイン）を受け付け、すべての変更を **オール・オア・ナッシング**で適用し、DSH の動作には一切干渉しません。
 
 ## DSH バージョン互換性
 
 | DSH バージョン | ステータス | 備考 |
 |---|---|---|
-| `0.1.5-rc.1+` | ✅ サポート対象（本ライン、v0.2.2+） | 型ベースラインを実在の `0.1.5-rc.3` ピアに固定し、`peerDependencies`/`engines.dsh` は `>=0.1.5-rc.1 <0.1.6-0` にキャップ。`dsh-0.1.5` dist-tag で公開。 |
-| `0.1.2-rc.1` ~ `0.1.4` | ↗ メンテナンスライン | 公開済みの `0.1.2`（main ブランチ）が担います。`0.1.6+` は別契約（shell の `run` → `execute`）であり、compat/0.1.7・compat/0.2.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 を削除しました。 |
 
-設定の登録はデュアル API フォールバック（0.1.2 以降では `settings.installSection`、旧ホストでは `settings.register`）を使用します。
+本ラインの設定は宣言的です：`Config` 内で `.volatile()` を付けたフィールドがそのまま設定フォームになり、プラグインは登録フックの代わりに `loader/volatile-update` を購読します。
 
 ## そもそもなぜパッチなのか？（ツールルーティングガイド）
 
@@ -108,9 +111,9 @@ dsh web --dump-config   # verify the plugin row appears
 
 ```bash
 npm install
-npm run typecheck        # against 0.1.5-rc.3 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

@@ -1,15 +1,18 @@
 # dsh-patch-edit-plus
 
+[English](./README.md) | [简体中文](./README.zh.md) | [日本語](./README.ja.md) | 한국어 | [Français](./README.fr.md) | [Deutsch](./README.de.md) | [Italiano](./README.it.md) | [Русский](./README.ru.md) | [Español](./README.es.md)
+
 [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness)를 위한 패치 스타일 파일 편집 도구입니다. 모델에 노출되는 단일 `apply_patch` 도구가 **git/unified diff**(기본)와 **Codex `apply_patch` 문법**(옵트인)을 받아들이고, 모든 변경을 **전부 아니면 전무(all-or-nothing)** 방식으로 적용하며, DSH의 동작에는 전혀 간섭하지 않습니다.
 
 ## DSH 버전 호환성
 
 | DSH 버전 | 상태 | 비고 |
 |---|---|---|
-| `0.1.5-rc.1+` | ✅ 지원됨(본 라인, v0.2.2+) | 타입 베이스라인을 실제 `0.1.5-rc.3` peer에 고정하고, `peerDependencies`/`engines.dsh`는 `>=0.1.5-rc.1 <0.1.6-0`으로 제한합니다. `dsh-0.1.5` dist-tag로 게시됩니다. |
-| `0.1.2-rc.1` ~ `0.1.4` | ↗ 유지보수 라인 | 게시된 `0.1.2`(main 브랜치)가 담당합니다. `0.1.6+`은 별도 계약(shell `run` → `execute`)이며 compat/0.1.7·compat/0.2.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를 제거했습니다. |
 
-설정 등록은 이중 API 폴백을 사용합니다(0.1.2+ 에서는 `settings.installSection`, 이전 호스트에서는 `settings.register`).
+본 라인의 설정은 선언적입니다: `Config`에서 `.volatile()`로 표시된 필드가 곧 설정 폼이며, 플러그인은 등록 훅 대신 `loader/volatile-update`를 구독합니다.
 
 ## 왜 굳이 패치인가? (도구 라우팅 가이드)
 
@@ -108,9 +111,9 @@ dsh web --dump-config   # verify the plugin row appears
 
 ```bash
 npm install
-npm run typecheck        # against 0.1.5-rc.3 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

@@ -1,15 +1,18 @@
 # dsh-patch-edit-plus
 
+English | [简体中文](./README.zh.md) | [日本語](./README.ja.md) | [한국어](./README.ko.md) | [Français](./README.fr.md) | [Deutsch](./README.de.md) | [Italiano](./README.it.md) | [Русский](./README.ru.md) | [Español](./README.es.md)
+
 Patch-style file editing for [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness): one model-facing `apply_patch` tool that accepts **git/unified diff** (default) and **Codex `apply_patch` syntax** (opt-in), applies every change **all-or-nothing**, and stays completely out of DSH's way.
 
 ## DSH version compatibility
 
 | DSH version | Status | Notes |
 |---|---|---|
-| `0.1.5-rc.1+` | ✅ supported (this line, v0.2.2+) | Type baseline pinned to the real `0.1.5-rc.3` peers; `peerDependencies`/`engines.dsh` capped to `>=0.1.5-rc.1 <0.1.6-0`. Published under the `dsh-0.1.5` dist-tag. |
-| `0.1.2-rc.1` ~ `0.1.4` | ↗ maintenance line | Served by the published `0.1.2` (main branch). `0.1.6+` is a different contract (shell `run` → `execute`) and is served by the compat/0.1.7 and compat/0.2.0 lines. |
+| `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 registration uses the dual-API fallback (`settings.installSection` on 0.1.2+, `settings.register` on older hosts).
+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.
 
 ## Why patch at all? (tool routing guide)
 
@@ -108,9 +111,9 @@ Enable with `allowCodexPatch: true`. When a Codex patch arrives while disabled,
 
 ```bash
 npm install
-npm run typecheck        # against 0.1.5-rc.3 peers (devDependencies)
-npm run typecheck:0.1.5  # static 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.ru.md

@@ -0,0 +1,127 @@
+# dsh-patch-edit-plus
+
+Русский | [English](./README.md) | [简体中文](./README.zh.md) | [日本語](./README.ja.md) | [한국어](./README.ko.md) | [Français](./README.fr.md) | [Deutsch](./README.de.md) | [Italiano](./README.it.md) | [Español](./README.es.md)
+
+Патчевое редактирование файлов для [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness): единственный доступный модели инструмент `apply_patch`, который принимает **git/unified diff** (по умолчанию) и **синтаксис `apply_patch` от Codex** (по явному включению), применяет каждое изменение по принципу **всё-или-ничего** и абсолютно не мешает работе DSH.
+
+## Совместимость с версиями DSH
+
+| Версия DSH | Статус | Примечания |
+|---|---|---|
+| `0.2.0-rc.1+` | ✅ поддерживается (эта линия, v0.3.0+) | Декларативные настройки: `allowCodexPatch` помечен `.volatile()` — форма настроек формируется автоматически, а `loader/volatile-update` перерегистрирует инструмент без перемонтирования. Вызов регистрации не нужен. Delete/Move переведены на foreground-API `ShellExecutor.execute()` + `result()`. |
+| `0.1.7-rc.1+` | ↗ линия сопровождения | Обслуживается веткой `compat/0.1.7` / dist-tag `dsh-0.1.7` (там v0.2.1). Shell-исполнитель 0.2.0 переименовал `run` → `execute` (изменение появилось между 0.1.2 и 0.1.7), поэтому одна кодовая база не может типобезопасно обслуживать обе линии. |
+| `0.1.2-rc.1` ~ `0.1.5-rc.2` | ↗ линия сопровождения | Обслуживается веткой до 0.1.7 / dist-tag `dsh-0.1.5`. В 0.1.7 удалены императивные API настроек, на которых держался двух-API-фолбэк. |
+
+На этой линии настройки декларативны: поля, помеченные `.volatile()` в `Config`, становятся формой настроек; плагин подписывается на `loader/volatile-update` вместо получения регистрационных хуков.
+
+## Зачем вообще патчи? (руководство по маршрутизации инструментов)
+
+Описание инструмента явно направляет модель:
+
+- **Одиночное небольшое изменение в уже прочитанном файле** → предпочитайте нативный инструмент `edit` (патч стоит больше токенов, чем буквальное редактирование).
+- **Небольшое изменение внутри БОЛЬШОГО файла** → `apply_patch` (не нужно повторять весь файл).
+- **Пакетные изменения во МНОГИХ файлах** → `apply_patch` (один вызов, атомарная проверка).
+- **Новый файл с существенным содержимым / удаление / переименование** → `apply_patch`.
+
+## Установка
+
+```bash
+dsh plugin --profile web add <path-to-dsh-patch-edit-plus>
+dsh web --dump-config   # verify the plugin row appears
+# restart DSH
+```
+
+## Использование
+
+### Unified diff (по умолчанию, включён)
+
+```text
+--- a/src/app.ts
++++ b/src/app.ts
+@@ -10,4 +10,4 @@ export function main() {
+   init()
+-  start(oldPort)
++  start(newPort)
+   await shutdown()
+ }
+```
+
+### Синтаксис apply_patch от Codex (по явному включению)
+
+```text
+*** Begin Patch
+*** Update File: src/app.ts
+@@
+   init()
+-  start(oldPort)
++  start(newPort)
+*** Add File: docs/notes.md
++# Notes
+*** Delete File: tmp/junk.txt
+*** Move to: src/app.ts   (via `*** Move to:` after *** Update File:)
+*** End Patch
+```
+
+Включается через `allowCodexPatch: true`. Если патч Codex приходит при выключенной опции, инструмент возвращает **действенную подсказку** (как её включить или как повторить попытку в unified diff) вместо общей ошибки разбора — синтаксис Codex является сильным априорным признаком для моделей семейства GPT, и молчаливый сбой затягивает их в циклы повторов.
+
+### Операции
+
+| Операция | Unified diff | Codex | Путь выполнения |
+|---|---|---|---|
+| Добавление | `new file mode` + `/dev/null` | `*** Add File:` | `ctx.fs.writeText` (официальная intent-последовательность) |
+| Обновление (multi-hunk) | `@@` hunks | `@@` hunks | `ctx.fs.writeText` |
+| Удаление | `deleted file mode` + `/dev/null` | `*** Delete File:` | `ctx.shell` (с учётом sandbox, путь передаётся через env) |
+| Перемещение / переименование | `rename from/to` | `*** Move to:` | `ctx.shell` |
+
+## Гарантии
+
+- **Всё-или-ничего**: весь патч сначала проверяется на соответствие текущему содержимому файлов (локализация контекста, удержание в рабочей области, политика symlink, дубликаты путей); любой сбой прерывает операцию без записи хотя бы байта.
+- **Соблюдение запрета на запись без чтения**: каждая запись воспроизводит intent-последовательность официального инструмента `write` — водопад `fs/write-intent` → защищённый `writeText` → эмиссия `fs/observed`. Голый `writeText` молча обходил бы этот барьер, поскольку провайдеры DSH никогда сами не диспетчеризуют события `fs/*`.
+- **Точная диагностика сбоев**: при несовпадении хунка ошибка содержит файл + индекс хунка, исходную строку поиска, превью ожидаемой строки (с показанными пробелами), фактический фрагмент файла и адресную подсказку.
+- **Точность переводов строк**: файлы CRLF записываются обратно как CRLF; окончания без завершающего перевода строки сохраняются, если только патч не меняет окончание.
+- **Чистое дополнение**: плагин регистрирует ровно один инструмент, никогда не вызывает `tools.restrict()`, никогда не переопределяет нативный инструмент, не регистрирует глобальных служб и при выгрузке удаляет всё. Конфликты имён с другими провайдерами `apply_patch` (`bainianlaoyao/dsh-codex-mode`, `shuind/dsh-codex-harness`, …) разрешаются избеганием переименования (`apply_patch_1`, `…_2`, …), так что DSH никогда не падает при старте.
+
+## Конфигурация
+
+| Опция | По умолчанию | Описание |
+|---|---|---|
+| `toolName` | `apply_patch` | Имя инструмента, доступного модели. |
+| `conflictPolicy` | `rename` | `rename` / `skip` / `fail`, если имя инструмента уже занято. |
+| `renameSuffix` | `_1` | Суффикс, используемый при избегании переименования. |
+| `allowUnifiedDiff` | `true` | Принимать git/unified diff. |
+| `allowCodexPatch` | `false` | Принимать синтаксис `apply_patch` от Codex. Также редактируется в панели настроек DSH; изменения вступают в силу немедленно, без перезапуска. |
+| `deleteBackend` | `shell` | `shell` или `none` (Delete/Move возвращают структурированную ошибку). |
+| `shellDialect` | `auto` | `auto` (pwsh на win32) / `posix` / `pwsh`. |
+| `deleteCommand` / `moveCommand` | built-in | Пользовательские шаблоны команд. Пути по-прежнему передаются **только через переменные окружения** (`DSH_PATCH_TARGET` / `DSH_PATCH_SOURCE`); никогда не подставляйте их в строку команды интерполяцией. |
+| `dryRunByDefault` | `false` | Считать вызовы пробными запусками (dry run), если не задано `dryRun: false`. |
+| `followSymlinks` | `false` | Разрешить путям патча переходить по symlink. |
+| `maxFiles` | `50` | Максимум файловых секций на один патч. |
+| `maxPatchBytes` | `524288` | Максимальный размер текста патча в байтах. |
+| `maxDiffBytes` | `16384` | Максимальный размер диффа на файл, сохраняемого в метаданных результата (большие диффы опустошаются и помечаются `truncated`). |
+
+## Ограничения (раскрытые)
+
+- **Delete/Move выполняются через `ctx.shell`.** Сила sandbox такова, каков обеспечивающий её загруженный shell-исполнитель (`bash-sandbox` изолирует; `bash-local` — нет) — та же позиция риска, что и у нативного инструмента bash. Каждый запрос несёт `sandboxPolicy` и сообщает факты о sandbox, чтобы «отказ политики» можно было отличить от «сбоя команды».
+- **Каждая запись и каждый Delete/Move несут политику в области действия сессии.** `apply_patch` разрешает `ctx.sandboxPolicy.resolve({ session })` при каждом вызове — переопределение режима сессии плюс её cwd как корень рабочей области — в точности как нативные инструменты `write`/`edit`, и разрешает пути плана относительно того же корня. Без этого файловая система принуждения откатывается к корню развёртывания, из-за чего записи внутри рабочей области завершаются отказами `workspace-write` даже в сессии `danger-full-access`. Отказ `workspace-write` проявляется как `PatchError`, сообщение которой несёт текст бэкенда (структурированный маркер `[sandbox: …]` и поля эскалации в том же ходе не реализованы; если нужна эскалация, пользуйтесь нативными `write`/`edit`).
+- **Add не создаёт родительские каталоги.** Это соответствует нативному инструменту `write` (у `ctx.fs` нет mkdir); в ошибке называется недостающий каталог.
+- Нет нечёткого/со смещением сопоставления: локализация хунка точная → `trimEnd` → `trim`, причём намеренно (нечёткое сопоставление небезопасно для разрушающих операций; оно есть в дорожной карте).
+- Двоичные патчи отклоняются с понятной ошибкой.
+
+## Разработка
+
+```bash
+npm install
+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, …)
+npm run smoke            # load-level smoke against a stub host
+```
+
+Ручная проверка на живом DSH (`dsh plugin --profile web add` → перезапуск → вызов инструмента в сессии) намеренно оставлена оператору.
+
+## Лицензия
+
+MIT

package/README.zh.md

@@ -1,15 +1,18 @@
 # dsh-patch-edit-plus
 
+[English](./README.md) | 简体中文 | [日本語](./README.ja.md) | [한국어](./README.ko.md) | [Français](./README.fr.md) | [Deutsch](./README.de.md) | [Italiano](./README.it.md) | [Русский](./README.ru.md) | [Español](./README.es.md)
+
 面向 [DeepSeek Harness（DSH）](https://github.com/deepseek-ai/deepseek-harness) 的补丁风格文件编辑插件：只提供 **1 个**模型可见工具 `apply_patch`，接受 **git/unified diff**（默认开启）与 **Codex `apply_patch` 语法**（可选开启），全量验证后**原子应用**，对 DSH 既有功能零负面影响。
 
 ## DSH 版本适配矩阵
 
 | DSH 版本 | 状态 | 说明 |
 |---|---|---|
-| `0.1.5-rc.1+` | ✅ 支持（本线，v0.2.2+） | 类型基线钉在真实 `0.1.5-rc.3` peer 包；`peerDependencies`/`engines.dsh` 封顶到 `>=0.1.5-rc.1 <0.1.6-0`。经 `dsh-0.1.5` dist-tag 发布。 |
-| `0.1.2-rc.1` ~ `0.1.4` | ↗ 维护线 | 由已发布的 `0.1.2`（main 分支）服务。`0.1.6+` 是另一套契约（shell `run` → `execute`），由 compat/0.1.7 与 compat/0.2.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 注册走双 API 回退：0.1.2+ 的 `settings.installSection` 优先，旧版回退 `settings.register`。
+本线的 settings 是声明式的：`Config` 中标记 `.volatile()` 的字段即设置表单；插件订阅 `loader/volatile-update`，不再接收注册 hooks。
 
 ## 工具路由指引（为什么该用谁）
 
@@ -107,9 +110,9 @@ dsh web --dump-config   # 确认插件行出现
 
 ```bash
 npm install
-npm run typecheck        # 针对 0.1.5-rc.3 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.6",
+  "version": "0.3.1",
   "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.5-rc.1 <0.1.6-0"
+    "dsh": ">=0.2.0-rc.1 <0.2.1-0"
   },
   "components": {
     "host": "lib/index.js"

package/lib/config.js

@@ -12,7 +12,7 @@ export const Config = z.object({
     conflictPolicy: z.union(['rename', 'skip', 'fail']).default('rename'),
     renameSuffix: z.string().default('_1'),
     allowUnifiedDiff: z.boolean().default(true),
-    allowCodexPatch: z.boolean().default(false),
+    allowCodexPatch: z.boolean().default(false).volatile(),
     deleteBackend: z.union(['shell', 'none']).default('shell'),
     shellDialect: z.union(['auto', 'posix', 'pwsh']).default('auto'),
     deleteCommand: z.string(),
@@ -23,6 +23,14 @@ export const Config = z.object({
     maxPatchBytes: z.number().step(1).min(1024).default(512 * 1024),
     maxDiffBytes: z.number().step(1).min(256).default(16 * 1024),
 });
+/** Read a `.volatile()` field: a live ref on 0.1.7+, a plain boolean otherwise. */
+export function readVolatileBoolean(value, fallback) {
+    if (typeof value === 'boolean')
+        return value;
+    if (value && typeof value.get === 'function')
+        return Boolean(value.get());
+    return fallback;
+}
 /** Fill user config with defaults; `undefined`/null entries fall back too. */
 export function resolveConfig(config) {
     const c = config ?? {};
@@ -31,7 +39,7 @@ export function resolveConfig(config) {
         conflictPolicy: c.conflictPolicy ?? 'rename',
         renameSuffix: typeof c.renameSuffix === 'string' ? c.renameSuffix : '_1',
         allowUnifiedDiff: c.allowUnifiedDiff ?? true,
-        allowCodexPatch: c.allowCodexPatch ?? false,
+        allowCodexPatch: readVolatileBoolean(c.allowCodexPatch, false),
         deleteBackend: c.deleteBackend ?? 'shell',
         shellDialect: c.shellDialect ?? 'auto',
         deleteCommand: typeof c.deleteCommand === 'string' && c.deleteCommand !== '' ? c.deleteCommand : undefined,

package/lib/index.js

@@ -4,14 +4,15 @@
  * One `apply_patch` tool accepting git/unified diff (default) and Codex
  * `apply_patch` syntax (opt-in). All-or-nothing application through the
  * official fs write-intent dance; delete/move through the sandbox-aware
- * shell. Compatible with DSH 0.1.2-rc.1 through 0.1.5-rc.2: the tool
- * authoring contract is byte-identical across those versions, so a single
- * code path serves both; only settings registration needs the dual-API
- * fallback (`installSection` first, `register` second).
+ * shell. Targets DSH 0.1.7+: settings are declarative — the fields marked
+ * `.volatile()` in `Config` render the settings form automatically (no
+ * registration call), and `loader/volatile-update` drives re-registration
+ * without a plugin remount. This line drops the pre-0.1.7 hosts; the
+ * 0.1.2-rc.1 ~ 0.1.5-rc.2 line stays on its maintenance branch.
  *
  * @module dsh-patch-edit-plus
  */
-import { Config, resolveConfig } from './config.js';
+import { resolveConfig } from './config.js';
 import { registerApplyPatchTool } from './register.js';
 /** Cordis plugin name used by Loader diagnostics. */
 export const name = 'dsh-patch-edit-plus';
@@ -31,26 +32,21 @@ export const name = 'dsh-patch-edit-plus';
  * in every profile that has no shell capability.
  */
 export const inject = ['tools', 'fs'];
+export { Config } from './config.js';
 /**
- * Settings namespace. Must match dsh-settings `NAMESPACE_PATTERN`
- * (`/^[a-z][a-z0-9-]*$/`) on every target version: letters, digits and
- * hyphens only — an underscore made `register()` throw before anything
- * persisted, so no migration is needed.
+ * Register the tool from the current config snapshot.
+ *
+ * 登记级 key。工具「描述」把可用语法固化进去了（tool.ts 拼 `Accepts ${styles}`），
+ * 所以判定必须覆盖整份 resolved config，而不是只看 allowCodexPatch。
  */
-export const SETTINGS_NAMESPACE = 'patch-edit-plus';
-export { Config };
-/** Register the tool and the settings namespace. Every registration is scoped to this plugin. */
 export function apply(ctx, config) {
+    // 组合条目（0.1.7 起 volatile 字段在其中是 live 引用）：rejudge 每次整体
+    // 重解析一次，一次调用内是同一份快照；跨调用的最新值由事件驱动重取。
     const compositionEntry = config ?? {};
-    // 权威来源：设置层挂载时是解析后的 scope，否则是组合条目。
-    // installSection 保证在每次匹配的 onChange 之前先调用 setSource（attach 与 detach 各一次）。
-    let readSource = () => compositionEntry;
     let disposer = null;
-    // 登记级 key。工具「描述」把可用语法固化进去了（tool.ts 拼 `Accepts ${styles}`），
-    // 所以判定必须覆盖整份 resolved config，而不是只看 allowCodexPatch。
     let registeredKey = null;
     const rejudge = () => {
-        const next = resolveConfig(readSource());
+        const next = resolveConfig(compositionEntry);
         const key = JSON.stringify(next);
         if (key === registeredKey)
             return;
@@ -66,23 +62,9 @@ export function apply(ctx, config) {
             registeredKey = null;
         };
     });
-    ctx.inject(['settings'], (settingsCtx) => {
-        const settings = settingsCtx.settings
-            ?? settingsCtx;
-        if (typeof settings?.installSection === 'function') {
-            settings.installSection(ctx, SETTINGS_NAMESPACE, Config, compositionEntry, {
-                setSource: (current) => { readSource = current; },
-                onChange: () => { rejudge(); },
-            });
-            return;
-        }
-        if (typeof settings?.register === 'function') {
-            const scope = settings.register(SETTINGS_NAMESPACE, Config, { base: compositionEntry });
-            if (scope !== undefined) {
-                readSource = () => scope.get();
-                scope.watch(() => { rejudge(); });
-                rejudge();
-            }
-        }
+    // 0.1.7+: 只有 volatile 字段变更才走这里（不 remount）；普通字段变更会整体
+    // remount 插件，新一次 `apply` 自然读到全部新值。等值变更宿主不通知。
+    ctx.on('loader/volatile-update', () => {
+        rejudge();
     });
 }

package/lib/shellops.js

@@ -36,7 +36,7 @@ export function moveTemplate(cfg) {
 export function resolveShell(ctx) {
     try {
         const shell = ctx.shell;
-        return shell !== undefined && typeof shell.run === 'function' && typeof shell.resolve === 'function' ? shell : undefined;
+        return shell !== undefined && typeof shell.execute === 'function' && typeof shell.resolve === 'function' ? shell : undefined;
     }
     catch {
         return undefined;
@@ -87,7 +87,8 @@ function requireShell(ctx, cfg) {
 }
 async function runShell(shell, request) {
     try {
-        return await shell.run(shell.resolve(request));
+        const execution = await shell.execute(shell.resolve(request));
+        return await execution.result();
     }
     catch (error) {
         const detail = error instanceof Error ? error.message : String(error);

package/lib/types/config.d.ts

@@ -6,6 +6,7 @@
  * @module dsh-patch-edit-plus/config
  */
 import z from '@deepseek-ai/schemastery';
+import type { Volatile } from '@deepseek-ai/cosmokit';
 /** What to do when the configured tool name is already taken at registration. */
 export type ConflictPolicy = 'rename' | 'skip' | 'fail';
 /** Backend used for Delete/Move operations (`ctx.fs` has no delete/move). */
@@ -22,8 +23,10 @@ export interface Config {
     renameSuffix?: string;
     /** Accept git/unified diff patches. Defaults to true. */
     allowUnifiedDiff?: boolean;
-    /** Accept Codex `apply_patch` syntax. Defaults to false. */
-    allowCodexPatch?: boolean;
+    /** Accept Codex `apply_patch` syntax. Defaults to false.
+     * 0.1.7 `.volatile()`: the loader hands `apply` a live `Volatile` ref for this
+     * field — always read it through `readVolatileBoolean`, never cache the ref. */
+    allowCodexPatch?: boolean | Volatile<boolean>;
     /** Delete/Move backend. Defaults to `shell`. `none` rejects Delete/Move with a structured error. */
     deleteBackend?: DeleteBackend;
     /** Shell dialect for the constant delete/move templates. Defaults to `auto` (pwsh on win32). */
@@ -44,7 +47,37 @@ export interface Config {
     maxDiffBytes?: number;
 }
 /** Schemastery schema for Loader defaults and generated configuration docs. */
-export declare const Config: z<Config>;
+export declare const Config: z<Schemastery.ObjectS<NoInfer<{
+    toolName: z<string, string, "defined">;
+    conflictPolicy: z<"rename" | "skip" | "fail", "rename" | "skip" | "fail", "defined">;
+    renameSuffix: z<string, string, "defined">;
+    allowUnifiedDiff: z<boolean, boolean, "defined">;
+    allowCodexPatch: z<boolean, boolean, "volatile-defined">;
+    deleteBackend: z<"shell" | "none", "shell" | "none", "defined">;
+    shellDialect: z<"auto" | "posix" | "pwsh", "auto" | "posix" | "pwsh", "defined">;
+    deleteCommand: z<string, string, "plain">;
+    moveCommand: z<string, string, "plain">;
+    dryRunByDefault: z<boolean, boolean, "defined">;
+    followSymlinks: z<boolean, boolean, "defined">;
+    maxFiles: z<number, number, "defined">;
+    maxPatchBytes: z<number, number, "defined">;
+    maxDiffBytes: z<number, number, "defined">;
+}>>, Schemastery.ObjectT<NoInfer<{
+    toolName: z<string, string, "defined">;
+    conflictPolicy: z<"rename" | "skip" | "fail", "rename" | "skip" | "fail", "defined">;
+    renameSuffix: z<string, string, "defined">;
+    allowUnifiedDiff: z<boolean, boolean, "defined">;
+    allowCodexPatch: z<boolean, boolean, "volatile-defined">;
+    deleteBackend: z<"shell" | "none", "shell" | "none", "defined">;
+    shellDialect: z<"auto" | "posix" | "pwsh", "auto" | "posix" | "pwsh", "defined">;
+    deleteCommand: z<string, string, "plain">;
+    moveCommand: z<string, string, "plain">;
+    dryRunByDefault: z<boolean, boolean, "defined">;
+    followSymlinks: z<boolean, boolean, "defined">;
+    maxFiles: z<number, number, "defined">;
+    maxPatchBytes: z<number, number, "defined">;
+    maxDiffBytes: z<number, number, "defined">;
+}>>, "plain">;
 /** Fully-resolved configuration used by the tool body. */
 export interface ResolvedConfig {
     toolName: string;
@@ -62,5 +95,7 @@ export interface ResolvedConfig {
     maxPatchBytes: number;
     maxDiffBytes: number;
 }
+/** Read a `.volatile()` field: a live ref on 0.1.7+, a plain boolean otherwise. */
+export declare function readVolatileBoolean(value: boolean | Volatile<boolean> | undefined, fallback: boolean): boolean;
 /** Fill user config with defaults; `undefined`/null entries fall back too. */
 export declare function resolveConfig(config: Config | undefined): ResolvedConfig;

package/lib/types/index.d.ts

@@ -4,16 +4,21 @@
  * One `apply_patch` tool accepting git/unified diff (default) and Codex
  * `apply_patch` syntax (opt-in). All-or-nothing application through the
  * official fs write-intent dance; delete/move through the sandbox-aware
- * shell. Compatible with DSH 0.1.2-rc.1 through 0.1.5-rc.2: the tool
- * authoring contract is byte-identical across those versions, so a single
- * code path serves both; only settings registration needs the dual-API
- * fallback (`installSection` first, `register` second).
+ * shell. Targets DSH 0.1.7+: settings are declarative — the fields marked
+ * `.volatile()` in `Config` render the settings form automatically (no
+ * registration call), and `loader/volatile-update` drives re-registration
+ * without a plugin remount. This line drops the pre-0.1.7 hosts; the
+ * 0.1.2-rc.1 ~ 0.1.5-rc.2 line stays on its maintenance branch.
  *
  * @module dsh-patch-edit-plus
  */
 import type { Context } from '@deepseek-ai/cordis';
-import { Config } from './config.js';
 import type { Config as PluginConfig } from './config.js';
+declare module '@deepseek-ai/cordis' {
+    interface Events {
+        'loader/volatile-update': (paths: string[]) => void;
+    }
+}
 /** Cordis plugin name used by Loader diagnostics. */
 export declare const name = "dsh-patch-edit-plus";
 /**
@@ -32,13 +37,11 @@ export declare const name = "dsh-patch-edit-plus";
  * in every profile that has no shell capability.
  */
 export declare const inject: string[];
+export { Config } from './config.js';
 /**
- * Settings namespace. Must match dsh-settings `NAMESPACE_PATTERN`
- * (`/^[a-z][a-z0-9-]*$/`) on every target version: letters, digits and
- * hyphens only — an underscore made `register()` throw before anything
- * persisted, so no migration is needed.
+ * Register the tool from the current config snapshot.
+ *
+ * 登记级 key。工具「描述」把可用语法固化进去了（tool.ts 拼 `Accepts ${styles}`），
+ * 所以判定必须覆盖整份 resolved config，而不是只看 allowCodexPatch。
  */
-export declare const SETTINGS_NAMESPACE = "patch-edit-plus";
-export { Config };
-/** Register the tool and the settings namespace. Every registration is scoped to this plugin. */
 export declare function apply(ctx: Context, config?: PluginConfig): void;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-patch-edit-plus",
-  "version": "0.2.6",
-  "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, and 0.1.5-rc line compatibility (dsh-0.1.5 dist-tag).",
+  "version": "0.3.1",
+  "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.5-rc.1 <0.1.6-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.5-rc.1 <0.1.6-0",
-    "@deepseek-ai/dsh-sandbox": ">=0.1.5-rc.1 <0.1.6-0",
-    "@deepseek-ai/dsh-shell": ">=0.1.5-rc.1 <0.1.6-0",
-    "@deepseek-ai/dsh-tools": ">=0.1.5-rc.1 <0.1.6-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": {
@@ -85,19 +85,23 @@
     }
   },
   "dependencies": {
-    "@deepseek-ai/schemastery": "^3.18.2"
+    "@deepseek-ai/schemastery": "^3.18.4"
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.2",
-    "@deepseek-ai/dsh-fs": "0.1.5-rc.3",
-    "@deepseek-ai/dsh-sandbox": "0.1.5-rc.3",
-    "@deepseek-ai/dsh-shell": "0.1.5-rc.3",
-    "@deepseek-ai/dsh-tools": "0.1.5-rc.3",
+    "@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",
     "typescript": "^5.6.0",
     "typescript-eslint": "^8.0.0",
-    "vitest": "^3.0.0"
+    "vitest": "^3.0.0",
+    "@deepseek-ai/schemastery": "^3.18.4"
+  },
+  "publishConfig": {
+    "tag": "dsh-0.2.0"
   }
 }