dsh-minimal-ptc 0.4.7 → 0.5.1

package/README.en.md

@@ -1,103 +1,71 @@
-# dsh-minimal-ptc
-
-![npm](https://img.shields.io/npm/v/dsh-minimal-ptc) ![downloads](https://img.shields.io/npm/dm/dsh-minimal-ptc) ![license](https://img.shields.io/github/license/STARDUSTLC666/dsh-minimal-ptc) ![stars](https://img.shields.io/github/stars/STARDUSTLC666/dsh-minimal-ptc?style=social)
-
-> Minimal prompt x full PTC capabilities — a cleaner coding agent.
-> Installing gives you a new agent mode: **Minimal PTC**, with Git Bash and persistent PowerShell on Windows, compatible with Harness 0.1.5-rc.2 and 0.1.6-alpha.1.
-
-## Highlights
-
-- **RL-aligned**: the whole system prompt is one sentence — `You are a helpful software engineer assistant.` — close to the compact instruction distribution used during RL fine-tuning, without long-prompt format bias or context noise.
-- **Complete PTC surface**: provides `run_code` SDK orchestration, files and search, Shell, Skills, plan mode, goals, subagents, Ralph, and web search/fetch; the general-purpose workflow tool stays hidden as in alpha.4.
-- **We / Let's reasoning**: the PTC SDK packs thinking and doing into one TypeScript program, orchestrating multi-step operations before executing them once. This matches the high-scoring Minimal trajectory in DeepSeek's official Project2 V4.1b runs (99/96), where reasoning is dominated by `we` / `let's` instead of the standard-like `let me` / `I` blocks seen at 91/92.
-- **Git Bash on Windows**: ships a preset-local Git Bash executor (GIT_BASH -> Program Files\Git -> LOCALAPPDATA\Git -> PATH). The bash tool is no longer disabled on Windows.
-- **Persistent PowerShell on Windows**: mirrors the `dsh-v0.1.5-rc.1` minimal preset; `pwsh` runs as a persistent PTY session, so cwd, variables, and functions survive across calls.
-
-## Compatibility
-
-Verified with official source builds of Harness `0.1.5-rc.2` and `0.1.6-alpha.1` on 2026-09-16: all 18 components load alongside ModLens, with passing tool schemas, skill registration, offline read-only calls, real Agent preset mounting, and plugin calls through `run_code`. Uses the `cordis.patch.yml` + `dsh.bundle.patch` bundle model. Node requirements are 22.19 or later within 22.x, or 24 or later. Live external-service workflows require separate configuration and validation.
-
-Since 0.4.6, the plugin selects the workflow provider after host startup: `workflow-ptc` on 0.1.6 and `workflow-worker-thread` on 0.1.5. Managed presets refresh when the plugin version or host runtime family changes. Local edits on the same version and runtime, and user-created presets without a marker, remain untouched. Since 0.4.7, the preset restores the official 0.1.6 `ptc` rows `present` / `command-goal` / `tool-plugin-manager` (disabled) plus `modelSelectionSettings` on subagent spawn, and a startup health check guards the `reading 'prepare'` failure modes (see Troubleshooting).
-
-The Minimal PTC preset also mounts in a real agent and assembles `run_code` as the model-facing tool while retaining installed plugin tools and Windows Git Bash. Uses the persona `prefix` field introduced in Harness 0.1.3; use plugin 0.4.3 with older Harness versions. Since 0.4.5, the preset update marker reads the package version automatically so upgrades cannot leave an older preset because of a stale hard-coded version.
-
-## Installation
-
-1. Add this package to a web profile (`package.json`):
-
-   ```json
-   "dependencies": { "dsh-minimal-ptc": "^0.4.0" },
-   "dsh": { "profile": { "bundles": [..., "dsh-minimal-ptc"] } }
-   ```
-
-   Local development can use a link: `"dsh-minimal-ptc": "link:E://deepseek//dsh-minimal-ptc"`.
-
-2. Run `pnpm install` in the profile directory.
-
-3. Restart the web profile process. The host row materializes the bundled preset into `$DSH_HOME/.agent-presets/ptc-minimal`.
-
-4. Select **Minimal PTC** when starting a new session.
-
-## Troubleshooting: `Cannot read properties of undefined (reading 'prepare')`
-
-When every tool call (including `run_code`) fails with this error while sessions mount fine, the root cause is **two identities of the dsh-tools scheduler key (a Symbol) inside one process**. Two confirmed triggers:
-
-1. **A duplicate core package inside a profile**: a third-party plugin lists `@deepseek-ai/*` under `dependencies` (it belongs in `peerDependencies`), a tarball install drags in transitive copies, or stale `node_modules` linger. Check:
-
-   ```bash
-   # Any output means trouble (should be empty)
-   ls ~/.dsh/profiles/*/node_modules/@deepseek-ai 2>/dev/null
-   ```
-
-   Fix: move the `@deepseek-ai` directory out of that profile's `node_modules` (or fix the offending plugin's dependencies and reinstall), then restart dsh.
-
-2. **The 0.1.6-alpha host's own dual build outputs**: the `@deepseek-ai/dsh-tools` exports map routes `./types` and `./presentation` to a second compiled tree (`lib/types/*.js`) next to the bundle (`lib/index.js`) — the key splits even with zero extra copies. The root fix, in `packages/core/tools/src/index.ts`:
-
-   ```ts
-   Symbol('@deepseek-ai/dsh-tools.scheduler')  →  Symbol.for('@deepseek-ai/dsh-tools.scheduler')
-   ```
-
-   `Symbol.for` uses the global symbol registry, so the key stays identical across module instances and both triggers are disarmed.
-
-**Since 0.4.7 this plugin self-checks at startup**: if a profile holds core-package copies, or the host still uses a module-local Symbol key (unpatched), it logs a warning with the matching remediation. Warnings never block startup.
-
-## Uninstall
-
-```bash
-dsh plugin --profile web remove dsh-minimal-ptc
-```
-
-Then restart the web service. To clean up fully, also remove the plugin entry from your profile `cordis.patch.yml` if you overrode it.
-
-
-## Capabilities
-
-- Web search and page fetch are enabled via `tool-web` (`fetch: true`).
-- Subagents and Ralph are enabled; the general-purpose workflow tool remains hidden in PTC mode.
-- `subagent_codex` and `subagent_claude_code` providers are disabled by default; remove their `disabled: true` lines to expose them.
-
-## Windows Git Bash configuration
-
-The preset-local Git Bash executor can be overridden in `agent.cordis.yml` under `gitbash-executor`:
-
-| Option | Default | Meaning |
-| :-- | :-- | :-- |
-| `shellPath` | auto-detected | Fixed Git Bash path (e.g. `C:\\Program Files\\Git\\bin\\bash.exe`) |
-| `timeoutMs` | 120000 | Per-command timeout (ms) |
-| `maxTimeoutMs` | 600000 | Maximum timeout a request may ask for |
-| `maxOutputBytes` | 64000 | Per-call output cap |
-| `maxSpillBytes` | 67108864 | Output spill-to-disk cap |
-| `graceMs` | 3000 | Grace period after timeout |
-
-Detection order: `GIT_BASH` -> `Program Files\\Git` -> `Program Files (x86)\\Git` -> `LOCALAPPDATA\\Programs\\Git` -> PATH.
-
-## Materialization policy
-
-- No target directory -> write all preset files and a version marker.
-- Plugin version or host runtime family changes -> refresh managed files.
-- Directory exists without a marker (treated as user-created) -> leave it untouched.
-- Upgrading: bump `version` in `package.json`; the marker reads it automatically.
-
-## License
-
-MIT
+[中文](README.md)
+
+# dsh-minimal-ptc
+
+## 0.5.1 update (2026-09-27)
+
+Declares the tools service dependency so the startup health check can inspect the tool scheduler on the current Cordis host.
+
+Validation host: Harness 0.1.7-rc.2 built from official sources, retaining the local tool-scheduler fix. Build and automated checks pass; interactive coverage and external-service limits are recorded in this release round.
+
+Adds **Minimal PTC** to DeepSeek Harness: a concise system prompt with files, terminals, search, skills and installed plugin tools, orchestrated through `run_code`. Windows includes Git Bash and persistent PowerShell.
+
+## Install and use
+
+Version 0.5.0 requires **Harness 0.1.7 or later**. Use `dsh-minimal-ptc@0.4.7` on Harness 0.1.5/0.1.6.
+
+```bash
+dsh plugin --profile web add dsh-minimal-ptc
+```
+
+Restart `dsh web`, start a new session and choose **极简 PTC 模式** (Minimal PTC) from the mode picker above the message box. Describe your task normally; no preset directory or YAML editing is required.
+
+For example: “Run this project’s tests, find the failures and fix them.” Existing email, calendar and other plugin tools remain available.
+
+## Changes in 0.5.0
+
+- Registers through the official Harness 0.1.7 declarative Agent preset service, fixing the missing mode after a host upgrade.
+- Installs and updates the preset with the plugin. Existing user content in `.agent-presets/ptc-minimal` is preserved.
+- Checks for conflicting runtime packages without flagging supported helpers such as `schemastery` and `cosmokit`.
+- Uses `workflow-ptc` and retains plugin tools, Git Bash, persistent PowerShell, search, plans, goals and subagents.
+
+## Compatibility and validation
+
+Tested on 2026-09-23 with official-source **Harness 0.1.7-alpha.2**, including a local `Symbol.for` tool-scheduler fix. All 18 plugins load together with passing tool contracts and skill registration. The real Web mode picker lists and selects the preset; a real agent mounts it with `run_code` as its model entry point while retaining plugin tools and the shell.
+
+A real `run_code` call to the RSS plugin passed in a sandboxed Windows workspace and again after restart. The fixture owner has full control of the disposable directory so the host can apply sandbox permissions. External mail, databases and other services still require their own valid configuration.
+
+Requires Node 22.19 or later within 22.x, or 24 or later.
+
+## Windows terminals
+
+A standard Git for Windows installation is detected automatically. For a custom location, set `GIT_BASH` to the full path of `bash.exe` before starting DSH. PowerShell sessions preserve their current directory, variables and functions.
+
+Developers creating their own preset can use the bundled `ptc-minimal.patch.yml` as a reference; the executor module is `dsh-minimal-ptc/gitbash-executor`.
+
+| Executor option | Default | Purpose |
+| :-- | :-- | :-- |
+| `shellPath` | auto-detected | Git Bash path |
+| `timeoutMs` | 120000 | Per-command timeout in ms |
+| `maxTimeoutMs` | 600000 | Maximum requested timeout |
+| `maxOutputBytes` | 64000 | Output cap per call |
+| `maxSpillBytes` | 67108864 | Output spill-to-disk cap |
+| `graceMs` | 3000 | Grace period after timeout |
+
+## Troubleshooting
+
+If the mode is missing, confirm Harness is 0.1.7 or later and restart after installation. Recreating a retired preset directory will not help: the new host does not discover presets there.
+
+If every tool fails with `Cannot read properties of undefined (reading 'prepare')`, check startup logs for duplicate runtime packages. Update the plugin bringing in extra `dsh-tools` / `cordis` copies and reinstall dependencies. Do not remove the entire `@deepseek-ai` directory: public helpers are supported dependencies. Another confirmed cause is the host loading two tool build outputs with a module-local scheduler `Symbol`; source builds can use `Symbol.for('@deepseek-ai/dsh-tools.scheduler')` and rebuild.
+
+## Uninstall
+
+```bash
+dsh plugin --profile web remove dsh-minimal-ptc
+```
+
+Restart the Web service afterward.
+
+## License
+
+MIT

