@quan-huayan/dsh-research-engine 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,38 @@
+# 更新日志
+
+本文件记录本包对外可见的变化。格式参考 [Keep a Changelog](https://keepachangelog.com/zh-CN/1.1.0/)，
+版本号遵循 [语义化版本](https://semver.org/lang/zh-CN/)。
+
+## [0.1.0] — 2026-09-08
+
+首个发布版本：research-engine preset 从「本机 `$DSH_HOME/.agent-presets/` 里的私有副本」
+变成可分发的 npm 包。
+
+### 新增
+
+- `presets/research-engine/` —— 引擎本体（唯一真源）：`preset.yml`、`agent.cordis.yml`、
+  用户面 `SKILL.md`、7 份 JSON schema + `managed.json` + `fields.md`、5 个插件模块。
+- `cordis.patch.yml` + `startup.js` —— 组合包层：把自带的 preset 根注册成 `agent-presets`
+  的 `system` 根（`dsh plugin --profile <name> add` 后新会话即可选用）。
+- `scripts/install.mjs` —— 把 preset 同步进 `$DSH_HOME/.agent-presets/` 的幂等安装器
+  （`--force` 先备份、`--dry-run` 只报告、`--dir` 换根）；覆盖 dsh 0.1.1-rc.x 等
+  组合包根不生效的版本。
+- `README.md`、`CHANGELOG.md`、`.gitignore`、`LICENSE`（MIT）。
+
+### 变更
+
+- 插件依赖解析改为多锚点回退：先按插件自身位置解析（随包安装的 `node_modules`），
+  再回退到 `$DSH_HOME/profiles/node_modules` 的扁平安装 —— 同一份代码既能作为 npm 包运行，
+  也能作为拷贝进用户 preset 根的副本运行。
+- 仓库结构：规格稿与验收报告移入 `docs/`，v6 存档移入 `archive/preset-v6/`，
+  headless 验收 overlay 移入 `overlays/`，测试工程移入 `fixtures/`（gitignore）。
+- 自检脚本默认读仓库内的 preset，可用 `RESEARCH_ENGINE_PRESET` 覆盖。
+
+### 已知问题
+
+- dsh 0.1.1-rc.x 的启动器会覆写 `agent-presets` 的 `roots`，组合包注册的自带根在该版本不生效；
+  请改用 `scripts/install.mjs`。
+- `tools/probe-*.mjs` 在 dsh 沙箱内运行时，`git-lfs` 无法创建命名管道，导致引擎提交 `raw/` 失败、
+  探针误报 8 项；在普通终端运行即全绿。
+
+[0.1.0]: https://github.com/quan-huayan/dsh-research-engine/releases/tag/v0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Quan-huayan
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,183 @@
+# @quan-huayan/dsh-research-engine · 研究引擎
+
+> 一个 DeepSeek Harness（dsh）**agent preset**：把研究工程变成「不可变证据 + 一条可重放的过程」。
+> 环境 / 台账 / 状态机 / 执行 / 知识五层由工具独占，模型只能经工具改工程，数字只能由工具从已登记文件里提取。
+
+**English** — `@quan-huayan/dsh-research-engine` ships a self-contained dsh agent preset (`research-engine`) plus a
+profile bundle layer that registers it. Inside a research project every mutation goes through a tool, every claim
+points at evidence, and user authority must quote a real answer; the engine keeps its own internal version store the
+model never sees. 21 model-facing tools + 1 internal service, 7 JSON schemas, 5 plugin modules, zero runtime deps
+beyond `js-yaml` / `ajv`.
+
+- 版本：**0.1.0**
+- 包名：`@quan-huayan/dsh-research-engine`（npm）
+- 需要：Node ≥ 22；dsh（0.1.1-rc.2 及以上均可）；`git` 必需，`git-lfs` 可选（不装则 `raw/` 降级为哈希-only）
+
+---
+
+## 1. 根本原则
+
+**任何研究结论，都必须能由不可变证据 + 一条可重放的过程重新得到。**
+
+三条推论决定引擎的每一个动作：
+
+| | 原则 | 物理落点 |
+|---|---|---|
+| P1 | **证据优先**：结论只能指向证据；数字只能由工具从已登记文件里提取 | `experiments/<runId>/{config,manifest,observations}.json` + `raw/` |
+| P2 | **封闭变更**：工程里的所有变更只能经工具发生 | 写类工具前置守卫 + 内建版本库（模型不可见） |
+| P3 | **权威分离**：用户权威 / 证据权威 / agent 提议不得互相冒充 | `conventions[]` + `decision` 事件 / `observations.json` / `.kb/notes` 的 `status` |
+
+八要素落点、22 条权责、逐工具流程见 [`docs/`](docs/README.md)。
+
+---
+
+## 2. 安装
+
+### 方式 A：组合包（推荐，dsh ≥ 0.1.2-rc.1）
+
+```sh
+dsh plugin --profile web add @quan-huayan/dsh-research-engine
+```
+
+本包声明了 `dsh.bundle.patch`，`dsh` 会把它追加进该 profile 的 `dsh.profile.bundles`；启动时
+[`cordis.patch.yml`](cordis.patch.yml) 把本包自带的 `presets/` 注册成 `agent-presets` roster 的一个
+`system` 根 —— **新建会话即可在 preset 选择器里看到「研究引擎」**，无需重启。
+
+先只看组合结果、不启动：
+
+```sh
+dsh --profile web --dump-config      # 应能看到 "# == @quan-huayan/dsh-research-engine" 这一层
+```
+
+卸载：`dsh plugin --profile web remove @quan-huayan/dsh-research-engine`（依赖与层一起移除）。
+
+> **dsh 0.1.1-rc.x 的限制**：那一版的启动器会把 `agent-presets` 的 `roots` 覆写为「仅随附根」，
+> 组合包注册的自带根不生效（`--dump-config` 里能看到，启动后没有）。请用方式 B。
+
+### 方式 B：装进用户 preset 根（全版本可用）
+
+```sh
+node node_modules/@quan-huayan/dsh-research-engine/scripts/install.mjs
+# 或从本仓库直接跑：
+node scripts/install.mjs
+```
+
+把 `presets/research-engine/` 同步到 `$DSH_HOME/.agent-presets/research-engine`。
+脚本是幂等的：目标不存在就装；内容相同就跳过；**内容不同会拒绝覆盖并提示**，确认要覆盖加 `--force`
+（先自动备份成 `research-engine.bak-<时间戳>`）。`--dry-run` 只报告将要做什么，`--dir <目录>` 换 preset 根。
+
+两种方式可以共存：组合包的 `system` 根排在用户根之前，同名 id 由组合包那份胜出。
+
+---
+
+## 3. 用它
+
+1. 在目标工作区**新建**会话，选「研究引擎」preset（切换 preset 只在空白会话可用）。
+2. 首句直接说目标，或先让它看现状：
+
+```
+project_load → project_verify          # 先看现状，别凭记忆断言工程内容
+stage_read → stage_goto                # 走到该在的阶段
+（需要新能力）script_declare → template_declare
+run_draft → run_launch → job_output    # 跑
+run_observe                            # 数字来自产出文件本身
+note_write(claim, evidence=[runId]) → note_adjudicate(accept)
+view_render(report) → view_render(notes-skill)
+```
+
+新目录接引擎：让它 `project_init`。已经存在的旧工程：`project_init mode=migrate`（原文归档、逐项迁移、
+不删任何既有文件）。
+
+### 21 个模型面工具
+
+| 域 | 工具 |
+|---|---|
+| 环境 / 台账（7） | `project_init` `project_load` `project_verify` `project_reconcile` `entity_declare` `entity_query` `convention_declare` |
+| 状态机（3） | `stage_declare` `stage_read` `stage_goto` |
+| 执行 / 证据（7） | `template_declare` `script_declare` `run_draft` `run_launch` `run_observe` `run_query` `run_close` |
+| 知识 / 裁决（4） | `note_write` `note_adjudicate` `note_query` `view_render` |
+
+内建服务 `research.engineGit` 不注册工具，模型侧看不到任何版本库概念。
+
+### 工程里的物理形态
+
+```
+project.yaml  pipeline.yaml  templates.yaml  scripts/  registry.jsonl
+experiments/<runId>/{config.json, manifest.json, observations.json, raw/}
+.kb/{notes/*.md, index.yaml}          _report/{runs.csv, summary.json}
+.research/{state.json, managed.json, engine.git/}
+skills/<工程>/SKILL.md                 ← 派生视图，由 view_render 生成
+遗留区（.pth/.png/.txt/.ipynb …）      ← 只登记，不改不删
+```
+
+---
+
+## 4. 仓库结构
+
+```
+presets/research-engine/        引擎本体（唯一真源）
+  preset.yml  agent.cordis.yml
+  skills/research-engine/SKILL.md
+  contract/                     7 份 schema + managed.json + fields.md
+  plugins/{engine-git,exp-ledger,stage-ctrl,task-dispatch,kb-core}/main.js
+cordis.patch.yml                组合包层：把 presets/ 注册成 agent-presets 的 system 根
+startup.js                      组合包的提供方行（只暴露 presetsDir 服务）
+scripts/install.mjs             把 preset 装进 $DSH_HOME/.agent-presets/
+tools/                          自检脚本（不进 npm 包）
+overlays/                       headless 验收 overlay
+docs/                           规格稿 + 六轮验收报告
+archive/preset-v6/              v6 历史存档
+fixtures/                       测试工程（gitignore，不进包）
+```
+
+---
+
+## 5. 自检
+
+```sh
+npm run check          # 契约 + 插件静态检查 + 197 项工具探针
+npm run check:preset   # 用 dsh 自己的 preset 发现器解析 agent.cordis.yml
+node tools/probe-migrate.mjs   # 迁移自检
+```
+
+| 脚本 | 覆盖 |
+|---|---|
+| `tools/check-contract.mjs` | 7 份 schema 可编译、跨文件引用无环、真实数据差距清单 |
+| `tools/check-plugins.mjs` | 5 插件可加载、21 工具名合法唯一、schema 落在 dsh-tools 支持子集内 |
+| `tools/probe-tools.mjs` | 假 ctx 逐工具跑 197 项断言（严格返回字段、返回文本零版本库词汇、拒绝路径必带修法） |
+| `tools/probe-migrate.mjs` | 旧式工程 → `project_init mode=migrate` → 核对六项产出与幂等复检 |
+| `tools/check-preset.mjs` | 宿主 preset 发现器解析合成文件（含 `!!js`） |
+
+> **探针必须在 dsh 沙箱之外跑。** 沙箱禁止创建命名管道，`git-lfs` 因此起不来
+> （`couldn't create signal pipe, Win32 error 5`），引擎提交 `raw/` 失败，探针会误报 8 项。
+> 在普通终端里跑即全绿。
+
+`RESEARCH_ENGINE_PRESET` 环境变量可让所有自检改读别的 preset 副本（例如已安装的那份）。
+
+---
+
+## 6. 已知边界
+
+- **用户权威落点为空是正常的**：约定与裁决需要真实用户答复，引擎拒绝推断、代答、润色。
+- **`job_output` 在任务结束后可能为空**：进程输出已被收进 `experiments/<runId>/raw/stdout.log`（证据）。
+- **`git-lfs` 不可用时**：`raw/` 降级为哈希-only，证据被改动即 `invalidated`。
+- **前端外观**（client 插件 + host 只读桥）未做；本期只有模型面与派生视图。
+- **preset 副本会漂移**：升级本包后，方式 B 装下的副本需要重跑 `scripts/install.mjs`（脚本会提示）。
+
+---
+
+## 7. 开发与发布（维护者）
+
+改动 `presets/research-engine/` 后：
+
+1. 递增 `agent.cordis.yml` 里 `./plugins/*/main.js?v=N` 的 N —— loader 按 URL 缓存 ESM，同进程内改代码只有 URL 变了才重新求值。
+2. 跑 §5 的自检。
+3. 更新 `CHANGELOG.md` 与 `package.json` 的 `version`。
+4. 发布：`npm publish`（`publishConfig.access=public`）。
+   预览包内容：`npm pack --dry-run`。
+
+---
+
+## 8. 许可
+
+[MIT](LICENSE) © 2026 Quan-huayan

package/cordis.patch.yml

@@ -0,0 +1,32 @@
+# @quan-huayan/dsh-research-engine 的组合包层（bundle patch）。
+#
+# 安装后 `dsh plugin --profile web add @quan-huayan/dsh-research-engine` 会把本行加入
+# profile 的 dsh.profile.bundles，本层在启动时按下面的顺序生效：
+#
+#   1) insert：把本包的提供方行挂进 profile（它只暴露 presetsDir 这个服务）；
+#   2) id 定向补丁：让 agent-presets 注入该服务，并把本包自带的 presets/ 注册成
+#      一个 system 根 —— 新会话即可在 preset 选择器里看到「研究引擎」。
+#
+# 两点说明：
+#   * 行名用包名（Node 从 profile 的 node_modules 解析到已安装代码），不用相对路径；
+#   * 路径走 !!js 求值，取的是本包自己的绝对路径，与 cwd / baseUrl 无关。
+#   * 补丁按 id 整体替换 config：如果你的 profile 自己也配置了 agent-presets 的 config，
+#     你的层在本层之后应用，会整体覆盖 —— 那时请把下面的 roots 一并重述。
+#
+# 兼容性：DSH >= 0.1.2-rc.1 时 agent-presets 的 roots 由本层决定；
+# DSH 0.1.1-rc.x 的启动器会把 roots 覆写为「仅随附根」，本层不生效 ——
+# 那种版本请改用 `node node_modules/@quan-huayan/dsh-research-engine/scripts/install.mjs`
+# 把 preset 装进 $DSH_HOME/.agent-presets/（用户根）。
+
+- insert:
+    - id: research-engine-bundle
+      name: '@quan-huayan/dsh-research-engine/startup'
+
+- id: agent-presets
+  inject: [researchEngineBundle]
+  config:
+    default: standard
+    includeUserRoot: true
+    roots:
+      - path: !!js ctx.researchEngineBundle.presetsDir
+        trust: system

package/package.json

@@ -0,0 +1,59 @@
+{
+  "name": "@quan-huayan/dsh-research-engine",
+  "version": "0.1.0",
+  "license": "MIT",
+  "author": "Quan-huayan",
+  "description": "研究引擎（research-engine）：把研究工程变成「不可变证据 + 可重放过程」的 DeepSeek Harness agent preset —— 环境/台账/状态机/执行/知识五层由工具独占，21 个模型面工具 + 1 个内建版本库服务。",
+  "type": "module",
+  "main": "startup.js",
+  "exports": {
+    ".": "./startup.js",
+    "./startup": "./startup.js",
+    "./package.json": "./package.json",
+    "./presets/*": "./presets/*"
+  },
+  "files": [
+    "startup.js",
+    "cordis.patch.yml",
+    "presets",
+    "scripts/install.mjs",
+    "README.md",
+    "CHANGELOG.md"
+  ],
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    }
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/quan-huayan/dsh-research-engine.git"
+  },
+  "homepage": "https://github.com/quan-huayan/dsh-research-engine#readme",
+  "bugs": {
+    "url": "https://github.com/quan-huayan/dsh-research-engine/issues"
+  },
+  "keywords": [
+    "dsh",
+    "deepseek-harness",
+    "agent-preset",
+    "research-engine",
+    "reproducible-research",
+    "provenance"
+  ],
+  "engines": {
+    "node": ">=22"
+  },
+  "dependencies": {
+    "ajv": "^8.20.0",
+    "js-yaml": "^4.3.1"
+  },
+  "scripts": {
+    "check": "node tools/check-contract.mjs && node tools/check-plugins.mjs && node tools/probe-tools.mjs",
+    "check:preset": "node tools/check-preset.mjs",
+    "install-preset": "node scripts/install.mjs"
+  }
+}

