dsh-plugin-prompt-tool 0.7.2 → 0.8.0

package/engine/anchor-match.mjs

@@ -51,7 +51,7 @@ export function parseRegexFromString(key) {
 
 /** 单键正则编译（逐键匹配：any/all/not 需要精确的命中键数，捕获组会干扰 match 计数）。
  *  useRegex 三态：true=强制正则；false=强制字面；缺省=ST 语义自动检测。 */
-function compileSingle(key, { caseSensitive, wholeWords, useRegex }) {
+function compileSingle(key, { caseSensitive, wholeWords, useRegex, stWords }) {
   const flags = caseSensitive ? '' : 'i'
   if (useRegex === true) {
     // ST use_regex=true：键原样作为正则（作者负责合法性）。
@@ -62,6 +62,7 @@ function compileSingle(key, { caseSensitive, wholeWords, useRegex }) {
     if (auto !== undefined) return auto
   }
   if (wholeWords) {
+    if (stWords) return new RegExp(key.split(/\s+/).length > 1 ? escapeRegExp(key) : `(?:^|\\W)(${escapeRegExp(key)})(?:$|\\W)`, flags)
     return new RegExp(`(^|[^\\p{L}\\p{N}])(${escapeRegExp(key)})(?![\\p{L}\\p{N}])`, `${flags}u`)
   }
   return new RegExp(escapeRegExp(key), flags)
@@ -85,6 +86,7 @@ function compileKeyList(list, options) {
  * @param {boolean} [options.useRegex] 三态：true=强制正则 / false=强制字面 / 缺省=自动检测（ST 语义）
  * @param {'any'|'all'|'not'|'notAny'} [options.logic] 组合逻辑（缺省 any）
  * @param {'scan'|'prefix'} [options.mode] 匹配模式（缺省 scan）
+ * @param {boolean} [options.stWords] ST 整词规则：多词子串、单词 ASCII 边界；仅 ST 导入开启
  * @returns {{ scan: (text: string) => { primary: number, secondary: number, active: boolean } }}
  */
 export function createAnchorMatcher(options = {}) {
@@ -96,9 +98,10 @@ export function createAnchorMatcher(options = {}) {
     useRegex = undefined,
     logic = MATCH_LOGIC.ANY,
     mode = 'scan',
+    stWords = false,
   } = options
-  const primaryList = compileKeyList(keys, { caseSensitive, wholeWords, useRegex })
-  const secondaryList = compileKeyList(secondaryKeys, { caseSensitive, wholeWords, useRegex })
+  const primaryList = compileKeyList(keys, { caseSensitive, wholeWords, useRegex, stWords })
+  const secondaryList = compileKeyList(secondaryKeys, { caseSensitive, wholeWords, useRegex, stWords })
 
   const scan = (raw) => {
     const text = String(raw ?? '')

package/engine/character-tools.mjs

@@ -0,0 +1,11 @@
+/** 角色卡库工具预设模块。 */
+export const name = "character-tools"
+
+export function apply(ctx) {
+  const service = ctx.get("pt-character-tools")
+  if (service === null || service === undefined || typeof service.mount !== "function") {
+    ctx.logger?.warn(name + ": service unavailable; character tools not mounted for this preset")
+    return
+  }
+  ctx.effect(() => service.mount(ctx), name + ": mount")
+}

package/engine/classify-task.mjs

@@ -33,3 +33,21 @@ export function createTaskClassifier({ buildPattern, complexPattern }) {
     },
   }
 }
+
+/**
+ * 通用有序任务规则分类器（subagentToolPolicy.taskRules 单一实现）。
+ * 规则：order 升序（同 order 按数组顺序）、首个匹配获胜；输入为
+ * description + "\n" + prompt；无匹配回落 undefined（调用方用 default）。
+ * 规则在保存时已编译（非法 pattern 拒绝整次保存），此处只按顺序 test。
+ */
+export function createOrderedTaskClassifier(rules) {
+  const ordered = [...(Array.isArray(rules) ? rules : [])]
+    .filter((rule) => rule !== null && typeof rule === 'object' && typeof rule.re?.test === 'function')
+    .sort((a, b) => (a.order - b.order) || 0)
+  return (text) => {
+    for (const rule of ordered) {
+      if (rule.re.test(String(text ?? ''))) return rule.id
+    }
+    return undefined
+  }
+}

package/engine/compaction-epoch.mjs

@@ -2,14 +2,14 @@
  * Epoch-aware promotion tracker shared by the bootstrap and baseline-gate
  * plugins of the anchored presets.
  *
- * A compaction rewrites the model-visible surface: the pre-compaction
+ * A successful compaction rewrites the model-visible surface: the pre-compaction
  * conversation collapses into one synthetic summary message, and the
  * workspace-instruction baseline is re-injected from scratch. The first
  * post-compaction request is therefore a "second first request" — the same
  * first-token conditions the anchored presets exist to control. Promotion is
  * epoch-aware: only a durable promotion signal (`tool/call` and/or
  * `assistant/message`, per the caller's `promoteEvents`) recorded AFTER the
- * last `compaction/end` boundary counts as promoted. Before any compaction
+ * last successful `compaction/end` boundary counts as promoted. Before any compaction
  * the boundary is -1, which preserves the original one-shot semantics.
  *
  * State is memoized per session id and maintained incrementally through
@@ -21,10 +21,10 @@
  * to make subagents follow the same bootstrap/anchor phase as top-level
  * sessions.
  *
- * GATE MODE (liangshen 稳定化扩展, source: xiaobright/dsh-anchored-standard
+ * GATE MODE (strict two-phase stabilization extension, source: xiaobright/dsh-anchored-standard
  * MIT + phase-1 quarantine): `promoteGate: true` gates the promotion on the
  * first reasoning block classifying minimal-like (`we` present, no `let me`),
- * with a `maxPromoteSteps` (default 4) fallback; `promoteAfterFirstResponse:
+ * with a `maxPromoteSteps` fallback supplied by the caller's config; `promoteAfterFirstResponse:
  * true` promotes a tool-less first response once it has responded, and also
  * releases an anchor-gated session when its first turn ends. Gate mode uses
  * the durable-event state machine below and ignores `promoteEvents` (fixed
@@ -32,7 +32,9 @@
  * Non-gate mode keeps the original event-set semantics byte-for-byte.
  */
 
-/** 首段 reasoning 块分类（liangshen 移植）：we 且无 let me = minimal-like。 */
+import { sessionEvents, sessionState } from './shared.mjs'
+
+/** 首段 reasoning 块分类（严格门控扩展）：we 且无 let me = minimal-like。 */
 export function classifyReasoning(text) {
   const trimmed = String(text ?? '').trim()
   const we = [...trimmed.matchAll(/\bwe\b/gi)].length
@@ -50,19 +52,21 @@ export function hasAnchoredReasoning(content) {
   return first !== undefined && classifyReasoning(first.text).label === 'minimal-like'
 }
 
+/** True only when compaction completed and changed the model-visible surface. */
+export function isSuccessfulCompactionEnd(event) {
+  return event?.type === 'compaction/end' && event.data?.error === undefined
+}
+
 /** Build one epoch-aware promotion tracker. */
 export function createEpochPromotion(promoteEvents, options = {}) {
   const includeSubagents = options.includeSubagents === true
   const promoteGate = options.promoteGate === true
   const promoteAfterFirstResponse = options.promoteAfterFirstResponse === true
-  const maxPromoteSteps = Number.isSafeInteger(options.maxPromoteSteps) && options.maxPromoteSteps > 0
-    ? options.maxPromoteSteps
-    : 4
+  // 门控回退步数由调用方配置提供（tool-bootstrap 在开启门控时做必填校验）：
+  // 引擎不内置默认；未提供时步数兜底不生效，只按 anchored 判定。
+  const maxPromoteSteps = options.maxPromoteSteps
   const promote = new Set(promoteEvents)
   const gated = promoteGate || promoteAfterFirstResponse
-  /** sessionId -> entry（boundary/promoted + 门控字段） */
-  const state = new Map()
-
   const freshEntry = (boundary) => ({
     boundary,
     promoted: false,
@@ -73,7 +77,24 @@ export function createEpochPromotion(promoteEvents, options = {}) {
     steps: 0,
   })
 
-  /** 门控晋升判定（liangshen decidePromotion 移植）。 */
+  /**
+   * 会话 epoch 条目容器（`sessionState`：统一访问接口，键 / 淘汰 / 复位三项与迁移前逐条相同）。
+   *
+   * - 键类型：`session.id`。
+   * - 淘汰策略：超 `MAX_TRACKED_SESSIONS` 时 `clear()` 全清（`evict` 缺省档），
+   *   清空只触发一次冷扫重建，相位由 durable 事件流重建。
+   * - 复位：**不声明**——压缩边界不是「删条目」：`applyEvent` 遇成功 `compaction/end`
+   *   直接把条目重置为 `freshEntry(seq)` 新边界（见 `scan` / `observe`），条目本身必须留在
+   *   容器里。声明 `reset` 只会多注册一条监听并改变语义，故 `ctx` 完全用不到、不传入。
+   *
+   * 无 `session.id` 的会话不记账（`sessionState` 既有决定，见 `predicates.mjs`）：`peek` 恒
+   * 未命中 → 每次按该会话自己的 durable 事件流重建。旧实现把这类会话的条目存在共享的
+   * `undefined` 键上（跨会话串味、且能把 `observe` 喂进来但不在事件流里的状态钉住），
+   * 现在以 durable 事实为准——方向与「状态是快路径、真相在事件流」的纪律一致。
+   */
+  const state = sessionState(undefined, () => freshEntry(-1))
+
+  /** 门控晋升判定（严格门控扩展）。 */
   const decideGate = (entry) => {
     if (entry.promoted) return true
     if (entry.toolCalled && !promoteGate) return true
@@ -83,10 +104,10 @@ export function createEpochPromotion(promoteEvents, options = {}) {
     return false
   }
 
-  /** 应用一个事件；compaction/end 返回新 entry（旧状态清零、boundary 前推）。 */
+  /** 应用一个事件；成功 compaction/end 返回新 entry（旧状态清零、boundary 前推）。 */
   const applyEvent = (entry, event) => {
     const seq = event.seq ?? 0
-    if (event.type === 'compaction/end') return freshEntry(seq)
+    if (isSuccessfulCompactionEnd(event)) return freshEntry(seq)
     if (seq <= entry.boundary) return entry
     if (gated) {
       if (event.type === 'tool/call') entry.toolCalled = true
@@ -106,8 +127,8 @@ export function createEpochPromotion(promoteEvents, options = {}) {
   /** Scan a session's durable log from scratch (cold start / resume). */
   const scan = (session) => {
     let entry = freshEntry(-1)
-    for (const event of session.events) entry = applyEvent(entry, event)
-    state.set(session.id, entry)
+    for (const event of sessionEvents(session)) entry = applyEvent(entry, event)
+    state.set(session, entry)
     return entry
   }
 
@@ -115,7 +136,7 @@ export function createEpochPromotion(promoteEvents, options = {}) {
     /**
      * Current phase of the agent's session.
      * @param agent - the assembly/pre-step agent, or undefined outside an agent.
-     * @returns { boundary, promoted } — `boundary` is the last compaction/end
+     * @returns { boundary, promoted } — `boundary` is the last successful compaction/end
      *   seq (-1 before any compaction); `promoted` is true when a durable
      *   promotion signal exists after that boundary.
      */
@@ -126,14 +147,14 @@ export function createEpochPromotion(promoteEvents, options = {}) {
       // 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)
+      return state.peek(session) ?? scan(session)
     },
     /** Incremental feed: call on every `session/event`. */
     observe(session, event) {
-      const entry = state.get(session.id)
+      const entry = state.peek(session)
       if (entry === undefined) return
       const next = applyEvent(entry, event)
-      if (next !== entry) state.set(session.id, next)
+      if (next !== entry) state.set(session, next)
     },
   }
 }

package/engine/compositions/library/agent-instructions.yml

@@ -0,0 +1,9 @@
+# module: agent-instructions
+# source: master/packages/bundle/web-app/presets/standard.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
+# local patches: 0
+
+- id: agent-instructions
+  name: '@deepseek-ai/dsh-agent-instructions'
+  config:
+    maxBytes: 65536

package/engine/compositions/library/command-goal.yml

@@ -1,11 +1,7 @@
 # module: command-goal
-# source: D:\AI\GitHub\deepseek-harness/packages/preset/agent-presets/presets/standard/agent.cordis.yml
+# source: master/packages/bundle/web-app/presets/standard.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
 # local patches: 0
 
-# ── goals ───────────────────────────────────────────────────────────────────
-
-# The goal service and session driver stay on the host plane, where the Gateway
-# can resolve them. The human command and model-facing tool register into this
-# preset's scoped layers.
 - id: command-goal
   name: '@deepseek-ai/dsh-command-goal'

package/engine/compositions/library/compaction.yml

@@ -1,18 +1,8 @@
 # module: compaction
-# source: D:\AI\GitHub\deepseek-harness/packages/preset/agent-presets/presets/standard/agent.cordis.yml
+# source: master/packages/bundle/web-app/presets/standard.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
 # local patches: 0
 
-# ── 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
@@ -22,31 +12,11 @@
   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.

package/engine/compositions/library/delegation-ptc.yml

@@ -0,0 +1,58 @@
+# module: delegation-ptc
+# source: master/packages/bundle/web-app/presets/ptc.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
+# local patches: 0
+
+- 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
+    - 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'
+      disabled: true
+      config:
+        provider: spawn
+    - id: tool-workflow
+      name: '@deepseek-ai/dsh-tool-workflow'
+      disabled: true
+    - id: tool-ralph
+      name: '@deepseek-ai/dsh-tool-ralph'
+      disabled: true
+      config:
+        subagentProvider: spawn
+        maxRounds: 64

package/engine/compositions/library/delegation.yml

@@ -1,24 +1,8 @@
 # module: delegation
-# source: D:\AI\GitHub\deepseek-harness/packages/preset/agent-presets/presets/standard/agent.cordis.yml
+# source: master/packages/bundle/web-app/presets/standard.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
 # local patches: 0
 
-# ── 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
@@ -27,10 +11,8 @@
   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:
@@ -38,22 +20,12 @@
         toolName: subagent
         modelSelectionSettings: true
         backgroundMode: continuable
-
-    # Fork omits model selection so provider/model stay equal to the parent and
-    # the inherited history remains eligible for KV Cache reuse. This preset
-    # keeps fork continuable and accepts its child-scoped `report` additions invalidating
-    # that prefix; issue #2124 tracks cache-preserving continuable fork.
     - 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
@@ -62,7 +34,6 @@
         toolName: subagent_codex
         backgroundMode: one-shot
         maxDepth: provider-managed
-
     - id: tool-subagent-claude-code
       name: '@deepseek-ai/dsh-tool-subagent'
       disabled: true
@@ -71,19 +42,15 @@
         toolName: subagent_claude_code
         backgroundMode: one-shot
         maxDepth: provider-managed
-
-    - id: workflow-worker-thread
-      name: '@deepseek-ai/dsh-workflow-worker-thread'
+    - id: workflow-ptc
+      name: '@deepseek-ai/dsh-workflow-ptc'
       config:
         provider: spawn
-
     - id: tool-workflow
       name: '@deepseek-ai/dsh-tool-workflow'
-
     - id: tool-ralph
       name: '@deepseek-ai/dsh-tool-ralph'
+      disabled: true
       config:
         subagentProvider: spawn
         maxRounds: 64
-
-# ── remaining model-facing rows ─────────────────────────────────────────────

package/engine/compositions/library/persistent-shell.yml

@@ -1,24 +1,21 @@
 # module: persistent-shell
-# source: D:\AI\GitHub\deepseek-harness/packages/preset/agent-presets/presets/minimal/agent.cordis.yml
-# local patches: 2
+# source: master/packages/bundle/web-app/presets/minimal.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
+# local patches: 0
 
 - 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-bash
       name: '@deepseek-ai/dsh-terminal-bash'
       disabled: !!js process.platform === 'win32'
       config:
-        shellPath: !!js "process.getBuiltinModule?.('node:fs')?.existsSync('/bin/bash') ? '/bin/bash' : 'bash'"
         timeoutMs: 300000
-
     - id: persistent-bash
       name: '@deepseek-ai/dsh-tool-bash-persistent'
       disabled: !!js process.platform === 'win32'
@@ -27,20 +24,17 @@
         description: |-
           Run commands in a bash shell
           * When invoking this tool, the contents of the "command" parameter does NOT need to be XML-escaped.
-          * You don't have access to the internet via this tool.
-          * You do have access to a mirror of common linux and python packages via apt and pip.
+          * Network access depends on the task environment. Prefer configured mirrors/proxies when they are available.
           * State is persistent across command calls and discussions with the user.
           * To inspect a particular line range of a file, e.g. lines 10-25, try 'sed -n 10,25p /path/to/the/file'.
           * 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.
-
     - 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'
@@ -54,6 +48,3 @@
           * 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.
-
-# The bare local filesystem shadows the host's sandboxed provider only for this
-# preset. The editor shares that realm and requires absolute paths.

package/engine/compositions/library/planning.yml

@@ -1,11 +1,8 @@
 # module: planning
-# source: D:\AI\GitHub\deepseek-harness/packages/preset/agent-presets/presets/standard/agent.cordis.yml
+# source: master/packages/bundle/web-app/presets/standard.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
 # local patches: 0
 
-# ── 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
@@ -16,26 +13,14 @@
       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.
+          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.
 
-              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.
+          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.
 
-              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.
+          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.
 
-              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.
+          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.
 
-# ── compaction ──────────────────────────────────────────────────────────────
+          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.
 
-# `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.
+          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.

package/engine/compositions/library/skill-filesystem-cordis.yml

@@ -0,0 +1,10 @@
+# module: skill-filesystem-cordis
+# source: master/packages/bundle/web-app/presets/cordis.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
+# local patches: 0
+
+- id: skill-filesystem
+  name: '@deepseek-ai/dsh-skill-filesystem'
+  config:
+    customSkillDirs:
+      - !!js process.getBuiltinModule('node:path').join(process.getBuiltinModule('node:path').dirname(process.getBuiltinModule('node:module').createRequire(baseUrl).resolve('@deepseek-ai/dsh-agent-preset/package.json')), 'skills')

package/engine/compositions/library/skill-filesystem.yml

@@ -1,13 +1,7 @@
 # module: skill-filesystem
-# source: D:\AI\GitHub\deepseek-harness/packages/preset/agent-presets/presets/standard/agent.cordis.yml
+# source: master/packages/bundle/web-app/presets/standard.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
 # local patches: 0
 
-# ── 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).
 - id: skill-filesystem
   name: '@deepseek-ai/dsh-skill-filesystem'

package/engine/compositions/library/tool-ask-user.yml

@@ -1,8 +1,7 @@
 # module: tool-ask-user
-# source: D:\AI\GitHub\deepseek-harness/packages/preset/agent-presets/presets/standard/agent.cordis.yml
+# source: master/packages/bundle/web-app/presets/standard.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
 # local patches: 0
 
-# ── remaining model-facing rows ─────────────────────────────────────────────
-
 - id: tool-ask-user
   name: '@deepseek-ai/dsh-tool-ask-user'

package/engine/compositions/library/tool-bash.yml

@@ -1,16 +1,8 @@
 # module: tool-bash
-# source: D:\AI\GitHub\deepseek-harness/packages/preset/agent-presets/presets/standard/agent.cordis.yml
-# local patches: 1
+# source: master/packages/bundle/web-app/presets/standard.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
+# local patches: 0
 
-# ── 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: true
+  disabled: !!js process.platform === 'win32'

package/engine/compositions/library/tool-cordis.yml

@@ -0,0 +1,7 @@
+# module: tool-cordis
+# source: master/packages/bundle/web-app/presets/cordis.patch.yml
+# commit: c36a83ff6bb95e3f82cf79f9be7c724270a8aa61
+# local patches: 0
+
+- id: tool-cordis
+  name: '@deepseek-ai/dsh-tool-cordis'