@menghuan1918/dsh-apollo 0.3.0 → 0.4.1

package/presets/eng-noask/plugins/mode-instructions/package.json

@@ -1,7 +0,0 @@
-{
-  "name": "dsh-preset-eng-mode-instructions",
-  "private": true,
-  "type": "module",
-  "main": "index.js",
-  "version": "0.1.0"
-}

package/presets/eng-noask/plugins/wait-subagent/index.js

@@ -1,228 +0,0 @@
-/**
- * `wait_subagent` tool — explicit wait for continuable children to settle.
- *
- * Preset-local plugin for the eng preset (resolved relative to this preset's
- * directory). Continuable subagents live in the `subagents` registry, not the
- * `jobs` registry, so the only settlement signal is the scoped `subagent/end`
- * event. The tool takes an ARRAY of durable child ids (`subagent_id`), awaits
- * them all concurrently (duplicates deduped, order preserved), and returns one
- * SHORT line per id (done + stopReason).
- *
- * The children's content is none of this tool's business: the subagent manager
- * unconditionally delivers a settlement notice to the parent BEFORE
- * `subagent/end` fires (dispose order: notifySettlement() →
- * observer.settle()), carrying the one-line account and the closing message.
- * A busy parent is steered, so the notice sits in the pending next-step queue
- * and reaches the model right after this tool result — exactly once, per
- * child, by the framework. Earlier designs returned the child's final message
- * here AND spliced the duplicate notice (and any mid-run `report`) out of the
- * parent inbox; that coupled this plugin to `agent.inbox` internals and to
- * the `subagent-report` source kind, which upstream removed in
- * 0.1.2-alpha.4 (bidirectional `send_message` replaced `report`). Returning
- * "done" lines and leaving delivery to the framework has no such coupling.
- * Mid-run messages the child sends (`send_message`, source kind
- * `agent-message`) likewise stay in place.
- *
- * `timeout_ms` is ONE shared window over the whole batch (all timers start at
- * the same instant), matching the semantics same-message parallel calls had.
- * An id that is not a direct child fails the whole call fast — nobody is
- * waited for — keeping the contract the single-id version had. A child
- * dispatched moments ago may not have started its first turn yet: its status
- * is not `running` and no settlement exists. Returning early with a "not
- * running" note there (the pre-grace behavior) ended the turn before the
- * child even started and forced a re-wait on the next turn — session audit
- * 2f5dd618. Instead, a not-yet-started child gets a startup grace window
- * (START_GRACE_MS): the tool keeps waiting while the child spins up,
- * settles, the optional timeout elapses, or the grace expires without the
- * child ever starting (only then a retryable informational line).
- *
- * Zero imports on purpose: the module loads from the preset directory, where
- * Node's upward node_modules walk never reaches the harness install, so bare
- * package imports would fail. Everything needed comes from the context.
- */
-
-export const name = 'tool-wait-subagent'
-
-export const inject = ['tools', 'subagents', 'agents']
-
-/** Grace window for a just-dispatched child that has not started running yet. */
-const START_GRACE_MS = 30_000
-
-/** Status polling interval while waiting for a not-yet-started child. */
-const POLL_MS = 250
-
-export function apply(ctx) {
-  /** childId -> { time, info } — latest settlement observed since mount. */
-  const settled = new Map()
-  /** childId -> finish(info) callbacks awaiting settlement. */
-  const waiters = new Map()
-
-  ctx.on('subagent/end', (info) => {
-    const id = info && info.id
-    if (typeof id !== 'string') return
-    settled.set(id, { time: Date.now(), info })
-    const list = waiters.get(id)
-    if (list !== undefined) {
-      waiters.delete(id)
-      for (const finish of [...list]) finish({ kind: 'settled', info })
-    }
-  })
-
-  ctx.tools.register({
-    name: 'wait_subagent',
-    description: 'Wait for one or more background continuable subagents (spawned by subagent or subagent_fork) to finish their current turn. Pass their durable ids as an array in subagent_id — all are awaited concurrently and the result carries one short line per id (done + stop reason); a child\'s closing message arrives as the framework settlement notice immediately after this result; do not expect it here. Blocks until every listed child settles, the optional timeout_ms elapses (one shared window over all ids), or the user interrupts — without timeout_ms, until completion. A just-dispatched child that has not started yet is awaited through a brief startup grace rather than reported as not running. Use it when your next step depends on those results; with independent work remaining, prefer background plus completion notices. Do not pass bash job ids — those use job_output.',
-    parameters: {
-      type: 'object',
-      properties: {
-        subagent_id: {
-          type: 'array',
-          items: { type: 'string' },
-          minItems: 1,
-          description: 'One or more durable subagent ids returned by the subagent or subagent_fork tool call; every id is awaited concurrently.',
-        },
-        timeout_ms: {
-          type: 'integer',
-          description: 'Optional maximum wait in milliseconds applied as one shared window over all ids; omit to wait until every child settles. On expiry the tool returns while some children are still running.',
-        },
-      },
-      required: ['subagent_id'],
-    },
-    output: {
-      schema: { type: 'string' },
-      render: (_args, value) => [{ type: 'text', text: value }],
-    },
-    isConcurrencySafe: () => true,
-    async execute(args, exec) {
-      // Dedupe preserving input order; the schema already enforces a
-      // non-empty array, the guard below only covers malformed direct calls.
-      const ids = [...new Set(Array.isArray(args.subagent_id) ? args.subagent_id : [])]
-      if (ids.length === 0) return 'subagent_id must be a non-empty array of subagent ids.'
-      const parent = exec.agent
-      if (parent === undefined) throw new Error('wait_subagent requires a calling agent (exec.agent was undefined)')
-
-      // Verify every id is one of this agent's direct children — fail fast,
-      // waiting for nobody (the contract the single-id version had).
-      let entries
-      try {
-        entries = await ctx.subagents.listChildren(parent.id, exec.signal)
-      } catch (error) {
-        return 'listChildren failed: ' + (error && error.message ? error.message : String(error))
-      }
-      const known = new Set(entries.map((entry) => entry.id))
-      const unknown = ids.filter((id) => !known.has(id))
-      if (unknown.length > 0) {
-        return `unknown subagent ${unknown.map((id) => `"${id}"`).join(', ')}: not a direct child of this agent (list_agents shows your children; only depth-1 children can be awaited).`
-      }
-
-      const statusOf = (id) => {
-        const agent = ctx.agents.get(id)
-        return agent === undefined ? 'ready' : agent.status === 'running' ? 'running' : 'idle'
-      }
-
-      /** Settlement line: short done line; content belongs to the framework notice. */
-      const doneLine = (id, info) => `subagent ${id} done (${info && info.stopReason ? info.stopReason : 'completed'}); its closing message follows as the settlement notice.`
-
-      const startedAt = Date.now()
-      const capMs = typeof args.timeout_ms === 'number' && args.timeout_ms > 0 ? args.timeout_ms : undefined
-
-      /**
-       * Wait for one child. Resolves with {kind:'settled',info} |
-       * {kind:'timedOut'} | {kind:'aborted'} | {kind:'notStarted'}. The
-       * per-id machinery (settled fast path, waiter registration, timeout
-       * timer, startup-grace poller) is the single-id logic of old,
-       * unchanged; Promise.all over ids gives the concurrent batch.
-       */
-      const waitOne = (id) => {
-        // Fast path: the child is not running and a settlement is already on
-        // record — resolve immediately (the notice was already delivered when
-        // the child settled, so it is in the conversation history).
-        if (statusOf(id) !== 'running') {
-          const hit = settled.get(id)
-          if (hit !== undefined) return Promise.resolve({ kind: 'settled', info: hit.info })
-        }
-
-        return new Promise((resolve) => {
-          let done = false
-          let timer
-          let poller
-          const finish = (value) => {
-            if (done) return
-            done = true
-            if (poller !== undefined) clearInterval(poller)
-            const list = waiters.get(id)
-            if (list !== undefined) {
-              const index = list.indexOf(finish)
-              if (index >= 0) list.splice(index, 1)
-              if (list.length === 0) waiters.delete(id)
-            }
-            if (timer !== undefined) clearTimeout(timer)
-            if (exec.signal !== undefined) exec.signal.removeEventListener('abort', onAbort)
-            resolve(value)
-          }
-          const onAbort = () => finish({ kind: 'aborted' })
-
-          const list = waiters.get(id) ?? []
-          list.push(finish)
-          waiters.set(id, list)
-          // All ids share startedAt, so one capMs value is one shared window.
-          if (capMs !== undefined) timer = setTimeout(() => finish({ kind: 'timedOut' }), capMs)
-          if (exec.signal !== undefined) {
-            if (exec.signal.aborted) {
-              finish({ kind: 'aborted' })
-              return
-            }
-            exec.signal.addEventListener('abort', onAbort, { once: true })
-          }
-
-          // Startup grace: a freshly dispatched child sits between spawn and
-          // its first turn (status not `running`, no settlement yet). Keep the
-          // wait alive while it spins up; once `running`, only `subagent/end`
-          // (the listener above) resolves us. If the grace expires without the
-          // child ever starting or settling, fall back to a retryable note
-          // instead of the old misleading "is not running" early return.
-          poller = setInterval(() => {
-            if (done) return
-            const hit = settled.get(id)
-            if (hit !== undefined) {
-              finish({ kind: 'settled', info: hit.info })
-              return
-            }
-            if (statusOf(id) !== 'running' && Date.now() - startedAt >= START_GRACE_MS) {
-              finish({ kind: 'notStarted' })
-            }
-          }, POLL_MS)
-
-          // Re-check: the child may have settled between the fast path above
-          // and waiter registration. Only a settlement AFTER this wait started
-          // counts as a live result.
-          const hit = settled.get(id)
-          if (hit !== undefined && hit.time >= startedAt) finish({ kind: 'settled', info: hit.info })
-        })
-      }
-
-      const outcomes = await Promise.all(ids.map((id) => waitOne(id)))
-
-      // Every waiter shares one abort signal, so an interruption either
-      // aborts the whole batch or lands after some children already settled.
-      // Collapse the all-aborted case into one line; mixed cases keep
-      // per-id lines so the settled ones are not lost.
-      if (outcomes.length > 0 && outcomes.every((outcome) => outcome.kind === 'aborted')) {
-        return `wait for ${ids.length} subagent${ids.length === 1 ? '' : 's'} was aborted by user interruption; the children may still be running.`
-      }
-
-      const lines = outcomes.map((outcome, index) => {
-        const id = ids[index]
-        if (outcome.kind === 'aborted') return `wait for subagent ${id} was aborted by user interruption; the child may still be running.`
-        if (outcome.kind === 'timedOut') return `timed out waiting for subagent ${id}; it is still running. You will be notified when it finishes — you can wait_subagent it again or continue with other work.`
-        if (outcome.kind === 'notStarted') {
-          return `subagent ${id} has not started after ${Math.round(START_GRACE_MS / 1000)}s (status: ${statusOf(id)}). It may still be spinning up — call wait_subagent again, or continue with other work; you will be notified when it finishes.`
-        }
-        // Real settlement: short done line; the framework's settlement notice
-        // (already delivered to the parent inbox before `subagent/end`)
-        // carries the closing message — nothing to consume or deduplicate.
-        return doneLine(id, outcome.info)
-      })
-      return lines.join('\n')
-    },
-  })
-}

