dsh-ppt-studio 1.1.0

package/agent-presets/ppt/agent.cordis.yml

@@ -0,0 +1,308 @@
+# The `standard` agent preset: the full coding agent, mounted once per process.
+#
+# This file is an AGENT-PLANE composition. The roster mounts it ONCE under a
+# standing scope; every session naming it joins by scope parentage, so the
+# tools and prompt sections registered here cover each joined agent while a
+# session's own state stays keyed per Session/Agent inside the plugins. The
+# host composition (`base.cordis.yml` + `web.cordis.yml`) keeps everything a
+# preset must not own: the registries themselves, the sandbox and approval
+# stack, persistence, and the model route.
+#
+# A service row here MUST sit inside a group carrying an `isolate` realm.
+# Without one it publishes into the root realm, where it is process-global —
+# another preset publishing the same name collides, and a host reader would
+# resolve one preset's instance for every session; the agent-preset registry
+# 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.)
+#
+# 【本文件在 DSH 0.1.7 上怎么被用（2026-09-24 适配）】
+# 它是一份 **Loader 方言的条目数组**，由 `lib/preset-delivery.js` 读出来、作为
+# `plugins` 交给 `ctx.agentPresets.register({id:'ppt', name, description, order, plugins})`。
+# 0.1.6 及以前是靠把本文件**写到 `<dshHome>/.agent-presets/ppt/`** 让宿主扫到——那条路
+# 在 0.1.7 已被上游删除（原文："the harness discovers no preset on disk"），所以现在是**声明**。
+# 两个必须守住的细节（都在 preset-delivery.js 里有源码级依据）：
+#   · `!!js` 会被 Loader 求值（`{__jsExpr}`），自己读 YAML 时必须**保真**，否则平台开关会失真；
+#   · 相对模块名会被解析到**注册表所在层**（= dsh-web-app 包目录），不是本目录——本文件里没有相对名。
+
+# ── identity ────────────────────────────────────────────────────────────────
+
+# The preset's own persona, shadowing the deployment default for this agent.
+# `{{model}}` and `{{cwd}}` resolve from the agent's own route and workspace.
+#
+# 【本预设唯一的**有意差异**（相对随包 standard）】2026-09-18：
+# 这行原来与 standard 逐字相同（通用编码人格），于是本预设只是"改了名字的 standard"——
+# 用户提问"我们的预设和标准模式有啥区别？"时，diff 给出的答案是"0 行差异"。
+# 工具/技能按预设隔离在这版 DSH 上做不到（切换预设时 agent 已存在 ⇒ `agent/created` 钩子不触发；
+# 技能注册表在父层读 ⇒ 子层注册看不见；见 docs/03 最新条目），所以**预设能可靠交付的只有人格**。
+# 改这行必须同步更新 scripts/check-preset.mjs 顶部的 INTENTIONAL 白名单（否则门禁会报配置漂移）。
+- id: persona
+  name: '@deepseek-ai/dsh-persona'
+  config:
+    suffix: Your working directory is {{cwd}}.
+    prefix: >-
+      You are the presentation engineer of PPT Studio, powered by the {{model}} model.
+      You treat a deck as an engineered deliverable, not a pile of slides: settle the outline and the
+      one claim each page makes before choosing any layout; put a conclusion in the title and evidence
+      in the body; give every number and chart a stated source and keep the same metric consistent
+      across pages; and run the deck through the gates (render, numeric verify, visual spot-check)
+      before showing it. The ppt_* tools, the /ppt commands and the PPT Studio skill manuals are your
+      working set — reach for them instead of hand-rolling artifacts.
+      If the human's request is clearly unrelated to decks, answer it normally without forcing this workflow.
+
+- id: agent-instructions
+  name: '@deepseek-ai/dsh-agent-instructions'
+  config:
+    maxBytes: 65536
+
+# ── shell ───────────────────────────────────────────────────────────────────
+
+# `shell-env` stays in the HOST composition: `apps/cli/src/web.ts` injects it to
+# publish `DSH_WEB_URL`/`DSH_WEB_MODE`, and a host row that injects a service is
+# the criterion for host-plane ownership — injection resolves before any session
+# exists, so there is no agent to key by. Behind a preset realm those variables
+# never reached the model's shell at all. Both shell tools consume the host
+# registry from here; their executors (`bash-sandbox`/`pwsh-sandbox`) are
+# host-plane too.
+- id: tool-bash
+  name: '@deepseek-ai/dsh-tool-bash'
+  disabled: !!js process.platform === 'win32'
+
+- id: tool-pwsh
+  name: '@deepseek-ai/dsh-tool-pwsh'
+  disabled: !!js process.platform !== 'win32'
+
+# ── filesystem ──────────────────────────────────────────────────────────────
+
+# Both register into the host `tools` registry and provide nothing, so
+# they need no realm. The `fs` service and its policy stay in the host.
+- id: tool-fs
+  name: '@deepseek-ai/dsh-tool-fs'
+
+- id: tool-fs-search
+  name: '@deepseek-ai/dsh-tool-fs-search'
+  config:
+    sampleOverCapGlobResults: false
+
+# ── background jobs ────────────────────────────────────────────────────────
+
+# Only the model-facing controls. The task REGISTRY stays on the host plane:
+# its producers sit outside any realm this file could put it in — `tool-bash`
+# above resolves it with `ctx.get`, and an entry-local realm here is invisible
+# to every sibling row, so `run_in_background` would answer "background jobs
+# unavailable" while these controls sat in the catalog. The registry is keyed by
+# owning agent anyway, so one host instance serves every session. What a preset
+# chooses is whether its agent can collect and stop background work at all.
+- id: tool-jobs
+  name: '@deepseek-ai/dsh-tool-jobs'
+
+# ── skills ──────────────────────────────────────────────────────────────────
+
+# The skill REGISTRY lives in the host composition and is layered per scope:
+# these rows register into THIS preset's layer of it, so they need no realm.
+# `skill-filesystem` contributes local-root discovery for agents on this preset, and
+# `tool-skill` gives them the catalog and loader; the merged catalog also
+# carries whatever the deployment registered globally (repository plugins).
+- id: skill-filesystem
+  name: '@deepseek-ai/dsh-skill-filesystem'
+
+- id: tool-skill
+  name: '@deepseek-ai/dsh-tool-skill'
+
+# ── 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'
+
+- id: tool-goal
+  name: '@deepseek-ai/dsh-tool-goal'
+
+# ── plan mode ───────────────────────────────────────────────────────────────
+
+# Plan state is per-agent by nature, so an entry-local realm is not a
+# workaround here — it is the correct lifetime.
+- id: planning
+  name: cordis:group
+  group: true
+  isolate:
+    planMode: true
+  config:
+    - id: plan-mode
+      name: '@deepseek-ai/dsh-plan-mode'
+      config:
+        section: |
+              You are in plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
+
+              Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan. Prefer existing functions and patterns over new machinery.
+
+              The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
+
+              Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
+
+              Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
+
+              When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
+
+# ── compaction ──────────────────────────────────────────────────────────────
+
+# `compaction-basic` reads `toolResultPrune` through `ctx.get`, so the pruner must
+# share this realm rather than sit outside it.
+#
+# `tokenMeter` is deliberately NOT in this realm: the meter stays on the HOST
+# plane, and the rows here resolve that one instance. It takes no configuration,
+# keys every fold by Session, and owns the context-meter projection units the
+# browser reads for every session — behind a realm those units would come and go
+# with whichever presets happen to be mounted. What a preset chooses is whether
+# its agent compacts at all, which is `compaction-basic` below.
+- id: compaction
+  name: cordis:group
+  group: true
+  isolate:
+    compaction: true
+    toolResultPruner: true
+  config:
+    - id: compaction-basic
+      name: '@deepseek-ai/dsh-compaction-basic'
+
+    - id: command-compact
+      name: '@deepseek-ai/dsh-command-compact'
+
+    - id: tool-result-pruner
+      name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
+      config:
+        thresholdChars: 8192
+        headChars: 4096
+        tailChars: 1024
+
+# ── delegation and workflows ────────────────────────────────────────────────
+
+# The `subagents` registry and its spawn/fork backends live in the HOST
+# composition: the registry is a process singleton whose cross-session queries
+# the api-proxy serves to the browser, and a provider name may only be
+# registered once. This preset contributes the delegation TOOLS, which resolve
+# that host registry.
+#
+# `workflows` is different — nothing outside an agent reads it — so every row
+# that reaches it shares one entry-local realm here, and a consumer left
+# outside would resolve a host registry this preset does not populate.
+- 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
+
+    # 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; parent and child inherit the same messaging tool,
+    # while the parent id and return guidance follow the inherited history.
+    - id: tool-subagent-fork
+      name: '@deepseek-ai/dsh-tool-subagent'
+      config:
+        provider: fork
+        toolName: subagent_fork
+        backgroundMode: continuable
+
+    # Production dsh does not install these optional providers. Install the
+    # matching Bundle in this Profile and restart the Host, then copy this
+    # preset and remove `disabled` from the matching tool row. Host availability
+    # alone grants no tool.
+    - id: tool-subagent-codex
+      name: '@deepseek-ai/dsh-tool-subagent'
+      disabled: true
+      config:
+        provider: codex
+        toolName: subagent_codex
+        backgroundMode: one-shot
+        maxDepth: provider-managed
+
+    - id: tool-subagent-claude-code
+      name: '@deepseek-ai/dsh-tool-subagent'
+      disabled: true
+      config:
+        provider: claude-code
+        toolName: subagent_claude_code
+        backgroundMode: one-shot
+        maxDepth: provider-managed
+
+    - id: workflow-ptc
+      name: '@deepseek-ai/dsh-workflow-ptc'
+      config:
+        provider: spawn
+
+    - id: tool-workflow
+      name: '@deepseek-ai/dsh-tool-workflow'
+
+    # Off by default with the base row it mirrors: the tool description
+    # restricts `ralph` to runs the human explicitly asked for, and completion
+    # is a worker self-report, not an independent evaluation. Preset files take
+    # no patches, so a session that wants it duplicates this preset under a new
+    # id and drops `disabled`; the shipped root shadows a copy that reuses this
+    # id.
+    - id: tool-ralph
+      name: '@deepseek-ai/dsh-tool-ralph'
+      disabled: true
+      config:
+        subagentProvider: spawn
+        maxRounds: 64
+
+# ── remaining model-facing rows ─────────────────────────────────────────────
+
+- id: tool-ask-user
+  name: '@deepseek-ai/dsh-tool-ask-user'
+
+- id: tool-todo
+  name: '@deepseek-ai/dsh-tool-todo'
+  config:
+    allowParallelInProgress: true
+
+# The `web` service and its search provider stay in the host composition; only
+# the model-facing tool is per-session.
+- id: tool-web
+  name: '@deepseek-ai/dsh-tool-web'
+  config:
+    fetch: true
+    searchTimeoutMs: 60000
+
+- id: present
+  name: '@deepseek-ai/dsh-tool-present'
+
+- id: tool-plugin-manager
+  name: '@deepseek-ai/dsh-plugin-manager/tools'
+  disabled: true
+
+# ── 为什么这里**没有**本插件的插件行（2026-09-24 按 DSH 0.1.7 重写说明）──────────────
+# 本文件是「PPT 工作室」预设的组合真相：装配时由 lib/preset-delivery.js 声明给 agentPresets 注册表。
+# **里面不放本插件的插件行**——插件已经由 profile bundle（cordis.patch.yml）挂载过；这里再来一行
+# 会在同一进程把它挂第二次（预设组合里那一次注册进**预设作用域**，与 profile 那一次重复）。
+# 插件自身有装配防重，但纪律是"一处挂载"，所以随包预设恒为"干净组合"。
+#
+# 曾经验证过两条**都走不通**的路（留档，别再试）：
+#   ① 用**裸包名** `dsh-ppt-studio` 写一行（0.1.6 实测事故）：预设的行由注册表在**它自己 ctx 的
+#      baseUrl** 下 mount（源码 `mountPreset(scope.ctx.extend({ baseUrl: record.context.baseUrl }), …)`，
+#      而 `register()` 里 `context = this.ctx`）——那是 `dsh-web-app` 的包目录，**不是** profile、
+#      也不是预设目录 ⇒ 解析不到 ⇒ 预设被判 `broken` ⇒ 前端选择器只渲染健康预设
+#      （`presetOptions() = presets.filter(p => p.broken === void 0)`）⇒ 用户根本选不到；
+#   ② 把插件行写成**相对路径**（0.1.6 的 `--isolate` 就是这么做，靠预设目录内的 junction 解析）：
+#      0.1.7 上预设目录**不再被扫描**、"组合文件所在目录"这个概念随之消失 ⇒ 同样解析不到。
+# 结论：**默认（全局）装法**是本版本唯一受支持的装配路径（`scripts/install.mjs` 的默认分支，
+# 也是 `dsh plugin add` 那一条）。真要"只在「PPT 工作室」里生效"，得把插件行放进**预设声明本身**
+# 并给它一个安装期算出的**绝对 `file://` 名字**——这块尚未实现，`--isolate` 会明确拒绝而不是静默失败。