package/README.md

@@ -1,114 +1,71 @@
-# dsh-minimal-ptc
-
-![npm](https://img.shields.io/npm/v/dsh-minimal-ptc) ![downloads](https://img.shields.io/npm/dm/dsh-minimal-ptc) ![license](https://img.shields.io/github/license/STARDUSTLC666/dsh-minimal-ptc) ![stars](https://img.shields.io/github/stars/STARDUSTLC666/dsh-minimal-ptc?style=social)
-
-> 极简提示词 × PTC 全能力 —— 一个更"干净"的编码 Agent。
-> 安装即获得新的 Agent 模式：**极简 PTC 模式**；Windows 自动启用 Git Bash 与持久 PowerShell，兼容 Harness 0.1.5-rc.2 和 0.1.6-alpha.1。
-
-## 卖点
-
-- **对齐 RL 训练**：系统提示词只有一句 `You are a helpful software engineer assistant.`，
-  贴近 RL 微调时的简洁指令分布，没有长提示词带来的格式偏置与上下文噪音，
-  让模型按训练时的节奏干活。
-- **PTC 工具面完整**：提供 `run_code` SDK 多步编排、文件读写与检索、Shell、
-  Skills、计划、目标、子代理、Ralph 与网页搜索/抓取；按 alpha.4 默认隐藏通用 workflow 工具。
-- **We / Let's 思维链**：PTC SDK 把"想"和"做"装进一个 TypeScript 程序，
-  多步操作先编排、再一次执行。这与 DeepSeek 官方跑分环境（Project2 V4.1b）中
-  Minimal 高分轨迹一致：99/96 的两跑以 `we` / `let's` 为主，而不是
-  Standard/PTC 常见的 `let me` / `I` 长块。
-- **Windows 保持 bash**：预设内置 Git Bash executor（自动探测 GIT_BASH → Program Files\Git → LOCALAPPDATA\Git → PATH），`bash` 工具不再在 Windows 上被禁用。
-- **Windows 持久 PowerShell**：对齐 `dsh-v0.1.5-rc.1` 的 minimal 预设，`pwsh` 使用持久 PTY 会话，cwd、变量、函数跨调用保留。
-
-## 兼容性
-
-已在官方源码构建的 Harness `0.1.5-rc.2` 和 `0.1.6-alpha.1` 上验证（2026-09-16）：18 个组件与 ModLens 同载，工具 schema、技能注册、离线只读调用、真实 Agent 预设挂载及 `run_code` 调用插件工具通过。采用 `cordis.patch.yml` + `dsh.bundle.patch` 组合包模型。Node 要求为 22.19 及以上的 22.x，或 24 及以上。外部服务的实际业务操作需按各组件配置单独验证。
-
-0.4.6 起，插件等待宿主启动完成后选择工作流运行时：0.1.6 使用 `workflow-ptc`，0.1.5 保留 `workflow-worker-thread`。受管理的预设会在插件版本或运行时种类变化时刷新；同版本、同运行时的本地修改以及无版本标记的自建预设保持不变。0.4.7 起预设补齐官方 0.1.6 `ptc` 的 `present` / `command-goal` / `tool-plugin-manager`（默认关闭）行与 subagent 的 `modelSelectionSettings`，并新增启动健康检查（见下文故障排查）。
-
-另已在真实 agent 中挂载极简 PTC 预设并组装模型工具：模型入口为 `run_code`，安装的插件工具和 Windows Git Bash 均可用。沿用 0.1.3 起的 persona `prefix` 字段；更旧的 Harness 请使用插件 0.4.3。0.4.5 起，预设更新标记自动读取包版本，避免升级后仍保留旧预设。
-
-## 安装
-
-1. 把本包加入 web profile（`package.json`）：
-
-   ```json
-   "dependencies": { "dsh-minimal-ptc": "^0.4.0" },
-   "dsh": { "profile": { "bundles": [..., "dsh-minimal-ptc"] } }
-   ```
-
-   本地开发也可以用 link：`"dsh-minimal-ptc": "link:E://deepseek//dsh-minimal-ptc"`。
-
-2. 在 profile 目录执行 `pnpm install`。
-
-3. 重启 web profile 进程：宿主行会把内置预设物化到
-   `$DSH_HOME/.agent-presets/ptc-minimal`。
-
-4. 新建会话时选择 **极简 PTC 模式**。
-
-## 故障排查：`Cannot read properties of undefined (reading 'prepare')`
-
-每次工具调用（含 `run_code`）都以这个错误失败、且会话在挂载期一切正常时，根因是 **dsh-tools 的调度器键（一个 Symbol）在进程内出现了两个身份**。两个已确认的触发路径：
-
-1. **profile 里多装了一份核心包**：某个第三方插件把 `@deepseek-ai/*` 写进了 `dependencies`（应为 `peerDependencies`）、tarball 安装拖入传递副本，或旧 `node_modules` 残留。检查：
-
-   ```bash
-   # 任一命令有输出即为中招（应为空）
-   ls ~/.dsh/profiles/*/node_modules/@deepseek-ai 2>/dev/null
-   ```
-
-   修复：把该 profile `node_modules` 下的 `@deepseek-ai` 目录移走（或整改插件依赖后重装），重启 dsh。
-
-2. **0.1.6-alpha 宿主自身的双构建产物**：`@deepseek-ai/dsh-tools` 的 exports 把 `./types`、`./presentation` 子路径指向第二套编译输出（`lib/types/*.js`），与打包产物 `lib/index.js` 并存时调度器键同样分裂——即使没有装任何多余副本也会中招。根治办法是把 `packages/core/tools/src/index.ts` 里的
-
-   ```ts
-   Symbol('@deepseek-ai/dsh-tools.scheduler')  →  Symbol.for('@deepseek-ai/dsh-tools.scheduler')
-   ```
-
-   `Symbol.for` 走全局符号注册表，跨模块实例恒等，两类触发路径同时免疫。
-
-**本插件自 0.4.7 起在启动时自动体检**：发现 profile 内核心包副本、或宿主仍使用模块本地 Symbol 键（未打上述补丁）时，会在日志里给出对应警告与修复指引（只警告，不阻断启动）。
-
-## 卸载
-
-```bash
-dsh plugin --profile web remove dsh-minimal-ptc
-```
-
-卸载后重启 Web 服务。如需彻底清理，可再手动删除自己 profile `cordis.patch.yml` 中覆盖的插件行。
-
-
-## Windows Git Bash 配置
-
-预设内置的 Git Bash executor 可在 `agent.cordis.yml` 的 `gitbash-executor` 行覆盖：
-
-| 配置 | 默认 | 说明 |
-| :-- | :-- | :-- |
-| `shellPath` | 自动探测 | 固定 Git Bash 路径（如 `C:\\Program Files\\Git\\bin\\bash.exe`） |
-| `timeoutMs` | 120000 | 单次命令超时（毫秒） |
-| `maxTimeoutMs` | 600000 | 请求可要求的最大超时 |
-| `maxOutputBytes` | 64000 | 单次输出上限 |
-| `maxSpillBytes` | 67108864 | 输出溢出落盘上限 |
-| `graceMs` | 3000 | 超时后的宽限时间 |
-
-自动探测顺序：`GIT_BASH` → `Program Files\\Git` → `Program Files (x86)\\Git` → `LOCALAPPDATA\\Programs\\Git` → PATH。
-
-## 目录结构
-
-```
-dsh-minimal-ptc/
-├── cordis.patch.yml              # 插入宿主行（物化预设）
-├── lib/index.js                  # 宿主插件：物化 ptc-minimal 预设到用户预设根目录
-└── presets/ptc-minimal/          # 内置 Agent 模式（极简提示词 + PTC 全能力）
-    ├── agent.cordis.yml
-    ├── gitbash-executor.mjs      # Windows Git Bash 探测与执行器（零依赖）
-    └── preset.yml
-```
-
-## 说明
-
-- 物化策略：目标目录不存在时写入全部文件；插件版本或宿主运行时种类变化时刷新受管理文件；无标记的自建预设不覆盖。
-- 升级插件只需更新 `package.json` 的版本；预设标记自动读取该版本。
-
-## 许可证
-
-MIT
+[English](README.en.md)
+
+# dsh-minimal-ptc
+
+## 0.5.1 更新（2026-09-27）
+
+补齐 tools 服务依赖声明，让启动健康检查可以在新版 Cordis 宿主中读取工具调度器。
+
+验证宿主：官方源码构建的 Harness 0.1.7-rc.2（保留本地工具调度器修复）。构建与自动测试通过；实际操作和外部服务限制见本轮验收记录。
+
+给 DeepSeek Harness 添加「极简 PTC 模式」：使用简短的系统提示词，保留文件、终端、搜索、技能与已安装插件，通过 `run_code` 编排多步操作。Windows 支持 Git Bash 和持久 PowerShell。
+
+## 安装和使用
+
+0.5.0 需要 **Harness 0.1.7 及以上**。仍使用 Harness 0.1.5/0.1.6 时，请安装 `dsh-minimal-ptc@0.4.7`。
+
+```bash
+dsh plugin --profile web add dsh-minimal-ptc
+```
+
+重启 `dsh web`，新建会话，在输入框上方的模式列表中选择 **极简 PTC 模式**，然后像平时一样描述任务。无需创建预设目录或修改 YAML。
+
+例如：「检查这个项目的测试，找出失败原因并修复。」已有的邮件、日历等插件也可按原来的方式使用。
+
+## 0.5.0 的变化
+
+- 使用 Harness 0.1.7 官方的声明式 Agent 预设注册方式，修复升级后模式消失的问题。
+- 预设随插件安装和更新；保留用户旧的 `.agent-presets/ptc-minimal` 目录，不覆盖其中的自定义内容。
+- 启动检查只提示会影响工具运行的核心包副本，不再把 `schemastery`、`cosmokit` 等正常依赖误报为冲突。
+- 使用新版 `workflow-ptc`，保留插件工具、Git Bash、持久 PowerShell、搜索、计划、目标与子代理能力。
+
+## 兼容性与验证
+
+2026-09-23 在官方源码构建的 **Harness 0.1.7-alpha.2** 上验证（含本地工具调度器 `Symbol.for` 修复）：18 个插件同载，工具契约与技能注册通过；极简 PTC 出现在实际网页模式列表中并可选择，真实 Agent 挂载后以 `run_code` 为模型入口，保留插件工具与 Shell。
+
+已在沙箱开启的 Windows 隔离工作区通过 `run_code` 实际调用 RSS 插件，重启后再次通过。测试工作区由当前用户拥有完整管理权限，以便宿主设置沙箱权限；外部邮箱、数据库等业务仍需各插件的有效配置。
+
+Node 要求为 22.19 及以上的 22.x，或 24 及以上。
+
+## Windows 终端
+
+安装常规版 Git for Windows 后会自动找到 Git Bash。若安装在自定义位置，可设置 `GIT_BASH` 为 `bash.exe` 的完整路径，再启动 DSH。PowerShell 会话会保留当前目录、变量和函数。
+
+开发者如需自建预设，可参考包内的 `ptc-minimal.patch.yml`，执行器模块为 `dsh-minimal-ptc/gitbash-executor`。
+
+| 执行器选项 | 默认值 | 作用 |
+| :-- | :-- | :-- |
+| `shellPath` | 自动探测 | 指定 Git Bash 路径 |
+| `timeoutMs` | 120000 | 单次命令超时，毫秒 |
+| `maxTimeoutMs` | 600000 | 允许请求的最长超时 |
+| `maxOutputBytes` | 64000 | 单次输出上限 |
+| `maxSpillBytes` | 67108864 | 输出落盘上限 |
+| `graceMs` | 3000 | 超时后的退出宽限时间 |
+
+## 排错
+
+模式未出现时，先确认 DSH 为 0.1.7 及以上且安装后已重启。不要通过重建旧预设目录解决，新宿主不再从该目录发现预设。
+
+若每个工具都报 `Cannot read properties of undefined (reading 'prepare')`，查看启动日志中的核心包冲突提示。应升级带入额外 `dsh-tools` / `cordis` 副本的插件并重新安装依赖；不要删除整个 `@deepseek-ai` 目录，官方的公共辅助包属于正常依赖。另一个已确认原因是宿主同时加载两份工具构建产物且调度器键使用模块局部 `Symbol`；源码构建可将其改为 `Symbol.for('@deepseek-ai/dsh-tools.scheduler')` 后重新构建。
+
+## 卸载
+
+```bash
+dsh plugin --profile web remove dsh-minimal-ptc
+```
+
+重启 Web 服务后生效。
+
+## License
+
+MIT

package/lib/index.js

@@ -1,167 +1,172 @@
-// dsh-minimal-ptc 宿主行：把内置的 ptc-minimal 预设物化到用户预设根目录。
-//
-// 预设发现是实时重读的，因此安装完成后重启一次 web profile 进程，
-// 选择器里就会出现「极简 PTC 模式」。
-//
-// 物化策略：目标目录不存在 → 写入全部文件并留版本标记；
-// 版本标记低于当前版本 → 用插件自带文件刷新；
-// 目录存在但无标记（视为用户自建）→ 不覆盖。
-//
-// 零运行时依赖：harness home 的解析逻辑内置（DSH_HOME 环境变量优先，
-// 否则 ~/.dsh），与 dsh 官方规则一致。
-import { mkdirSync, readFileSync, writeFileSync, existsSync, readdirSync } from 'node:fs'
-import { homedir } from 'node:os'
-import { join, resolve } from 'node:path'
-import { fileURLToPath } from 'node:url'
-import pkg from '../package.json' with { type: 'json' }
-
-export const name = 'ptc-minimal-preset'
-export const inject = ['appReady']
-
-const VERSION = pkg.version
-const PRESET_ID = 'ptc-minimal'
-const MARKER = '.dsh-ptc-minimal.version'
-
-// dsh-tools keys its tool scheduler with this symbol description. On stock
-// hosts it is a module-local Symbol(), so any second dsh-tools instance
-// (duplicate profile copy, or the package's own dual build outputs on
-// 0.1.6-alpha) breaks the agent-loop lookup: every tool call then fails with
-// "Cannot read properties of undefined (reading 'prepare')".
-const SCHEDULER_SYMBOL_DESC = '@deepseek-ai/dsh-tools.scheduler'
-
-const packageDir = fileURLToPath(new URL('..', import.meta.url))
-const presetSourceDir = join(packageDir, 'presets', PRESET_ID)
-
-/** 与 @deepseek-ai/dsh-home-paths 相同的解析规则：DSH_HOME > ~/.dsh。 */
-function dshHomePath(...segments) {
-  const env = process.env.DSH_HOME
-  const fromEnv = typeof env === 'string' && env.trim().length > 0 ? env : null
-  let base = fromEnv ?? join(homedir(), '.dsh')
-  if (base === '~') base = homedir()
-  if (base.startsWith('~/') || base.startsWith('~\\')) base = join(homedir(), base.slice(2))
-  return resolve(base, ...segments)
-}
-
-function materialize(logger, modernRuntime) {
-  const dir = dshHomePath('.agent-presets', PRESET_ID)
-  mkdirSync(dir, { recursive: true })
-  const revision = modernRuntime ? `${VERSION}:ptc-runtime` : VERSION
-
-  let marker = null
-  try {
-    marker = readFileSync(join(dir, MARKER), 'utf8').trim()
-  } catch {
-    // 无标记：可能是首次安装，也可能是用户自建目录
-  }
-
-  if (marker === revision) return
-  if (marker === null && existsSync(join(dir, 'agent.cordis.yml'))) {
-    logger?.warn(`dsh-minimal-ptc: ${dir} exists without our marker; leaving it alone`)
-    return
-  }
-
-  for (const file of ['agent.cordis.yml', 'preset.yml', 'gitbash-executor.mjs']) {
-    let content = readFileSync(join(presetSourceDir, file), 'utf8')
-    if (modernRuntime && file === 'agent.cordis.yml') {
-      content = content.replaceAll('workflow-worker-thread', 'workflow-ptc')
-        .replaceAll('`codeRuntime`', '`ptcRuntime`')
-    }
-    writeFileSync(join(dir, file), content)
-  }
-  writeFileSync(join(dir, MARKER), revision + '\n')
-  logger?.info(`dsh-minimal-ptc: materialized agent preset "${PRESET_ID}" into ${dir}`)
-}
-
-export function apply(ctx) {
-  ctx.effect(() => ctx.appReady.onReady(() => {
-    try {
-      materialize(ctx.logger, ctx.get('ptcRuntime') !== undefined)
-    } catch (error) {
-      ctx.logger?.warn(`dsh-minimal-ptc: preset materialization failed: ${String(error)}`)
-    }
-    try {
-      healthCheck(ctx)
-    } catch (error) {
-      ctx.logger?.warn(`dsh-minimal-ptc: health check failed: ${String(error)}`)
-    }
-  }))
-}
-
-/**
- * Warn about the two known causes of "Cannot read properties of undefined
- * (reading 'prepare')" before the first session hits them. Warnings only —
- * nothing here blocks startup.
- */
-function healthCheck(ctx) {
-  const logger = ctx.logger
-
-  // Cause 1 (most common in the wild): a plugin or stale install left a
-  // physical copy of @deepseek-ai/* inside some profile's node_modules. The
-  // core must come from the CLI's own dependency tree only.
-  for (const hit of findProfileCoreCopies()) {
-    logger?.warn(
-      `dsh-minimal-ptc: duplicate core package in profile: ${hit}\n`
-      + '  A second @deepseek-ai copy breaks the tool scheduler key (module-local Symbol) '
-      + 'and every tool call fails with "reading \'prepare\'".\n'
-      + '  Fix: remove the @deepseek-ai directory from that profile\'s node_modules '
-      + '(and reinstall the offending plugin with core packages in peerDependencies), then restart.',
-    )
-  }
-
-  // Cause 2 (seen on stock 0.1.6-alpha): the host itself can load two dsh-tools
-  // instances (bundled lib/index.js vs per-module lib/types/*.js). It is safe
-  // only when the scheduler key survives multiple instances, i.e. the host was
-  // built with Symbol.for. Probe exactly that.
-  const status = schedulerKeyStatus(ctx.tools)
-  if (status === 'module-local') {
-    logger?.warn(
-      'dsh-minimal-ptc: this host keys the tool scheduler with a module-local Symbol '
-      + '(unpatched dsh-tools). PTC sessions break with "reading \'prepare\'" '
-      + 'whenever a second dsh-tools instance loads in this process.\n'
-      + '  Fix: rebuild dsh-tools with `Symbol.for(\'@deepseek-ai/dsh-tools.scheduler\')` '
-      + 'in packages/core/tools/src/index.ts, or keep a single dsh-tools copy.',
-    )
-  }
-}
-
-/**
- * Physical @deepseek-ai copies under any profile's node_modules.
- * @returns {string[]} paths like "<profile>/node_modules/@deepseek-ai/<pkg>"
- */
-export function findProfileCoreCopies(home = dshHomePath('profiles')) {
-  const hits = []
-  let profiles = []
-  try {
-    profiles = readdirSync(home, { withFileTypes: true })
-  } catch {
-    return hits
-  }
-  for (const profile of profiles) {
-    if (!profile.isDirectory()) continue
-    const scopeDir = join(home, profile.name, 'node_modules', '@deepseek-ai')
-    let entries = []
-    try {
-      entries = readdirSync(scopeDir, { withFileTypes: true })
-    } catch {
-      continue
-    }
-    for (const entry of entries) {
-      if (entry.isDirectory()) hits.push(join(scopeDir, entry.name))
-    }
-  }
-  return hits
-}
-
-/**
- * How the host's tool registry exposes the scheduler key:
- * - 'global'       — Symbol.for key works; safe across duplicate instances.
- * - 'module-local' — registry carries a same-description local Symbol; the
- *                    agent loop breaks if a second dsh-tools instance loads.
- * - 'absent'       — no tools registry / no scheduler mounted (nothing to say).
- */
-export function schedulerKeyStatus(tools) {
-  if (tools == null || (typeof tools !== 'object' && typeof tools !== 'function')) return 'absent'
-  if (tools[Symbol.for(SCHEDULER_SYMBOL_DESC)] !== undefined) return 'global'
-  const local = Object.getOwnPropertySymbols(tools).some(s => s.description === SCHEDULER_SYMBOL_DESC)
-  return local ? 'module-local' : 'absent'
-}
+// dsh-minimal-ptc 宿主行：把内置的 ptc-minimal 预设物化到用户预设根目录。
+//
+// 预设发现是实时重读的，因此安装完成后重启一次 web profile 进程，
+// 选择器里就会出现「极简 PTC 模式」。
+//
+// 物化策略：目标目录不存在 → 写入全部文件并留版本标记；
+// 版本标记低于当前版本 → 用插件自带文件刷新；
+// 目录存在但无标记（视为用户自建）→ 不覆盖。
+//
+// 零运行时依赖：harness home 的解析逻辑内置（DSH_HOME 环境变量优先，
+// 否则 ~/.dsh），与 dsh 官方规则一致。
+import { mkdirSync, readFileSync, writeFileSync, existsSync, readdirSync } from 'node:fs'
+import { homedir } from 'node:os'
+import { join, resolve } from 'node:path'
+import { fileURLToPath } from 'node:url'
+import pkg from '../package.json' with { type: 'json' }
+
+export const name = 'ptc-minimal-preset'
+export const inject = ['appReady', 'tools']
+
+const VERSION = pkg.version
+const PRESET_ID = 'ptc-minimal'
+const MARKER = '.dsh-ptc-minimal.version'
+
+// dsh-tools keys its tool scheduler with this symbol description. On stock
+// hosts it is a module-local Symbol(), so any second dsh-tools instance
+// (duplicate profile copy, or the package's own dual build outputs on
+// 0.1.6-alpha) breaks the agent-loop lookup: every tool call then fails with
+// "Cannot read properties of undefined (reading 'prepare')".
+const SCHEDULER_SYMBOL_DESC = '@deepseek-ai/dsh-tools.scheduler'
+
+const packageDir = fileURLToPath(new URL('..', import.meta.url))
+const presetSourceDir = join(packageDir, 'presets', PRESET_ID)
+
+/** 与 @deepseek-ai/dsh-home-paths 相同的解析规则：DSH_HOME > ~/.dsh。 */
+function dshHomePath(...segments) {
+  const env = process.env.DSH_HOME
+  const fromEnv = typeof env === 'string' && env.trim().length > 0 ? env : null
+  let base = fromEnv ?? join(homedir(), '.dsh')
+  if (base === '~') base = homedir()
+  if (base.startsWith('~/') || base.startsWith('~\\')) base = join(homedir(), base.slice(2))
+  return resolve(base, ...segments)
+}
+
+function materialize(logger, modernRuntime) {
+  const dir = dshHomePath('.agent-presets', PRESET_ID)
+  mkdirSync(dir, { recursive: true })
+  const revision = modernRuntime ? `${VERSION}:ptc-runtime` : VERSION
+
+  let marker = null
+  try {
+    marker = readFileSync(join(dir, MARKER), 'utf8').trim()
+  } catch {
+    // 无标记：可能是首次安装，也可能是用户自建目录
+  }
+
+  if (marker === revision) return
+  if (marker === null && existsSync(join(dir, 'agent.cordis.yml'))) {
+    logger?.warn(`dsh-minimal-ptc: ${dir} exists without our marker; leaving it alone`)
+    return
+  }
+
+  for (const file of ['agent.cordis.yml', 'preset.yml', 'gitbash-executor.mjs']) {
+    let content = readFileSync(join(presetSourceDir, file), 'utf8')
+    if (modernRuntime && file === 'agent.cordis.yml') {
+      content = content.replaceAll('workflow-worker-thread', 'workflow-ptc')
+        .replaceAll('`codeRuntime`', '`ptcRuntime`')
+    }
+    writeFileSync(join(dir, file), content)
+  }
+  writeFileSync(join(dir, MARKER), revision + '\n')
+  logger?.info(`dsh-minimal-ptc: materialized agent preset "${PRESET_ID}" into ${dir}`)
+}
+
+export function apply(ctx) {
+  ctx.effect(() => ctx.appReady.onReady(() => {
+    try {
+      // 0.1.7 discovers the declarative row shipped by this bundle. Never
+      // rewrite a user's retired directory while running on that host.
+      if (typeof ctx.get('agentPresets')?.register !== 'function') {
+        materialize(ctx.logger, ctx.get('ptcRuntime') !== undefined)
+      }
+    } catch (error) {
+      ctx.logger?.warn(`dsh-minimal-ptc: preset materialization failed: ${String(error)}`)
+    }
+    try {
+      healthCheck(ctx)
+    } catch (error) {
+      ctx.logger?.warn(`dsh-minimal-ptc: health check failed: ${String(error)}`)
+    }
+  }))
+}
+
+/**
+ * Warn about the two known causes of "Cannot read properties of undefined
+ * (reading 'prepare')" before the first session hits them. Warnings only —
+ * nothing here blocks startup.
+ */
+function healthCheck(ctx) {
+  const logger = ctx.logger
+
+  // Cause 1 (most common in the wild): a plugin or stale install left a
+  // physical copy of @deepseek-ai/* inside some profile's node_modules. The
+  // core must come from the CLI's own dependency tree only.
+  for (const hit of findProfileCoreCopies()) {
+    logger?.warn(
+      `dsh-minimal-ptc: duplicate core package in profile: ${hit}\n`
+      + '  A second @deepseek-ai copy breaks the tool scheduler key (module-local Symbol) '
+      + 'and every tool call fails with "reading \'prepare\'".\n'
+      + '  Fix: update the plugin that brings in this runtime package, reinstall profile dependencies, '
+      + 'then restart. Shared helpers such as schemastery and cosmokit are supported dependencies.',
+    )
+  }
+
+  // Cause 2 (seen on stock 0.1.6-alpha): the host itself can load two dsh-tools
+  // instances (bundled lib/index.js vs per-module lib/types/*.js). It is safe
+  // only when the scheduler key survives multiple instances, i.e. the host was
+  // built with Symbol.for. Probe exactly that.
+  const status = schedulerKeyStatus(ctx.tools)
+  if (status === 'module-local') {
+    logger?.warn(
+      'dsh-minimal-ptc: this host keys the tool scheduler with a module-local Symbol '
+      + '(unpatched dsh-tools). PTC sessions break with "reading \'prepare\'" '
+      + 'whenever a second dsh-tools instance loads in this process.\n'
+      + '  Fix: rebuild dsh-tools with `Symbol.for(\'@deepseek-ai/dsh-tools.scheduler\')` '
+      + 'in packages/core/tools/src/index.ts, or keep a single dsh-tools copy.',
+    )
+  }
+}
+
+/**
+ * Physical @deepseek-ai copies under any profile's node_modules.
+ * @returns {string[]} paths like "<profile>/node_modules/@deepseek-ai/<pkg>"
+ */
+export function findProfileCoreCopies(home = dshHomePath('profiles')) {
+  const hits = []
+  let profiles = []
+  try {
+    profiles = readdirSync(home, { withFileTypes: true })
+  } catch {
+    return hits
+  }
+  for (const profile of profiles) {
+    if (!profile.isDirectory()) continue
+    const scopeDir = join(home, profile.name, 'node_modules', '@deepseek-ai')
+    let entries = []
+    try {
+      entries = readdirSync(scopeDir, { withFileTypes: true })
+    } catch {
+      continue
+    }
+    for (const entry of entries) {
+      // Schema helpers are ordinary published dependencies, not another host.
+      if (entry.isDirectory() && (entry.name === 'dsh-tools' || entry.name === 'cordis')) hits.push(join(scopeDir, entry.name))
+    }
+  }
+  return hits
+}
+
+/**
+ * How the host's tool registry exposes the scheduler key:
+ * - 'global'       — Symbol.for key works; safe across duplicate instances.
+ * - 'module-local' — registry carries a same-description local Symbol; the
+ *                    agent loop breaks if a second dsh-tools instance loads.
+ * - 'absent'       — no tools registry / no scheduler mounted (nothing to say).
+ */
+export function schedulerKeyStatus(tools) {
+  if (tools == null || (typeof tools !== 'object' && typeof tools !== 'function')) return 'absent'
+  if (tools[Symbol.for(SCHEDULER_SYMBOL_DESC)] !== undefined) return 'global'
+  const local = Object.getOwnPropertySymbols(tools).some(s => s.description === SCHEDULER_SYMBOL_DESC)
+  return local ? 'module-local' : 'absent'
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-minimal-ptc",
-  "version": "0.4.7",
+  "version": "0.5.1",
   "description": "DeepSeek Harness 极简 PTC 预设：简洁提示词、run_code 工具编排、完整插件工具，以及 Windows Git Bash 和持久 PowerShell。",
   "type": "module",
   "main": "lib/index.js",
@@ -9,7 +9,8 @@
       "default": "./lib/index.js"
     },
     "./cordis.patch.yml": "./cordis.patch.yml",
-    "./package.json": "./package.json"
+    "./package.json": "./package.json",
+    "./gitbash-executor": "./presets/ptc-minimal/gitbash-executor.mjs"
   },
   "files": [
     "lib",
@@ -17,11 +18,15 @@
     "cordis.patch.yml",
     "README.md",
     "README.en.md",
-    "LICENSE"
+    "LICENSE",
+    "ptc-minimal.patch.yml"
   ],
   "dsh": {
     "bundle": {
-      "patch": "./cordis.patch.yml"
+      "patch": [
+        "./cordis.patch.yml",
+        "./ptc-minimal.patch.yml"
+      ]
     }
   },
   "keywords": [

package/ptc-minimal.patch.yml

@@ -0,0 +1,307 @@
+# Harness 0.1.7 declarative preset; generated from the bundled agent composition.
+- insert:
+    - id: preset-ptc-minimal
+      name: "@deepseek-ai/dsh-agent-preset"
+      config:
+        id: ptc-minimal
+        name: 极简 PTC 模式
+        description: 简洁提示词、完整插件工具与 PTC 编排；Windows 支持 Git Bash 和持久 PowerShell。
+        order: 4
+        plugins:
+          # The `ptc-minimal` agent preset: the `ptc` (PTC 模式) capabilities with the
+          # `minimal` (极简模式) prompt.
+          #
+          # Everything in `ptc` is here unchanged — full standard capabilities plus the
+          # PTC tool presentation (`tool-presentation` with `mode: ptc`), where the
+          # model composes a TypeScript program against a generated SDK and `run_code`
+          # executes it. What differs is the persona row, taken verbatim from `minimal`:
+          # a fixed one-line persona marked `complete: true` with
+          # `includeRuntimeContext: false`, so global identity, Web orientation, tool
+          # guidance, and later assembly listeners cannot add prompt text, and runtime
+          # context snapshots are suppressed. The `agent-instructions` row from `ptc` is
+          # dropped for the same reason — its workspace instruction baselines would add
+          # user-role text the minimal prompt policy excludes.
+          #
+          # This file is an AGENT-PLANE composition. It is mounted under one agent's
+          # scope context, so every tool it registers belongs to that session alone.
+          # A service row here MUST sit inside a group carrying an `isolate` realm.
+
+          # ── identity ────────────────────────────────────────────────────────────────
+
+          # The persona is the complete system prompt (minimal-mode prompt policy).
+          # dsh 0.1.3 renamed the persona config field `text` to `prefix` (required).
+          - id: persona
+            name: '@deepseek-ai/dsh-persona'
+            config:
+              prefix: You are a helpful software engineer assistant.
+              complete: true
+              includeRuntimeContext: false
+
+          # ── shell ───────────────────────────────────────────────────────────────────
+
+          # `shell-env` stays in the HOST composition: `apps/cli/src/web.ts` injects it to
+          # publish `DSH_WEB_URL`/`DSH_WEB_MODE`. Both shell tools consume the host
+          # registry from here; their executors are host-plane too.
+          - id: tool-bash
+            name: '@deepseek-ai/dsh-tool-bash'
+            disabled: !!js process.platform === 'win32'
+
+          - id: tool-pwsh
+            name: '@deepseek-ai/dsh-tool-pwsh'
+            disabled: true
+
+          # Windows persistent PowerShell PTY stack (rc.1 minimal parity). Replaces the
+          # one-shot pwsh row on win32; the gitbash group below keeps a stateless bash
+          # tool beside it. The model-facing tool name remains `pwsh`.
+          - id: persistent-shell
+            name: cordis:group
+            group: true
+            disabled: !!js process.platform !== 'win32'
+            isolate:
+              terminals: true
+            config:
+              - id: pty
+                name: '@deepseek-ai/dsh-terminal'
+
+              - id: terminal-pwsh
+                name: '@deepseek-ai/dsh-terminal-bash'
+                disabled: !!js process.platform !== 'win32'
+                config:
+                  shellDialect: pwsh
+                  timeoutMs: 300000
+
+              - id: persistent-pwsh
+                name: '@deepseek-ai/dsh-tool-pwsh-persistent'
+                disabled: !!js process.platform !== 'win32'
+                config:
+                  timeoutMs: 300000
+                  description: |-
+                    Run commands in a PowerShell shell
+                    * When invoking this tool, the contents of the "command" parameter does NOT need to be XML-escaped.
+                    * Network access depends on the host environment.
+                    * State is persistent across command calls and discussions with the user.
+                    * Use native Windows paths (C:\...) and $env:NAME variables; this is PowerShell, not bash.
+                    * Please avoid commands that may produce a very large amount of output.
+                    * Please run long lived commands in the background, e.g. 'Start-Job' or start a server with Start-Process.
+
+          # Windows Git Bash shell stack. The preset-local executor runs every `bash`
+          # call through Git for Windows bash, keeping the model-facing tool name and
+          # stateless semantics identical to the POSIX `tool-bash` row above. Only
+          # mounted on win32; the POSIX host keeps the official bash runner.
+          - id: gitbash-shell
+            name: cordis:group
+            group: true
+            disabled: !!js process.platform !== 'win32'
+            isolate:
+              shell: true
+            config:
+              - id: gitbash-executor
+                name: dsh-minimal-ptc/gitbash-executor
+                config:
+                  # 留空：executor 自动探测 GIT_BASH → 常见安装目录 → PATH → 'bash'
+                  # 如需固定路径可显式写 shellPath: 'C:\\Program Files\\Git\\bin\\bash.exe'
+                  timeoutMs: 120000
+                  maxTimeoutMs: 600000
+                  maxOutputBytes: 64000
+                  maxSpillBytes: 67108864
+                  graceMs: 3000
+
+              - id: tool-bash-win
+                name: '@deepseek-ai/dsh-tool-bash'
+                config:
+                  enableRunInBackground: false
+
+          # ── filesystem ──────────────────────────────────────────────────────────────
+
+          # Both register into the host `tools` registry and provide nothing, so
+          # they need no realm. The `fs` service and its policy stay in the host.
+          - id: tool-fs
+            name: '@deepseek-ai/dsh-tool-fs'
+
+          - id: tool-fs-search
+            name: '@deepseek-ai/dsh-tool-fs-search'
+            config:
+              sampleOverCapGlobResults: false
+
+          # ── background jobs ────────────────────────────────────────────────────────
+
+          # Only the model-facing controls. The task REGISTRY stays on the host plane.
+          - id: tool-jobs
+            name: '@deepseek-ai/dsh-tool-jobs'
+
+          # ── skills ──────────────────────────────────────────────────────────────────
+
+          # The skill REGISTRY lives in the host composition and is layered per scope:
+          # these rows register into THIS preset's layer of it, so they need no realm.
+          - id: skill-filesystem
+            name: '@deepseek-ai/dsh-skill-filesystem'
+
+          - id: tool-skill
+            name: '@deepseek-ai/dsh-tool-skill'
+
+          # ── goals ───────────────────────────────────────────────────────────────────
+
+          # Only the model-facing tool plus the human command. The goal SERVICE, its
+          # session driver stay on the host plane.
+          - id: command-goal
+            name: '@deepseek-ai/dsh-command-goal'
+
+          - id: tool-goal
+            name: '@deepseek-ai/dsh-tool-goal'
+
+          # ── plan mode ───────────────────────────────────────────────────────────────
+
+          # Plan state is per-agent by nature, so an entry-local realm is not a
+          # workaround here — it is the correct lifetime.
+          - id: planning
+            name: cordis:group
+            group: true
+            isolate:
+              planMode: true
+            config:
+              - id: plan-mode
+                name: '@deepseek-ai/dsh-plan-mode'
+                config:
+                  section: |
+                        You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
+
+                        Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
+
+                        The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
+
+                        Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
+
+                        Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
+
+                        When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
+
+          # ── compaction ──────────────────────────────────────────────────────────────
+
+          # `compaction-basic` reads `toolResultPrune` through `ctx.get`, so the pruner
+          # must share this realm rather than sit outside it. `tokenMeter` stays HOST-side.
+          - id: compaction
+            name: cordis:group
+            group: true
+            isolate:
+              compaction: true
+              toolResultPruner: true
+            config:
+              - id: compaction-basic
+                name: '@deepseek-ai/dsh-compaction-basic'
+
+              - id: command-compact
+                name: '@deepseek-ai/dsh-command-compact'
+
+              - id: tool-result-pruner
+                name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
+                config:
+                  thresholdChars: 8192
+                  headChars: 4096
+                  tailChars: 1024
+
+          # ── delegation and workflows ────────────────────────────────────────────────
+
+          # The `subagents` registry and its spawn/fork backends live in the HOST
+          # composition. This preset contributes the delegation TOOLS. `workflows` shares
+          # one entry-local realm here, and a consumer left outside would resolve a host
+          # registry this preset does not populate.
+          - id: delegation
+            name: cordis:group
+            group: true
+            isolate:
+              workflowEngine: true
+            config:
+              - id: tool-subagent-control
+                name: '@deepseek-ai/dsh-tool-subagent-control'
+
+              - id: tool-subagent-list-agents
+                name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
+
+              - id: tool-subagent
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: spawn
+                  toolName: subagent
+                  modelSelectionSettings: true
+                  backgroundMode: continuable
+
+              - id: tool-subagent-fork
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: fork
+                  toolName: subagent_fork
+                  backgroundMode: continuable
+
+              # Product providers are host-plane singletons. Remove `disabled` from
+              # either ordinary tool row to expose that product to agents on this preset.
+              - id: tool-subagent-codex
+                name: '@deepseek-ai/dsh-tool-subagent'
+                disabled: true
+                config:
+                  provider: codex
+                  toolName: subagent_codex
+                  backgroundMode: one-shot
+                  maxDepth: provider-managed
+
+              - id: tool-subagent-claude-code
+                name: '@deepseek-ai/dsh-tool-subagent'
+                disabled: true
+                config:
+                  provider: claude-code
+                  toolName: subagent_claude_code
+                  backgroundMode: one-shot
+                  maxDepth: provider-managed
+
+              - id: workflow-ptc
+                name: '@deepseek-ai/dsh-workflow-ptc'
+                config:
+                  provider: spawn
+
+              - id: tool-workflow
+                name: '@deepseek-ai/dsh-tool-workflow'
+                # Keep the engine above for `ralph`, but do not publish a second
+                # model-authored orchestration surface beside `run_code` in PTC mode.
+                disabled: true
+
+              - id: tool-ralph
+                name: '@deepseek-ai/dsh-tool-ralph'
+                config:
+                  subagentProvider: spawn
+                  maxRounds: 64
+
+          # ── remaining model-facing rows ─────────────────────────────────────────────
+
+          - id: tool-ask-user
+            name: '@deepseek-ai/dsh-tool-ask-user'
+
+          - id: tool-todo
+            name: '@deepseek-ai/dsh-tool-todo'
+            config:
+              allowParallelInProgress: true
+
+          # The `web` service and its search provider stay in the host composition; only
+          # the model-facing tool is per-session.
+          - id: tool-web
+            name: '@deepseek-ai/dsh-tool-web'
+            config:
+              fetch: true
+              searchTimeoutMs: 60000
+
+          # ── presentation ────────────────────────────────────────────────────────────
+
+          # PTC for this agent alone. The row waits for the host's `ptcRuntime`
+          # rather than assuming it: a deployment that composes no TypeScript runtime
+          # fails this preset at mount, naming this id, instead of at the first request.
+          - id: tool-presentation
+            name: '@deepseek-ai/dsh-agent-tool-presentation'
+            config:
+              mode: ptc
+
+          # Official `ptc` parity rows (0.1.6): the deliverables presenter and the
+          # plugin-manager tools (off by default, mirroring the official preset).
+          - id: present
+            name: '@deepseek-ai/dsh-tool-present'
+
+          - id: tool-plugin-manager
+            name: '@deepseek-ai/dsh-plugin-manager/tools'
+            disabled: true