package/presets/eng-noask/plugins/wait-subagent/package.json

@@ -1,7 +0,0 @@
-{
-  "name": "dsh-preset-eng-wait-subagent",
-  "private": true,
-  "type": "module",
-  "main": "index.js",
-  "version": "0.1.0"
-}

package/presets/eng-noask.patch.yml

@@ -1,341 +0,0 @@
-# dsh-apollo bundle patch: the `eng-noask` (工程模式(无提问)) agent preset —
-# a copy of the `eng` plugins block with exactly one capability removed: the
-# `tool-ask-user` row is gone (sessions expose no ask_user_question tool),
-# plus a no-ask discipline line in the preset-local mode-instructions section
-# and the plan-mode section's two ask_user_question mentions rewritten for a
-# preset that cannot ask. Everything else matches `eng`;
-# tests/upstream-drift.test.mjs fails when this block drifts from `eng`
-# beyond the removed row. Keep the two in sync by editing `eng` first, then
-# redoing the copy.
-#
-# Declared as one `@deepseek-ai/dsh-agent-preset` insert row (the DSH 0.2.1
-# preset mechanism; the `<dshHome>/.agent-presets` scan root is gone).
-# `config.id` MUST stay `eng-noask`: it is the preset identity historical
-# sessions resume by. Preset-local plugin modules are referenced by bare
-# package subpaths (`@menghuan1918/dsh-apollo/presets/eng-noask/plugins/...`) resolved
-# from the profile directory's node_modules, not the preset directory.
-
-- insert:
-    - id: preset-eng-noask
-      name: '@deepseek-ai/dsh-agent-preset'
-      config:
-        id: eng-noask
-        name: 工程模式(无提问)
-        description: >-
-          工程模式的无人值守变体：剔除 ask_user_question 工具，配无提问纪律——全程自主决策不提问，关键假设与替代方案写进最终报告。
-        order: 11
-        plugins:
-          #
-          # This plugins block 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-preset` 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.
-          # One row on purpose: the rich engineering rules live in the user-global
-          # instructions (~/.dsh/AGENTS.md) and the preset's `eng:mode-instructions`
-          # section, not in the persona. `eng:mode-instructions` owns the delegation
-          # policy; the tiers stay global because they track local route config.
-          # 0.2.1's upstream `standard` preset carries `prefix` only: the working-
-          # directory `suffix` line it used to set is gone, and eng follows suit.
-          - id: persona
-            name: '@deepseek-ai/dsh-persona'
-            config:
-              prefix: >-
-                You are a coding agent powered by the {{model}} model.
-
-          # Workspace instructions (repository AGENTS.md files) are injected from the
-          # first request, capped at 64 KiB.
-          - id: agent-instructions
-            name: '@deepseek-ai/dsh-agent-instructions'
-            config:
-              maxBytes: 65536
-
-          # 0.2.1 standard adds the per-step time context (sampled current time,
-          # browser time zone and elapsed time) so date/time reasoning does not depend
-          # on the model's own clock. It consumes host services and provides nothing,
-          # so it needs no realm.
-          - id: time-context
-            name: '@deepseek-ai/dsh-time-context'
-
-          # ── 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.
-          #
-          # LOCAL OVERRIDE (2026-09-22): `maxConsecutiveWakes` is 5000 instead of the
-          # bundled 3. The budget is spent by every completion that opens a turn on an
-          # idle owner and is restored ONLY by a user-authored message, so a long
-          # unattended chain of background jobs parks after its third wake — from the
-          # fourth completion on, the notice degrades to injection and waits for the
-          # user's next input. This row and its config are copied verbatim from the
-          # eng patch; keep the two in sync (the upstream-drift test compares
-          # same-id row configs).
-          - id: tool-jobs
-            name: '@deepseek-ai/dsh-tool-jobs'
-            config:
-              maxConsecutiveWakes: 5000
-
-          # The automation-task tools (schedule_create/list/update/delete) are
-          # deliberately omitted from engineering mode: coding/infrastructure work
-          # does not need scheduled reminders. The host `schedule` service and the
-          # sidebar Automation page stay available to other presets.
-
-          # ── 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'
-
-          - id: tool-skill
-            name: '@deepseek-ai/dsh-tool-skill'
-
-          # ── goals ───────────────────────────────────────────────────────────────────
-
-          # Native command-goal/tool-goal rows are deliberately omitted. The goal
-          # domain is owned by the independent dsh-better-goal plugin row in the
-          # top-level patch: it registers one `goal` tool and one `/goal` command
-          # per Agent, hides any legacy goal tools a preset still carries, and has
-          # its own Plugins row for round limits and question timeouts. The two
-          # removed rows remain deliberate removals in tests/upstream-drift.test.mjs,
-          # which asserts they still exist upstream before filtering them out.
-
-          # ── 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 the user approves your plan through exit_plan_mode or 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. This preset exposes no ask-user tool: never wait on the user for a choice — decide autonomously, and record the decision, its key assumptions, and the alternatives you rejected in the plan so review can catch them. 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. 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:
-                  # Deliberately 2x the upstream `standard` preset (8192/4096/1024): eng
-                  # sessions emit large build/test/log tool results, and the extra
-                  # head/tail retention preserves the failure context the agent acts on.
-                  thresholdChars: 16384
-                  headChars: 8192
-                  tailChars: 2048
-
-          # ── 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.
-          #
-          # 0.1.2-alpha.4 note: the one-way child `report` tool is gone — parent/child
-          # messaging now rides the globally named `send_message` registered by
-          # `tool-subagent-control` below (children inherit it too), so this preset
-          # mounts no messaging row of its own.
-          - 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
-
-              # Fork omits model selection so provider/model stay equal to the parent and
-              # the inherited history remains eligible for KV Cache reuse.
-              - id: tool-subagent-fork
-                name: '@deepseek-ai/dsh-tool-subagent'
-                config:
-                  provider: fork
-                  toolName: subagent_fork
-
-              # 0.1.6-alpha.2 renamed `dsh-workflow-worker-thread` to `dsh-workflow-ptc`
-              # (workflow orchestration in the shared sandboxed Node PTC runtime).
-              - id: workflow-ptc
-                name: '@deepseek-ai/dsh-workflow-ptc'
-                config:
-                  provider: spawn
-
-              - id: tool-workflow
-                name: '@deepseek-ai/dsh-tool-workflow'
-
-          # ── remaining model-facing rows ─────────────────────────────────────────────
-
-          # No `tool-ask-user` here: this preset runs unattended. The no-ask discipline
-          # lives in the preset-local mode-instructions section.
-
-          - id: tool-todo
-            name: '@deepseek-ai/dsh-tool-todo'
-            config:
-              allowParallelInProgress: true
-
-          # The `web` service and its search/fetch providers stay in the host
-          # composition; only the model-facing tool is per-session. `fetch` reads the
-          # host-mounted SSRF-guarded `web-fetch-http` provider.
-          - id: tool-web
-            name: '@deepseek-ai/dsh-tool-web'
-            config:
-              fetch: true
-              searchTimeoutMs: 60000
-
-          # Declares deliverable files to the user (file-card surface). Upstream
-          # `standard` mounts it; eng is a fork-copy of that block, so this row has to be
-          # carried by hand — `tests/upstream-drift.test.mjs` fails when a shipped
-          # preset gains rows that eng never picked up.
-          - id: present
-            name: '@deepseek-ai/dsh-tool-present'
-
-          # 0.2.1 ships both plugin surfaces disabled by default; enable either only in a
-          # copy of this plugins block (edits saved from the Web editor override
-          # config.plugins by row id from the profile patch).
-          - id: tool-plugin-manager
-            name: '@deepseek-ai/dsh-plugin-manager/tools'
-            disabled: true
-
-          - id: tool-plugin-market
-            name: '@deepseek-ai/dsh-plugin-market/tools'
-            disabled: true
-
-          # ── subagent waiting ─────────────────────────────────────────────────────────
-
-          # Preset-local plugin: explicit wait for one continuable child to settle, so
-          # the agent can block on a specific subagent (pi-style await_task semantics)
-          # without giving up send_message continuations. The module specifier is a
-          # bare subpath of this package (@menghuan1918/dsh-apollo/presets/eng-noask/plugins/...):
-          # config.plugins names resolve from the profile directory's node_modules,
-          # where this package is installed or linked; it has zero bare imports on
-          # purpose.
-          - id: tool-wait-subagent
-            name: '@menghuan1918/dsh-apollo/presets/eng-noask/plugins/wait-subagent/index.js'
-
-          # ── exit guard ───────────────────────────────────────────────────────────────
-          #
-          # Preset-local plugin: pi-atlas 式退出守卫。回合结束（agent/turn-stopping）
-          # 时若有运行中的直接子代理或后台任务，注入 next-step 提醒（agent.steer）
-          # 强制回合继续，直到 wait_subagent / job_output / job_kill 处理完毕或用户
-          # 中断（被中断回合不触发）。开关为正式 Config.exitGuard，默认关闭，
-          # 每次事件读取当前值，设置保存后即时生效。监听器注册型
-          # 插件，无服务发布，无需 realm。
-          - id: eng-exit-guard
-            name: '@menghuan1918/dsh-apollo/presets/eng-noask/plugins/exit-guard/index.js'
-
-          # ── mode instructions ────────────────────────────────────────────────────────
-
-          # Preset-local prompt section carrying the two eng-only rules: the exit guard
-          # contract and the delegation/orchestration policy (the latter moved out of the
-          # user-global ~/.dsh/AGENTS.md on 2026-09-11 — the model tiers stay there
-          # because they mirror this host's `subagent-model-selection` route list).
-          # Registered as a system-prompt section (order 1, right after the persona slot)
-          # so it is scoped to sessions mounted on this preset and nothing else; injected
-          # from the first request alongside the other sections.
-          # This plugins block (presets/eng-noask.patch.yml) is the single source of truth;
-          # the 0.2.1 bundle-patch mechanism loads it straight from this file, with no
-          # boot-time copy in between.
-          - id: eng-mode-instructions
-            name: '@menghuan1918/dsh-apollo/presets/eng-noask/plugins/mode-instructions/index.js'