package/presets/research-engine/agent.cordis.yml

@@ -0,0 +1,305 @@
+# The `standard` agent preset: the full coding agent, mounted once per process.
+#
+# This file is an AGENT-PLANE composition. The roster mounts it ONCE under a
+# standing scope; every session naming it joins by scope parentage, so the
+# tools and prompt sections registered here cover each joined agent while a
+# session's own state stays keyed per Session/Agent inside the plugins. The
+# host composition (`base.cordis.yml` + `web.cordis.yml`) keeps everything a
+# preset must not own: the registries themselves, the sandbox and approval
+# stack, persistence, and the model route.
+#
+# A service row here MUST sit inside a group carrying an `isolate` realm.
+# Without one it publishes into the root realm, where it is process-global —
+# another preset publishing the same name collides, and a host reader would
+# resolve one preset's instance for every session; `dsh-agent-presets` rejects
+# that at mount. `true` means an entry-local realm: this standing mount's own
+# private instance, apart from every other preset's. (A shared label does NOT
+# pool instances — `provide()` throws on the second registration under the
+# same realm symbol; labels join REALMS, and are not what this file needs.)
+
+# ── identity ────────────────────────────────────────────────────────────────
+
+# The preset's own persona, shadowing the deployment default for this agent.
+# `{{model}}` and `{{cwd}}` resolve from the agent's own route and workspace.
+- id: persona
+  name: '@deepseek-ai/dsh-persona'
+  config:
+    text: >-
+      You are a research-engine agent powered by the {{model}} model, running on the
+      DeepSeek Harness. Your working directory is {{cwd}}.
+
+      你在「研究引擎」preset 下工作。研究工程的物理形态：project.yaml（身份/受管区/约定）、
+      pipeline.yaml（阶段机）、templates.yaml（可执行声明）、registry.jsonl（台账）、
+      experiments/<runId>/（证据）、.kb/notes（提议与结论）、_report 与 skills/<工程>/SKILL.md（派生视图）。
+
+      铁律：工程里的任何变更都只能经工具发生。结论只能指向证据；数字只能由工具从已登记文件里提取。
+      用户权威必须来自一次真实提问与用户答复原文，不得推断、润色、代答。
+
+      开工先加载 skill: research-engine，按里面的路由表工作。默认入口：
+      project_load → project_verify → stage_read → run_query → note_query。
+      动手前先看清现状，不要凭记忆断言工程内容。
+
+- id: agent-instructions
+  name: '@deepseek-ai/dsh-agent-instructions'
+  config:
+    maxBytes: 65536
+
+# ── shell ───────────────────────────────────────────────────────────────────
+
+# `shell-env` stays in the HOST composition: `apps/cli/src/web.ts` injects it to
+# publish `DSH_WEB_URL`/`DSH_WEB_MODE`, and a host row that injects a service is
+# the criterion for host-plane ownership — injection resolves before any session
+# exists, so there is no agent to key by. Behind a preset realm those variables
+# never reached the model's shell at all. Both shell tools consume the host
+# registry from here; their executors (`bash-sandbox`/`pwsh-sandbox`) 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: !!js process.platform !== 'win32'
+
+# ── 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:
+# its producers sit outside any realm this file could put it in — `tool-bash`
+# above resolves it with `ctx.get`, and an entry-local realm here is invisible
+# to every sibling row, so `run_in_background` would answer "background jobs
+# unavailable" while these controls sat in the catalog. The registry is keyed by
+# owning agent anyway, so one host instance serves every session. What a preset
+# chooses is whether its agent can collect and stop background work at all.
+- 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.
+# `skill-filesystem` contributes local-root discovery for agents on this preset, and
+# `tool-skill` gives them the catalog and loader; the merged catalog also
+# carries whatever the deployment registered globally (repository plugins).
+# research-engine: customSkillDirs 指向 preset 自带的 skills/（baseUrl = 本 preset 目录）
+# ——SKILL.md 随 preset 目录走，新会话免重启即可见。
+- id: skill-filesystem
+  name: '@deepseek-ai/dsh-skill-filesystem'
+  config:
+    customSkillDirs:
+      - !!js "process.getBuiltinModule('node:url').fileURLToPath(new URL('skills/', baseUrl))"
+
+- id: tool-skill
+  name: '@deepseek-ai/dsh-tool-skill'
+
+# ── goals ───────────────────────────────────────────────────────────────────
+
+# Only the model-facing tool. The goal SERVICE, its session driver, and the
+# `/goal` command stay on the host plane: the Gateway serves the goal domain as
+# Remote endpoints whose receiver comes from a generated descriptor, so it
+# resolves `goals` on the host and an entry-local realm here would hide it. The
+# registry is keyed by session anyway, so one host instance serves every
+# session. What a preset chooses is whether its agent can call the goal tool.
+- 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` is deliberately NOT in this realm: the meter stays on the HOST
+# plane, and the rows here resolve that one instance. It takes no configuration,
+# keys every fold by Session, and owns the context-meter projection units the
+# browser reads for every session — behind a realm those units would come and go
+# with whichever presets happen to be mounted. What a preset chooses is whether
+# its agent compacts at all, which is `compaction-basic` below.
+- 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: the registry is a process singleton whose cross-session queries
+# the api-proxy serves to the browser, and a provider name may only be
+# registered once. This preset contributes the delegation TOOLS, which resolve
+# that host registry.
+#
+# `workflows` is different — nothing outside an agent reads it — so every row
+# that reaches it shares one entry-local realm here, and a consumer left
+# outside would resolve a host registry this preset does not populate.
+#
+# `tool-subagent-report` is host-plane for the same reason as the registry,
+# not because a preset may not want it: it registers a CONTINUABLE SETUP on
+# that singleton rather than a tool this agent calls, and the setup list is
+# not scope-aware — one copy per mounted preset means every child gets
+# `report` registered once per live session, which throws on the second.
+- 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
+        backgroundMode: continuable
+
+    - id: tool-subagent-fork
+      name: '@deepseek-ai/dsh-tool-subagent'
+      config:
+        provider: fork
+        toolName: subagent_fork
+        backgroundMode: continuable
+
+    # Production dsh does not install these optional providers. Install the
+    # matching Bundle in this Profile and restart the Host, then copy this
+    # preset and remove `disabled` from the matching tool row. Host availability
+    # alone grants no tool.
+    - 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-worker-thread
+      name: '@deepseek-ai/dsh-workflow-worker-thread'
+      config:
+        provider: spawn
+
+    - id: tool-workflow
+      name: '@deepseek-ai/dsh-tool-workflow'
+
+    - 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: false
+    searchTimeoutMs: 60000
+
+# ── research-engine：内建版本库 + 四插件（同一 group，共享一个 entry-local isolate realm）──
+#
+# 行 name 用相对路径（从 preset 自身目录解析）——插件随 preset 目录走，免安装、免重启。
+# 插件源码只用 node:* 内建 + createRequire 锚定 $DSH_HOME/profiles/node_modules（取 js-yaml/ajv），
+# 不 import 兄弟插件文件；跨域调用只走 ctx.get('research.*') 服务。
+#
+# 行名带 `?v=N` 缓存版本：loader 以 `import(new URL(name, baseUrl))` 加载本地文件，Node 按 URL
+# 缓存 ESM 模块——同进程内改写插件后只有 URL 变化才会重新求值。改插件内容时递增 v。
+#
+# isolate 的键 = 本组 provide 的服务名：五个 research.* 服务 → entry-local realm，
+# 绝不漏出 realm（漏出 = 挂载被拒 published process-global service(s)）。
+- id: research-engine
+  name: cordis:group
+  group: true
+  isolate:
+    research.engineGit: true
+    research.expLedger: true
+    research.stageCtrl: true
+    research.taskDispatch: true
+    research.kbCore: true
+  config:
+    - id: engine-git
+      name: './plugins/engine-git/main.js?v=8'
+
+    - id: exp-ledger
+      name: './plugins/exp-ledger/main.js?v=8'
+
+    - id: stage-ctrl
+      name: './plugins/stage-ctrl/main.js?v=8'
+
+    - id: task-dispatch
+      name: './plugins/task-dispatch/main.js?v=8'
+
+    - id: kb-core
+      name: './plugins/kb-core/main.js?v=8'