@stardustlc/dsh-suite 0.1.10 → 0.2.0

package/README.en.md

@@ -10,7 +10,7 @@ Bundles five product lines — office flow (with dream-based memory), media stud
 
 ## Compatibility
 
-Verified against official `@deepseek-ai/dsh@0.1.5-rc.1` and Node `24.16.0` on 2026-09-11: 18 components plus separately installed Modlens register 97 host tools and 34 skills. All component tool schemas and both PTC SDK generators pass; Minimal PTC mounts in a real agent and exposes `run_code` to the model. Isolated Web startup, token authentication (303/401/200) and process shutdown pass. Requires Node 22.19 or later within 22.x, or 24 or later. The scripts below reproduce these checks; offline tests do not establish live external-service readiness.
+Version 0.2.0 requires Harness 0.1.7 or later; the current tested baseline is official-source **0.1.7-alpha.2**, with a local `Symbol.for` tool-scheduler fix. All 18 plugins register 96 tools and 34 skills; the Minimal PTC preset mounts in a real agent and appears in the mode picker. Settings migration, restart persistence, offline contracts and Web authentication are checked. Live external-service workflows need separate verification. Use suite 0.1.10 on Harness 0.1.5/0.1.6.
 
 ## Install / Uninstall
 
@@ -91,7 +91,7 @@ node scripts/smoke-harness.mjs --harness-root C:/path/to/deepseek-harness --inst
 
 Use `--install-tarballs` before release to test installation. The report must contain `{ "ok": true, "packages": [{ "name", "version", "tarball", "integrity" }] }` for the suite and all 18 components, with `sha512-...` integrity values. Only the temporary profile redirects those versions to local tarballs. The official CLI installs the suite; verification requires transitive component dependencies, no duplicate profile layers, successful startup, the complete registry and PTC mounting. Dependency installation can contact npm; this mode is not an offline test.
 
-Contracts use the selected Harness's real `ToolRuntime` and `SkillRegistry`: required service declarations, all parameter/output schemas, skill registrations and collisions, both PTC SDKs, and the execution/rendering of 16 health fixtures plus `ppt_themes`. The preset is materialized in an isolated home and its Harness module references are resolved. Startup verification also mounts it in a real agent, requiring `run_code` as the model entry point and retention of plugin tools and the shell. Only these read-only output samples are executed; other business workflows rely on the component unit tests and mocked dependencies.
+Contracts use the selected Harness's real `ToolRuntime` and `SkillRegistry`: required service declarations, all parameter/output schemas, skill registrations and collisions, both PTC SDKs, and the execution/rendering of 16 health fixtures plus `ppt_themes`. Legacy-host checks cover the retired directory format. On 0.1.7, startup verification checks declarative preset registration and module resolution. Startup verification also mounts it in a real agent, requiring `run_code` as the model entry point and retention of plugin tools and the shell. Only these read-only output samples are executed; other business workflows rely on the component unit tests and mocked dependencies.
 
 HyperFrames and Remotion also undergo a real registry regression: remove one registered skill and require unhealthy status, then restore the matching registration and require healthy status. The startup smoke check executes both health tools and requires all bundled skills to be active.
 

package/README.md

@@ -10,7 +10,7 @@
 
 ## 兼容性
 
-已在官方 `@deepseek-ai/dsh@0.1.5-rc.1`、Node `24.16.0` 上验证（2026-09-11）：18 个组件与额外安装的 Modlens 同载，宿主共注册 97 个工具、34 个技能。全部组件工具 schema 与两种 PTC SDK 生成检查通过；极简 PTC 已在真实 agent 中挂载，模型入口为 `run_code`。隔离 Web 启动、token 鉴权（303/401/200）与进程退出通过。Node 要求为 22.19 及以上的 22.x，或 24 及以上。下方脚本可重复验收；离线检查不代表外部服务业务已实测。
+0.2.0 需要 Harness 0.1.7 及以上，当前实测基线为官方源码构建的 **0.1.7-alpha.2**（含本地工具调度器 `Symbol.for` 修复）。18 个组件共同注册 96 个工具、34 个技能；极简 PTC 可在模式列表选择，并已在真实 Agent 挂载。配置迁移、重启持久化、离线契约和 Web 鉴权已验证。外部服务业务需单独验证；Harness 0.1.5/0.1.6 请使用套件 0.1.10。
 
 ## 安装
 
@@ -107,7 +107,7 @@ node scripts/smoke-harness.mjs --harness-root C:/path/to/deepseek-harness --inst
 
 发布前使用 `--install-tarballs` 验证真实安装：报告格式为 `{ "ok": true, "packages": [{ "name", "version", "tarball", "integrity" }] }`，须包含套件和 18 个组件，`integrity` 为 `sha512-...`。验证器只在临时 profile 中将指定版本映射到本地 tarball，经官方 CLI 安装套件，要求组件为传递依赖且不重复启用 profile 层，再检查实际启动、完整目录和 PTC 挂载。开发依赖可能访问 npm；这个安装模式不属于离线测试。
 
