dsh-plugin-prompt-tool 0.1.2 → 0.1.3

package/package.json

@@ -1,88 +1,96 @@
-{
-  "name": "dsh-plugin-prompt-tool",
-  "version": "0.1.2",
-  "description": "DSH 插件：提示词工具，规范模型的思维链与回答内容，提供 Web UI 编辑 preset.md 与 AGENTS.md，并按 skills 目录注册可开关技能。",
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/Czerror/dsh-plugin-prompt-tool.git"
-  },
-  "type": "module",
-  "main": "lib/index.mjs",
-  "types": "lib/index.d.mts",
-  "exports": {
-    ".": {
-      "types": "./lib/index.d.mts",
-      "default": "./lib/index.mjs"
-    },
-    "./client": "./lib/client.js",
-    "./package.json": "./package.json"
-  },
-  "engines": {
-    "node": ">=20"
-  },
-  "dsh": {
-    "bundle": {
-      "patch": "./cordis.patch.yml"
-    },
-    "client": {
-      "inject": [
-        "@deepseek-ai/dsh-client-connection",
-        "@deepseek-ai/dsh-client-ui-settings-plugins"
-      ],
-      "platform": "web"
-    }
-  },
-  "peerDependencies": {
-    "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-api-remotes": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-client-connection": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-client-runtime": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-client-ui-primitives": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-client-ui-settings-plugins": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-settings": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-system-prompt": "^0.1.0-rc.6",
-    "@deepseek-ai/schemastery": "^3.18.1",
-    "react": "^18.2.0"
-  },
-  "devDependencies": {
-    "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-api-remotes": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-client-runtime": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-client-ui-primitives": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-client-ui-settings": "^0.1.0-rc.6",
-    "@deepseek-ai/dsh-settings": "^0.1.0-rc.6",
-    "@types/node": "^26.2.0",
-    "@types/react": "~18.3.1",
-    "clsx": "^2.1.1",
-    "lightningcss": "^1.32.0",
-    "oxlint": "^1.78.0",
-    "react": "^18.3.1",
-    "tsdown": "^0.22.2",
-    "typescript": "^5.9.2"
-  },
-  "files": [
-    "lib",
-    "cordis.patch.yml",
-    "LICENSE",
-    "preset",
-    "vendor/dsh-anchored-standard/preset",
-    "vendor/dsh-anchored-standard/LICENSE",
-    "vendor/dsh-anchored-standard/NOTICE",
-    "skills",
-    "preset.md",
-    "AGENTS.md",
-    "plan.md",
-    "README.md"
-  ],
-  "scripts": {
-    "build": "tsdown",
-    "prepare": "tsdown",
-    "typecheck": "tsc -p tsconfig.json --noEmit && tsc -p tsconfig.client.json --noEmit",
-    "lint": "oxlint src test tsdown.config.ts",
-    "test": "pnpm build && node --test \"test/*.test.mjs\""
-  },
-  "dependencies": {
-    "yaml": "^2.9.0"
-  }
-}
+{
+  "name": "dsh-plugin-prompt-tool",
+  "version": "0.1.3",
+  "description": "DSH 插件：提示词工具，规范模型的思维链与回答内容，提供 Web UI 编辑 preset.md 与 AGENTS.md，并按 skills 目录注册可开关技能。",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Czerror/dsh-plugin-prompt-tool.git"
+  },
+  "type": "module",
+  "main": "lib/index.mjs",
+  "types": "lib/index.d.mts",
+  "exports": {
+    ".": {
+      "types": "./lib/index.d.mts",
+      "default": "./lib/index.mjs"
+    },
+    "./client": "./lib/client.js",
+    "./package.json": "./package.json"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    },
+    "client": {
+      "inject": [
+        "@deepseek-ai/dsh-client-runtime",
+        "@deepseek-ai/dsh-client-connection",
+        "@deepseek-ai/dsh-client-ui-settings-plugins"
+      ],
+      "platform": "web"
+    }
+  },
+  "peerDependencies": {
+    "@deepseek-ai/cordis": "^4.0.1",
+    "@deepseek-ai/dsh-api-remotes": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-client-connection": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-client-runtime": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-client-ui-primitives": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-client-ui-settings-plugins": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-host-webserver": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-settings": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-skill": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-system-prompt": "^0.1.0-rc.6",
+    "@deepseek-ai/schemastery": "^3.18.1",
+    "react": "^18.2.0",
+    "@deepseek-ai/dsh-commands": "^0.1.0-rc.6"
+  },
+  "devDependencies": {
+    "@deepseek-ai/cordis": "^4.0.1",
+    "@deepseek-ai/dsh-api-remotes": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-client-runtime": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-client-ui-primitives": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-client-ui-settings": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-client-ui-slots": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-commands": "0.1.0-rc.6",
+    "@deepseek-ai/dsh-host-webserver": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-settings": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-skill": "^0.1.0-rc.6",
+    "@types/node": "^26.2.0",
+    "@types/react": "~18.3.1",
+    "clsx": "^2.1.1",
+    "lightningcss": "^1.32.0",
+    "oxlint": "^1.78.0",
+    "react": "^18.3.1",
+    "tsdown": "^0.22.2",
+    "typescript": "^5.9.2"
+  },
+  "files": [
+    "lib",
+    "cordis.patch.yml",
+    "LICENSE",
+    "preset",
+    "vendor/dsh-anchored-standard/preset",
+    "vendor/dsh-anchored-standard/LICENSE",
+    "vendor/dsh-anchored-standard/NOTICE",
+    "skills",
+    "preset.md",
+    "AGENTS.md",
+    "plan.md",
+    "README.md"
+  ],
+  "scripts": {
+    "build": "tsdown",
+    "prepare": "tsdown",
+    "typecheck": "tsc -p tsconfig.json --noEmit && tsc -p tsconfig.client.json --noEmit",
+    "lint": "oxlint src test tsdown.config.ts",
+    "test": "pnpm build && node --test \"test/*.test.mjs\""
+  },
+  "dependencies": {
+    "yaml": "^2.9.0"
+  }
+}