package/agent-presets/ppt/preset.yml

@@ -0,0 +1,3 @@
+name: PPT 工作室
+description: 专业 PPT 制作工作区：四类任务（从头/补完/修改/总结）+ 设计意图声明制防元素冲突 + 数字门禁/视觉审阅/Office 真渲染三轨审核 + PPTD 中间层与内置模板库；支持在既有精美 PPT 上只改一页（splice/slice 保真交付，其余页逐字节不动）。
+order: 2

package/cordis.patch.yml

@@ -0,0 +1,29 @@
+# DSH profile bundle patch —— 「PPT 工作室」插件行（package.json 的 dsh.bundle.patch 指向本文件）
+#
+# 安装（一条命令，不需要 npm 账号）：
+#     dsh plugin --profile web add dsh-ppt-studio                     # npm（2026-09-18 起，推荐：短、可升级）
+#     dsh plugin --profile web add https://github.com/zbsph/dsh-ppt-studio/releases/download/<tag>/<资产名>.tgz   # 离线/归档通道
+# `dsh plugin` 会在 profile 目录里跑 pnpm，然后核对 package.json 的 dsh.profile.bundles：
+# **声明了 dsh.bundle.patch 的依赖自动入栈**（本文件即由 package.json 的 dsh.bundle.patch 指向）。
+#
+# 装配模型（2026-09-18 最终态 = **装上即可用**，见 docs/02 §2.1 与 docs/03 当日记录）：
+#   · 本行 = 把插件挂进 **profile 层**；插件在 `apply()` 里向**拿到手的那个 ctx** 注册全部能力面
+#     （22 个 ppt_* 工具 / `/ppt` 命令面 / `ppt_state` / 4 本内嵌技能 / 工作流提示段）⇒ 该 profile 的
+#     **每个会话**都能用（含官方 standard）。
+#   · 想要"只在「PPT 工作室」预设里生效"的用户：本版本**不支持**（`install.mjs --isolate` 会明确拒绝）。
+#     0.1.6 时代靠"预设目录内的 junction + 相对路径行"实现，而 0.1.7 删掉了目录发现、
+#     预设行改为在**注册表所在层**的 baseUrl 下解析 ⇒ 相对行与裸包名都解析不到 ⇒ 预设被判 broken。
+#     详见 agent-presets/ppt/agent.cordis.yml 末尾与 scripts/install.mjs 顶部。
+#   · 曾经的"按 agent 预设门控"设计（`agent/created` 钩子 + 预设层注册）已**证伪并撤除**：空白会话切预设时
+#     agent 已存在、钩子不会为它触发（先建会话再切 = 永远没工具），且技能注册表按层读、子层注册父层看不见。
+#     细节与实测见 docs/03（2026-09-18 三条撤回记录）与 src/index.js 顶部注释。
+#   · 预设本身由插件**声明**（2026-09-24 适配 0.1.7）：apply 时把包内 `agent-presets/ppt/` 的组合交给
+#     `ctx.agentPresets.register({id:'ppt', …})`，随插件同生共死（卸载即注销；`autoPreset: false` 可关闭）。
+#     0.1.6 及以前是"写到 `<dshHome>/.agent-presets/ppt/`"——那条发现路径在 0.1.7 已被上游整个删除。
+- insert:
+    - id: ppt-studio
+      name: 'dsh-ppt-studio'
+      config:
+        # 仅诊断用（插件日志打印 presetIds），**不再门控任何东西**——历史字段，保留以免改动既有装配行的形状
+        presetIds: ['ppt']
+        autoPreset: true