-契约检查使用指定 Harness 的真实 `ToolRuntime` 和 `SkillRegistry`：逐个校验服务注入声明、全部工具参数与输出 schema、技能注册和重名冲突，生成两种 PTC SDK，再通过宿主执行链运行 16 个 health 与 `ppt_themes` 输出样例。minimal-ptc 会物化到隔离目录，并校验预设引用的 Harness 模块可解析；启动验收还会创建真实 agent 挂载预设，确认模型入口为 `run_code` 且保留插件工具与 Shell。这里只覆盖这些只读样例的返回值；发信、合成、渲染等业务流程由组件测试中的模拟依赖验证。
+契约检查使用指定 Harness 的真实 `ToolRuntime` 和 `SkillRegistry`：逐个校验服务注入声明、全部工具参数与输出 schema、技能注册和重名冲突，生成两种 PTC SDK，再通过宿主执行链运行 16 个 health 与 `ppt_themes` 输出样例。旧宿主兼容测试会校验旧目录预设；0.1.7 启动验收检查声明式预设注册与模块解析，启动验收还会创建真实 agent 挂载预设，确认模型入口为 `run_code` 且保留插件工具与 Shell。这里只覆盖这些只读样例的返回值；发信、合成、渲染等业务流程由组件测试中的模拟依赖验证。
 
 HyperFrames 与 Remotion 另有真实注册表回归：卸载一个已注册技能，确认 health 报告异常，再恢复相同注册并确认 health 恢复正常。启动验收也会执行这两个 health，要求全部随包技能实际生效。
 

package/package.json