package/preset/prompt-injector.mjs

@@ -6,6 +6,11 @@
  *   turn1 reasoning 以 "we" 开头 → 下一轮注入 promptText 一次；
  *   we 未确认 → 最多再等一轮，仍无则强制注入（兜底，绝不卡死）。
  *
+ * promptText 由宿主在生成 preset 时准备好：
+ *   - 默认等于 preset.md 原文；
+ *   - 开启 injectAgentsPrompt 时，宿主会把 AGENTS.md 拼接到 preset.md 头部。
+ *   本模块只负责把最终文本作为一条 user 消息注入，不做路径探测。
+ *
  * 实测依据：
  *   - 复杂任务 + 原版 2 工具 + maxTokens 1024 → turn1 reasoning "We need"；
  *   - 简单任务模型直接调工具干活（无 we 首词），走兜底注入；
@@ -119,4 +124,4 @@ export function apply(ctx, config) {
     }
     return { ...decision, messages: [message, ...decision.messages] }
   })
-}
+}

package/preset.md

@@ -1,5 +1,5 @@
 You are a helpful software assistant.
-Begin every reasoning block with 'We need'.
+Begin every reasoning block or thinking with "'We need', '我需要'".
 DeepSeek harness operates in local execution mode. Answer requests directly in the
 user's language. No preamble, qualification, or redirection.
 

package/vendor/dsh-anchored-standard/README.md

@@ -2,15 +2,85 @@
 
 [中文说明](./README.zh-CN.md)
 
-An experimental DeepSeek Harness agent preset that bootstraps the first model
-request with a Minimal-aligned prompt, the Minimal preset's real tool schema
-(`bash` + `str_replace_editor`), and no auto-injected workspace/skill context,
-then exposes the complete Standard tool catalog after the first durable tool
-call or reply.
+Experimental DeepSeek Harness agent presets — one base mode plus two variants
+— that anchor a session's first model request on the Minimal condition
+(real Minimal tool schema, no auto-injected context), then promote to a small
+resident catalog once the session is durable, unlocking heavier Standard tools
+on demand.
 
 This is a community project. It is not an official DeepSeek preset and is not
 affiliated with or endorsed by DeepSeek.
 