@@ -1,17 +1,21 @@
 {
   "name": "@stardustlc/dsh-suite",
-  "version": "0.1.10",
+  "version": "0.2.0",
   "description": "DSH 插件全家桶：18 个组件覆盖邮件、日历、媒体创作、开发运维、消息通知与极简 PTC，一条命令安装。",
   "type": "module",
   "dsh": {
     "bundle": {
-      "patch": "./cordis.patch.yml"
+      "patch": [
+        "./cordis.patch.yml",
+        "./ptc-minimal.patch.yml"
+      ]
     }
   },
   "files": [
     "cordis.patch.yml",
     "README.md",
-    "README.en.md"
+    "README.en.md",
+    "ptc-minimal.patch.yml"
   ],
   "scripts": {
     "test": "node --test \"test/*.test.mjs\"",
@@ -37,19 +41,19 @@
   "dependencies": {
     "@stardustlc/dsh-docker": "0.3.3",
     "@stardustlc/dsh-dream": "0.3.3",
-    "dsh-calendar": "0.8.2",
+    "dsh-calendar": "0.8.4",
     "dsh-cite": "0.3.3",
     "dsh-code-security": "0.3.3",
     "dsh-codex-port": "0.2.2",
     "dsh-dingtalk": "0.2.1",
-    "dsh-email": "0.13.1",
+    "dsh-email": "0.14.0",
     "dsh-ffmpeg": "0.4.3",
     "dsh-flakefinder": "0.3.3",
     "dsh-hyperframes": "0.3.2",
-    "dsh-minimal-ptc": "0.4.7",
-    "dsh-ppt": "0.4.3",
+    "dsh-minimal-ptc": "0.5.0",
+    "dsh-ppt": "0.4.4",
     "dsh-remotion": "0.3.2",
-    "dsh-rss": "0.3.2",
+    "dsh-rss": "0.4.0",
     "dsh-slack": "0.3.1",
     "dsh-sql": "0.4.3",
     "dsh-voice": "0.3.4"

package/ptc-minimal.patch.yml

@@ -0,0 +1,307 @@
+# Harness 0.1.7 declarative preset; generated from the bundled agent composition.
+- insert:
+    - id: preset-ptc-minimal
+      name: "@deepseek-ai/dsh-agent-preset"
+      config:
+        id: ptc-minimal
+        name: 极简 PTC 模式
+        description: 简洁提示词、完整插件工具与 PTC 编排；Windows 支持 Git Bash 和持久 PowerShell。
+        order: 4
+        plugins:
+          # The `ptc-minimal` agent preset: the `ptc` (PTC 模式) capabilities with the
+          # `minimal` (极简模式) prompt.
+          #
+          # Everything in `ptc` is here unchanged — full standard capabilities plus the
+          # PTC tool presentation (`tool-presentation` with `mode: ptc`), where the
+          # model composes a TypeScript program against a generated SDK and `run_code`
+          # executes it. What differs is the persona row, taken verbatim from `minimal`:
+          # a fixed one-line persona marked `complete: true` with
+          # `includeRuntimeContext: false`, so global identity, Web orientation, tool
+          # guidance, and later assembly listeners cannot add prompt text, and runtime
+          # context snapshots are suppressed. The `agent-instructions` row from `ptc` is
+          # dropped for the same reason — its workspace instruction baselines would add
+          # user-role text the minimal prompt policy excludes.
+          #
+          # This file is an AGENT-PLANE composition. It is mounted under one agent's
+          # scope context, so every tool it registers belongs to that session alone.
+          # A service row here MUST sit inside a group carrying an `isolate` realm.
+
+          # ── identity ────────────────────────────────────────────────────────────────
+
+          # The persona is the complete system prompt (minimal-mode prompt policy).
+          # dsh 0.1.3 renamed the persona config field `text` to `prefix` (required).
+          - id: persona
+            name: '@deepseek-ai/dsh-persona'
+            config:
+              prefix: You are a helpful software engineer assistant.
+              complete: true
+              includeRuntimeContext: false
+
+          # ── shell ───────────────────────────────────────────────────────────────────
+
+          # `shell-env` stays in the HOST composition: `apps/cli/src/web.ts` injects it to
+          # publish `DSH_WEB_URL`/`DSH_WEB_MODE`. Both shell tools consume the host
+          # registry from here; their executors 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: true
+
+          # Windows persistent PowerShell PTY stack (rc.1 minimal parity). Replaces the
+          # one-shot pwsh row on win32; the gitbash group below keeps a stateless bash
+          # tool beside it. The model-facing tool name remains `pwsh`.
+          - 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-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'
+                config:
+                  timeoutMs: 300000
+                  description: |-
+                    Run commands in a PowerShell shell
+                    * When invoking this tool, the contents of the "command" parameter does NOT need to be XML-escaped.
+                    * Network access depends on the host environment.
+                    * State is persistent across command calls and discussions with the user.
+                    * 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.
+
+          # Windows Git Bash shell stack. The preset-local executor runs every `bash`
+          # call through Git for Windows bash, keeping the model-facing tool name and
+          # stateless semantics identical to the POSIX `tool-bash` row above. Only
+          # mounted on win32; the POSIX host keeps the official bash runner.
+          - id: gitbash-shell
+            name: cordis:group
+            group: true
+            disabled: !!js process.platform !== 'win32'
+            isolate:
+              shell: true
+            config:
+              - id: gitbash-executor
+                name: dsh-minimal-ptc/gitbash-executor
+                config:
+                  # 留空：executor 自动探测 GIT_BASH → 常见安装目录 → PATH → 'bash'
+                  # 如需固定路径可显式写 shellPath: 'C:\\Program Files\\Git\\bin\\bash.exe'
+                  timeoutMs: 120000
+                  maxTimeoutMs: 600000
+                  maxOutputBytes: 64000
+                  maxSpillBytes: 67108864
+                  graceMs: 3000
+
+              - id: tool-bash-win
+                name: '@deepseek-ai/dsh-tool-bash'
+                config:
+                  enableRunInBackground: false
+
+          # ── 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.
+          - 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.
+          - id: skill-filesystem
+            name: '@deepseek-ai/dsh-skill-filesystem'
+
+          - id: tool-skill
+            name: '@deepseek-ai/dsh-tool-skill'
+
+          # ── goals ───────────────────────────────────────────────────────────────────
+
+          # Only the model-facing tool plus the human command. The goal SERVICE, its
+          # session driver stay on the host plane.
+          - 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` stays HOST-side.
+          - 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. This preset contributes the delegation TOOLS. `workflows` 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
+
+              - id: tool-subagent-fork
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: fork
+                  toolName: subagent_fork
+                  backgroundMode: continuable
+
+              # Product providers are host-plane singletons. Remove `disabled` from
+              # either ordinary tool row to expose that product to agents on this preset.
+              - 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'
+                # Keep the engine above for `ralph`, but do not publish a second
+                # model-authored orchestration surface beside `run_code` in PTC mode.
+                disabled: true
+
+              - id: tool-ralph
+                name: '@deepseek-ai/dsh-tool-ralph'
+                config:
+                  subagentProvider: spawn
+                  maxRounds: 64
+
+          # ── remaining model-facing rows ─────────────────────────────────────────────
+
+          - id: tool-ask-user
+            name: '@deepseek-ai/dsh-tool-ask-user'
+
+          - id: tool-todo
+            name: '@deepseek-ai/dsh-tool-todo'
+            config:
+              allowParallelInProgress: true
+
+          # The `web` service and its search provider stay in the host composition; only
+          # the model-facing tool is per-session.
+          - id: tool-web
+            name: '@deepseek-ai/dsh-tool-web'
+            config:
+              fetch: true
+              searchTimeoutMs: 60000
+
+          # ── presentation ────────────────────────────────────────────────────────────
+
+          # PTC for this agent alone. The row waits for the host's `ptcRuntime`
+          # rather than assuming it: a deployment that composes no TypeScript runtime
+          # fails this preset at mount, naming this id, instead of at the first request.
+          - id: tool-presentation
+            name: '@deepseek-ai/dsh-agent-tool-presentation'
+            config:
+              mode: ptc
+
+          # Official `ptc` parity rows (0.1.6): the deliverables presenter and the
+          # plugin-manager tools (off by default, mirroring the official preset).
+          - id: present
+            name: '@deepseek-ai/dsh-tool-present'
+
+          - id: tool-plugin-manager
+            name: '@deepseek-ai/dsh-plugin-manager/tools'
+            disabled: true