+Welcome to submit feedback on the plugin in the form of Issues or PRs. For ideas for new plugins or useful findings, please submit them under the [repository](https://github.com/0liveiraaa/DeepseekCotexplorations).
+
+## Modes at a glance
+
+| Mode | Directory | First model request | Anchor mechanism | Promotion signal | Cost |
+|---|---|---|---|---|---|
+| Anchored Standard | `preset/` | 2 tools (the Minimal pair) | Minimal tool schema | first durable `tool/call` **or** `assistant/message` (`promoteOn: either`) | none |
+| Zero-Anchored Standard | `zero-anchored-standard/` | 0 tools | one fixed anchor turn | the anchor reply (`assistant/message`) | +1 model call |
+| Whoami Standard | `whoami-standard/` | 0 tools | one "你是谁" self-introduction turn | the self-introduction reply (`assistant/message`) | +1 model call |
+
+Every mode directory is self-contained and installs alone under whatever id
+you copy it to (see [Install](#install)).
+
+## Terminology
+
+- **trajectory** — the style of the model's first reasoning chain. The
+  Minimal condition produces "We need…" first lines; the Standard condition
+  produces "Let me…" ("standard-like") first lines.
+- **anchor** — the first-request conditions that select the trajectory. Issue
+  #11 isolated three levers: the tool schema, the output budget, and the
+  injected reminders.
+- **bootstrap phase** — request #1 of a session: the bootstrap tool pair, no
+  auto-injected context, optional output cap.
+- **promotion** — the durable session event that ends the bootstrap phase.
+  Base mode: first `tool/call` or `assistant/message`, whichever comes first.
+  Variants: the anchor reply.
+- **durable** — recorded in the session event log. Phase state is derived
+  from durable events, so resume and reload preserve it.
+- **resident catalog** — the promoted tool set: the bootstrap pair plus the
+  discovery tools plus every tool the model explicitly unlocked.
+- **discovery tools** — `dev_tool_search`, `skill_search`, `skill_load`: the
+  on-demand unlock surface for heavier Standard tools.
+- **materialized copy** — the committed copy of a `shared/` plugin inside a
+  mode directory, generated by `npm run sync`.
+
+## How it works
+
+The base mode in one request lifecycle (the variants change only the first
+turn — see their sections):
+
+```
+user's first message
+        │
+        ▼
+┌ request #1 ─ bootstrap phase ──────────────────────────────┐
+│ tools    : bash + str_replace_editor (Minimal's real pair) │
+│ context  : no AGENTS.md digest, no skill-catalog reminder  │
+│ budget   : adapter default (`bootstrapMaxTokens` optional) │
+└─────────────────────────────────────────────────────────────┘
+        │ first durable tool/call OR assistant/message
+        ▼ PROMOTION — derived from durable events, resume-safe
+┌ request #2+ ─ resident phase ──────────────────────────────┐
+│ tools    : bootstrap pair + discovery tools + unlocked     │
+│ context  : standard injections restored                    │
+│ budget   : adapter default (a cap is stripped on promote)  │
+└─────────────────────────────────────────────────────────────┘
+```
+
+Three first-request levers decide the trajectory (issue #11):
+
+1. **Tool schema** — the decisive variable at the adapter-default maxTokens
+   (256000). The real Minimal pair anchored 5/5; every standard-family schema
+   fell standard-like 11/11.
+2. **Output budget** — a 1024 first-request cap also anchored the trajectory
+   (26/32), independent of the tool descriptions. The base mode leaves this
+   lever unset (`bootstrapMaxTokens` is opt-in).
+3. **Injected reminders** — the AGENTS.md/CLAUDE.md digest and the
+   available-skills reminder. With the skill catalog present the anchor did
+   not reproduce at all (0/9); both are stripped during bootstrap.
+
 ## Why
 
 DeepSeek V4 Pro conditions strongly on the API-visible tool catalog. In the
@@ -23,23 +93,23 @@ Anchored Standard separates initial trajectory selection from later tool use:
 1. Keep the Minimal complete system prompt.
 2. Expose the Minimal preset's REAL tool schemas — persistent `bash` +
    `str_replace_editor`, byte-identical to the official Minimal composition —
-   on the first model request. Issue #11 measured this exact schema anchoring
-   5/5 runs at the adapter-default maxTokens (256000) with zero `let me`
-   first-lines, while every standard-family schema (pwsh/read, pwsh only,
-   sandboxed bash/read) fell into standard-like behavior 11/11. The tool
-   schema identity is the decisive first-request variable at 256000, so no
-   output cap is needed.
+   on the first model request (lever 1 above).
 3. Strip the auto-injected context on that first request as well — the
    AGENTS.md/CLAUDE.md workspace digest and the available-skills reminder that
    true Minimal never mounts (`suppressedContextSources` in the
-   `tool-bootstrap` row). User-initiated skill gestures are not filtered, and
-   both injections return unchanged from request #2 on.
+   `tool-bootstrap` row; lever 3). User-initiated skill gestures are not
+   filtered, and both injections return unchanged from request #2 on.
 4. After the session records its first durable promotion signal — a `tool/call`
-   or the first `assistant/message`, whichever comes first — expose all
-   Standard tools. Request #1 always sees the bootstrap catalog; request #2
-   always sees the full catalog, so a text-only first reply can no longer trap
-   the session in bootstrap. (`promoteOn` in the `tool-bootstrap` row selects
-   the trigger: `either` default, `tool-call`, or `assistant-message`.)
+   or the first `assistant/message`, whichever comes first — promote to the
+   RESIDENT catalog: the bootstrap pair plus the discovery tools plus whatever
+   the model has explicitly unlocked via `dev_tool_search`. Dumping the full
+   Standard catalog at promotion pulled the trajectory back to standard-like
+   behavior (the post-promotion regression), so heavier tools — `web_search`,
+   `subagent`, `workflow`, … — stay one `dev_tool_search` call away. Request
+   #1 always sees the bootstrap catalog; request #2 always sees the resident
+   catalog, so a text-only first reply can no longer trap the session in
+   bootstrap. (`promoteOn` in the `tool-bootstrap` row selects the trigger:
+   `either` default, `tool-call`, or `assistant-message`.)
 5. Derive the phase from durable session events so resume and reload preserve it.
 
 The bootstrap catalog is the same on every platform: the Minimal pair
@@ -59,9 +129,10 @@ Project2 V4.1b, DeepSeek V4 Pro, `reasoningEffort=max`, Windows native:
 | r2 | 99 | 162 | 165 | 98 | 0 | 1 |
 
 Both runs emitted exactly two tool-catalog snapshots: the two-tool Minimal
-bootstrap, followed by the 25-tool Standard catalog. The result is reproducible
-evidence for this task, not a claim of universal improvement across models or
-workloads.
+bootstrap, followed by the 25-tool Standard catalog (these runs predate the
+post-promotion narrowing to the resident set — see [How it works](#how-it-works)).
+The result is reproducible evidence for this task, not a claim of universal
+improvement across models or workloads.
 
 Cross-version evidence (issue #11, Windows + official endpoint, first-request
 trajectory only): at the adapter-default maxTokens the Minimal tool schema
@@ -73,6 +144,65 @@ first-request variable at 256000.
 Full methodology and aggregate evidence are in
 [`xiaobright/modeltest`](https://github.com/xiaobright/modeltest).
 
+## Configuration reference
+
+All knobs are rows in each mode's `agent.cordis.yml`. Unknown keys fail at
+preset mount.
+
+`tool-bootstrap` (in `preset/agent.cordis.yml`; the row must stay FIRST —
+waterfall registration order decides the first-request strip):
+
+| Key | Default | Meaning |
+|---|---|---|
+| `bootstrapTools` | `[bash, str_replace_editor]` | Tools visible on request #1. |
+| `promoteOn` | `either` | Promotion trigger: `either`, `tool-call`, or `assistant-message`. |
+| `bootstrapMaxTokens` | unset | Optional output cap for request #1; stripped after promotion. |
+| `suppressedContextSources` | `[agent-instructions, skill-catalog]` | `source.kind` values stripped during bootstrap; `[]` disables the filter. |
+| `compactionTools` | `[]` | Extra tools available between a compaction boundary and re-promotion. |
+
+`zero-tool-bootstrap` (in `zero-anchored-standard/` and `whoami-standard/`):
+`suppressedContextSources` and `compactionTools` have the same semantics
+(promotion is always the first `assistant/message`), plus
+`includeSubagents` — whether subagents also take the anchor phase (set `true`
+in `whoami-standard`, `false` in `zero-anchored-standard`).
+
+`anchor-turn` (in both variants): `text` — the synthetic first user message
+(default "This round is a test. Tools are not open yet; all tools will open
+next round." in zero-anchored, "你是谁" in whoami); `includeSubagents` —
+whether subagents also take the anchor turn.
+
+`instruction-hint` (all modes): `promoteOn` matching the mode's promotion
+semantics (`either` in the base mode, `assistant-message` in the variants) —
+the one-shot "instruction files exist, read them before acting" hint waits
+for promotion.
+
+## Repository layout
+
+```
+preset/                  Anchored Standard — the base mode
+zero-anchored-standard/  variant: fixed zero-tool anchor turn
+whoami-standard/         variant: "你是谁" anchor turn, subagents inherit
+shared/                  single source of truth for plugins used by 2+ modes
+scripts/sync-modes.mjs   materializes shared/ plugins into every mode dir
+test/                    zero-dependency test suite (npm test)
+verify/                  one-shot headless verification runner
+```
+
+Invariants, enforced by `npm run check`:
+
+- Every mode directory is self-contained: installable by copying it alone;
+  `agent.cordis.yml` rows may reference only `./local.mjs` files, never `../`.
+- Plugins shared by several modes live once in `shared/`; the copies in mode
+  directories are generated. Edit `shared/`, run `npm run sync`, commit both —
+  never edit a materialized copy.
+- The `tool-bootstrap` row stays the FIRST row of `preset/agent.cordis.yml`.
+
+This repository deliberately ships no AGENTS.md/CLAUDE.md: the presets' whole
+mechanism is a clean request #1, stripping exactly those instruction-file
+digests from it (issue #6: 0/9 anchored with the injection present). Shipping
+one would only feed later rounds and contradict the mechanism being
+documented. Everything an assistant needs is in this README.
+
 ## Compatibility
 
 Developed and tested against:
@@ -98,7 +228,10 @@ so review upstream changes before using it with a newer release.
 ## Install
 
 Clone this repository, then copy the entire `preset` directory into the user
-preset root under the id `anchored-standard`.
+preset root under the id `anchored-standard`. Every mode directory in this
+repository is self-contained: the `zero-anchored-standard/` and
+`whoami-standard/` variants install the same way, alone or together, with no
+other directory required (see their sections below).
 
 PowerShell:
 
@@ -139,9 +272,12 @@ variables that decide the anchor):
   no available-skills reminder — only the user message and the minimal persona
   system prompt;
 - after the first tool call or the first assistant reply, the next changed
-  header should contain the full Standard catalog;
-- subsequent requests should keep that full catalog and restore the standard
-  context injections.
+  header should contain the promoted resident catalog: the bootstrap pair plus
+  `dev_tool_search`/`skill_search`/`skill_load` plus any tools the model
+  already unlocked;
+- subsequent requests should keep that resident set (it grows only through
+  explicit `dev_tool_search` unlocks) and restore the standard context
+  injections.
 
 Run the local zero-dependency tests with:
 
@@ -153,10 +289,10 @@ npm test
 
 - With the default `promoteOn: either`, the session promotes after its first
   durable `tool/call` OR its first `assistant/message`, whichever comes first —
-  request #1 sees the bootstrap catalog and every later request sees the full
-  catalog. A text-only first reply therefore still promotes at request #2;
-  set `promoteOn: tool-call` to restore the original behavior, where a first
-  response that makes no tool call never promotes.
+  request #1 sees the bootstrap catalog and every later request sees the
+  resident catalog. A text-only first reply therefore still promotes at
+  request #2; set `promoteOn: tool-call` to restore the original behavior,
+  where a first response that makes no tool call never promotes.
 - A failed tool execution still promotes the session because the durable
   `tool/call` already exists.
 - The first request's output budget is NOT capped by default: the Minimal tool
@@ -164,12 +300,12 @@ npm test
   opt-in. When set, the first request is capped and the cap is explicitly
   stripped after promotion (the next request's seed proposal carries the
   previous header's maxTokens forward).
-- The Minimal pair stays mounted after promotion, so the promoted catalog is
-  the Standard catalog plus `bash` (persistent) and `str_replace_editor` —
-  and the Standard sandboxed `bash` row is disabled in favor of the persistent
-  shell (same tool name, same layer; see Why). The `read`/`write`/`edit` tools
-  keep the sandboxed filesystem while `str_replace_editor` uses the preset's
-  local fs.
+- The promoted catalog is the RESIDENT set — the bootstrap pair plus the
+  discovery tools plus everything the model unlocked via `dev_tool_search` —
+  not the full Standard dump. The Standard sandboxed `bash` row stays disabled
+  in favor of the persistent shell (same tool name, same layer; see Why). When
+  unlocked, the `read`/`write`/`edit` tools keep the sandboxed filesystem while
+  `str_replace_editor` uses the preset's local fs.
 - A missing bootstrap tool degrades to the full catalog with a one-time
   warning instead of failing requests, so a composition drift cannot brick a
   session; invalid `promoteOn` values fail at preset mount instead.
@@ -181,8 +317,8 @@ npm test
   Standard adds over Minimal). Set the list to `[]` to disable the context
   filter; add other `source.kind` values to suppress more. A filter failure
   degrades to keeping every message rather than eating context.
-- The tool catalog changes once, so request-prefix cache continuity also changes
-  once between the first and second model requests.
+- The tool catalog changes at promotion and again whenever `dev_tool_search`
+  unlocks a new tool; request-prefix cache continuity breaks at those points.
 - The preset has the same trust level as shell access. Review its files before
   installation.
 - The plugin performs no network requests and adds no telemetry.
@@ -198,11 +334,12 @@ on the first request it injects one fixed zero-tool anchor turn:
    tools will open next round." — ahead of it.
 2. The first real model request carries ZERO tools, so the session's first
    reasoning chain follows the zero-injection "we" trajectory.
-3. Once that anchor response is durable, the full Standard catalog is exposed
-   and the real message proceeds with all tools.
+3. Once that anchor response is durable, the resident catalog is exposed
+   and the real message proceeds with it.
 
 Anchoring on the first message — not on session creation — keeps the
-blank-session preset switcher usable. Subagents always see the full catalog.
+blank-session preset switcher usable. Subagents always see the resident
+catalog.
 
 Measured behavior (opencode-go, DeepSeek V4 Pro, `reasoningEffort=max`): the
 anchor request is stable "we"-style with zero `let me`; the following
@@ -230,7 +367,7 @@ user's real first message is deferred to the next turn. Whatever the user types
 first, the session warms up exactly one round and everything is ready when the
 real message is processed:
 
-1. When the user sends their first message, the `whoami-turn` plugin prepends a
+1. When the user sends their first message, the `anchor-turn` plugin prepends a
    fixed user message — "你是谁" (who are you) — ahead of it in the `next-turn`
    inbox queue.
 2. dsh claims exactly ONE `next-turn` message per turn, so the first model
@@ -240,15 +377,35 @@ real message is processed:
    catalog (shells, `str_replace_editor`, the discovery tools) already
    unlocked — heavier Standard tools are one `dev_tool_search` away.
 
-The anchor text is configurable via the `whoami-turn` row's `text` option
+The anchor text is configurable via the `anchor-turn` row's `text` option
 (default "你是谁"). Anchoring on the first message — not session creation —
-keeps the blank-session preset switcher usable; subagents always see the full
-catalog. The trade-off is one extra model call per session: the anchor turn is
-always taken, even when the first message is urgent.
+keeps the blank-session preset switcher usable.
+
+### Full-powered subagents
+
+Whoami Standard ships with `includeSubagents: true` on both the
+`zero-tool-bootstrap` and `anchor-turn` rows, so subagents spawned from a
+session inherit the same anchor flow as top-level sessions:
+
+1. A newly spawned subagent's first model request sees only the "你是谁"
+   anchor on an empty tool catalog.
+2. The subagent's self-introduction reply is the promotion signal.
+3. The delegated prompt runs on the next turn with the promoted resident
+   catalog (shells, `str_replace_editor`, and the discovery tools).
+
+Set `includeSubagents: false` on both rows to restore the plain behavior,
+where subagents start with the resident catalog immediately. Each subagent
+costs one extra model call for its anchor turn — a delegation-heavy session
+pays it per subagent.
+
+`zero-anchored-standard` keeps subagents plain by default; enabling the same
+flow there means setting `includeSubagents: true` on its `zero-tool-bootstrap`
+and `anchor-turn` rows (its anchor text stays the fixed test notice).
+
+The trade-off of the mode itself is one extra model call per session: the
+anchor turn is always taken, even when the first message is urgent.
 
-The preset shares plugin modules with the anchored `preset/` directory via
-`../preset/` references, so install that directory as well (see the Install
-section above).
+The directory is self-contained; install it alone or alongside any other mode.
 
 Install as a separate preset id:
 

package/vendor/dsh-anchored-standard/preset/agent.cordis.yml

@@ -159,7 +159,7 @@
           * Please avoid commands that may produce a very large amount of output.
           * Please run long lived commands in the background, e.g. 'sleep 10 &' or start a server in the background.
 
-# Windows-only `bash` tool (see preset/custom-bash.mjs): registers the SAME
+# Windows-only `bash` tool (see custom-bash.mjs): registers the SAME
 # tool name as the persistent shell with a Minimal-compatible description, but
 # executes through the ordinary cross-platform subprocess seam (`bash -c`)
 # instead of a PTY. `bashPath` defaults to `bash` on PATH; point it at Git
@@ -170,7 +170,7 @@
   name: ./custom-bash.mjs
   disabled: !!js process.platform !== 'win32'
   config:
-    bashPath: 'C:\Program Files\Git\bin\bash.exe'
+    bashPath: 'bash.exe'
 
 # ── filesystem ──────────────────────────────────────────────────────────────
 

package/vendor/dsh-anchored-standard/preset/compaction-epoch.mjs

@@ -15,10 +15,16 @@
  * State is memoized per session id and maintained incrementally through
  * `observe()`; a cold session scans its durable log once (so resume and
  * reload reconstruct the same phase), then O(1).
+ *
+ * By default subagents (`delegationDepth > 0`) are treated as already
+ * promoted so their first request can use tools. Set `includeSubagents: true`
+ * to make subagents follow the same bootstrap/anchor phase as top-level
+ * sessions.
  */
 
 /** Build one epoch-aware promotion tracker. */
-export function createEpochPromotion(promoteEvents) {
+export function createEpochPromotion(promoteEvents, options = {}) {
+  const includeSubagents = options.includeSubagents === true
   const promote = new Set(promoteEvents)
   /** sessionId -> { boundary, promoted } */
   const state = new Map()
@@ -53,8 +59,9 @@ export function createEpochPromotion(promoteEvents) {
       if (agent === undefined) return { boundary: -1, promoted: true }
       const session = agent.session
       if (session === undefined) return { boundary: -1, promoted: true }
-      // Subagents keep the full catalog from their very first request.
-      if ((session.header?.delegationDepth ?? 0) > 0) return { boundary: -1, promoted: true }
+      // By default subagents keep the full catalog from their very first
+      // request; includeSubagents makes them follow the normal bootstrap phase.
+      if (!includeSubagents && (session.header?.delegationDepth ?? 0) > 0) return { boundary: -1, promoted: true }
       return state.get(session.id) ?? scan(session)
     },
     /** Incremental feed: call on every `session/event`. */