dsh-vibe-math 2.0.21 → 2.0.22

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-vibe-math",
   "description": "Multi-agent mathematical problem-solving & verification frameworks for DeepSeek Harness — THREE agent presets in one install: vibe-math-v2 (probability-driven: qs.json + Propos knowledge base + explorer→solver→review/debate verdict), vibe-math-v3 (THIRD-generation, recommended: paper-style Markdown knowledge base with Problems/Progress/Propos/Methods/Verified + planner-agent scheduling that decides the next N actions + universal theory/method invention library + agents write their own Markdown directly via a per-file write lock), and vibe-math-v4 (FOURTH-generation: persistent self-organizing resident subagents that message & meet to decide all tasks, verify only by unanimous consensus, /compact at a context threshold, and stop only when all agree the problem is solved). Installing this bundle auto-installs all three presets (v1 was removed at v2.0.0).",
-  "version": "2.0.21",
+  "version": "2.0.22",
   "type": "module",
   "engines": {
     "node": "^22.19.0 || >=24.0.0"
@@ -15,6 +15,7 @@
   "files": [
     "installer.js",
     "cordis.patch.yml",
+    "RELEASE-NOTES-2.0.22.md",
     "vibe-math-v2/agent.cordis.yml",
     "vibe-math-v2/preset.yml",
     "vibe-math-v2/vibe-math-v2.js",
@@ -56,13 +57,18 @@
       "patch": "./cordis.patch.yml"
     },
     "minVersion": "0.1.2-rc.1",
-    "testedVersion": "0.1.2-rc.1",
-    "compatNote": "依赖宿主提供的 subagents/agents/tools/commands/fs 服务与 @deepseek-ai/dsh-* 插件行。本项目已充分测试并确认适配 dsh-v0.1.2-rc.1（v2/v3/v4；v1 已于 v2.0.0 移除）。注意：DSH 0.1.2 起 subagents.startContinuable 的 agentOptions/toolFilter 需要宿主 provider 声明对应 capability（spawn/fork 进程内 provider 均支持），安装器启动时会做能力自检并在旧版宿主上告警。",
+    "testedVersion": "0.1.5-rc.2",
+    "compatNote": "依赖宿主提供的 subagents/agents/tools/commands/fs 服务与 @deepseek-ai/dsh-* 插件行；可选 subprocess/sandboxPolicy/compaction。persona 行同时携带 prefix 与 text 两个键，以兼容 0.1.3-alpha.2 的 schema 更名（prefix 必填）与 0.1.2 及更早的 text 键。已在 dsh-v0.1.5-rc.2（@deepseek-ai/dsh-persona 0.1.5-rc.2）上逐行校验全部预设行并通过（v2/v3/v4；v1 已于 v2.0.0 移除）。注意：DSH 0.1.2 起 subagents.startContinuable 的 agentOptions/toolFilter 需要宿主 provider 声明对应 capability（spawn/fork 进程内 provider 均支持），安装器启动时会做能力自检并在旧版宿主上告警。2026 兼容性修复：v2/v3 工具权限名表原先硬编码 web/fetch/bash（未注册名会使 tools.restrict() 抛错、子代理无法建立），现按真实注册名并加带守卫的重试；v4 真实 /compact 原先在 subagent/end 里查 agents.get()（该事件触发时子代理已移出注册表，属死代码），现改为在 subagent/start 捕获 Agent 引用；三套预设的可选服务改为惰性读取，不再在 apply() 快照；v4 的 tools/commands 注册补入 ctx.effect；安装器自检新增 subprocess/sandboxPolicy/compaction。",
     "compatibility": {
       "dshReleases": {
         "0.1.2-alpha.4": "compatible",
         "0.1.2-alpha.5": "compatible",
-        "0.1.2-rc.1": "compatible"
+        "0.1.2-rc.1": "compatible",
+        "0.1.3-alpha.2": "compatible",
+        "0.1.5-alpha.1": "compatible",
+        "0.1.5-alpha.2": "compatible",
+        "0.1.5-rc.1": "compatible",
+        "0.1.5-rc.2": "compatible"
       }
     }
   }

package/vibe-math-v2/agent.cordis.yml

@@ -1,212 +1,256 @@
-# The `vibe-math-v2` agent preset: the full coding agent (`standard`), plus the
-# NEW-architecture multi-agent mathematical problem-solving & verification
-# framework (see 新架构-vibe-math-实现方案.md).
-#
-# The vibe-math-v2 plugin row consumes the HOST subagents/agents/fs/tools/commands
-# services and publishes nothing, so it needs no isolate realm.
-
-# ── identity ────────────────────────────────────────────────────────────────
-
-- id: persona
-  name: '@deepseek-ai/dsh-persona'
-  config:
-    text: |-
-      You are a coding agent powered by the {{model}} model. Your working directory is {{cwd}}.
-
-      ## Vibe Math V2 toolkit
-
-      This session includes the "Vibe Math V2" multi-agent mathematical problem-solving and
-      verification framework (NEW architecture). It is driven by a background scheduler (code),
-      NOT by the model: you only issue the control tools below and read status; the scheduler
-      programmatically runs explorer (direction setting) → per-direction solvers (agent_self_iteration)
-      → multi-reviewer independent review → debate → verdict, and promotes/updates data itself.
-
-      - vibe_math_add_problem {id, description, priority} — add a problem to qs/qs.json.
-      - vibe_math_add_proposition {id, 概述, 布尔估计, 优先级, 价值/关键性} — add a proposition to Propos/.
-      - vibe_math_list_propositions — list the proposition knowledge base (summary index).
-      - vibe_math_start / vibe_math_resume — start / resume the scheduler (resume = continue after a checkpoint or restart).
-      - vibe_math_status / vibe_math_report — read scheduler status / full progress report (report also writes Progress_Logs/report.json).
-      - vibe_math_pause / vibe_math_abort — pause / abort (abort interrupts all children).
-      - vibe_math_set_mode {mode: manual|auto} — switch manual / auto control.
-      - vibe_math_set_params {...} — tune any parameter (see vibe_math_setup for the full schema; e.g. reportMode file|push|both, promoteValueThreshold, verdictMode flat|forced).
-      - vibe_math_setup / vibe_math_save_settings / vibe_math_template — guided configuration / persist defaults / generate template.
-      - vibe_math_new_project / vibe_math_set_project / vibe_math_list_projects — per-project folders.
-      - vibe_math_list_decisions / vibe_math_decide {id, action: approve|reject|override, verdict?} — resolve manual decisions.
-      - vibe_math_list_agents / vibe_math_message_agent / vibe_math_interrupt_agent — inspect / steer / interrupt subagents.
-
-      A /vibe slash command mirrors the main controls. Data lives under {{cwd}}/VibeMath/Projects/<project>/
-      (qs/qs.json, Propos/<分类>_Propos.json, Reliable/, Verified/, Verification_logs/, Progress_Logs/, VibeMath_State/)
-      and survives restarts via vibe_math_resume.
-
-      Key rules to remember when reporting: a problem is "solved" when one of its solutions reaches
-      正确概率 = 1; a proposition reaches 布尔估计 = 1/0 when a proof/refutation in its lists reaches
-      正确概率 = 1; Propos propositions with 价值/关键性 ≥ promoteValueThreshold auto-promote to qs.json.
-      When the user asks about progress, call vibe_math_report and summarize in plain language.
-
-      Configuration highlights (all tunable via vibe_math_set_params / the settings file):
-      `knowledgeContext` overrides the shared data-model explanation injected into every child prompt
-      (empty = built-in full version); `explorerPersona` / `solverPersona` / `verifierPersona` prepend
-      role instructions; `solverAllowNetwork` / `verifierAllowNetwork` / `solverAllowScripts` /
-      `verifierAllowScripts` toggle network / script tools (empty = inherit, true = allow, false = deny);
-      `directionsPerSolver` = how many directions each solver's prompt includes (1 = own direction only).
-      Data behaviors: an auto-promoted proposition becomes the problem "判断下述命题是否成立：<命题>"
-      with its proofs/refutations transferred into the solution list (verification results sync back to the
-      source proposition); a solver-reported sub-question q_sub registers THREE objects — the q_sub problem,
-      the temporary-assumption proposition p_{q-tmp}, and the problem "判断下述命题是否成立：p_{q-tmp}".
-
-- id: agent-instructions
-  name: '@deepseek-ai/dsh-agent-instructions'
-  config:
-    maxBytes: 65536
-
-# ── shell ───────────────────────────────────────────────────────────────────
-
-- 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 ──────────────────────────────────────────────────────────────
-
-- 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 ────────────────────────────────────────────────────────
-
-- id: tool-jobs
-  name: '@deepseek-ai/dsh-tool-jobs'
-
-# ── skills ──────────────────────────────────────────────────────────────────
-
-- id: skill-filesystem
-  name: '@deepseek-ai/dsh-skill-filesystem'
-
-- id: tool-skill
-  name: '@deepseek-ai/dsh-tool-skill'
-
-# ── goals ───────────────────────────────────────────────────────────────────
-
-- id: tool-goal
-  name: '@deepseek-ai/dsh-tool-goal'
-
-# ── plan mode ───────────────────────────────────────────────────────────────
-
-- 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 ──────────────────────────────────────────────────────────────
-
-- 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 ────────────────────────────────────────────────
-
-- 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
-        backgroundMode: continuable
-
-    - id: tool-subagent-fork
-      name: '@deepseek-ai/dsh-tool-subagent'
-      config:
-        provider: fork
-        toolName: subagent_fork
-        backgroundMode: continuable
-
-    - id: workflow-worker-thread
-      name: '@deepseek-ai/dsh-workflow-worker-thread'
-      config:
-        provider: spawn
-
-    - id: tool-workflow
-      name: '@deepseek-ai/dsh-tool-workflow'
-
-    - 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
-
-- id: tool-web
-  name: '@deepseek-ai/dsh-tool-web'
-  config:
-    fetch: false
-    searchTimeoutMs: 60000
-
-# ── Vibe Math V2 ────────────────────────────────────────────────────────────
-
-# The NEW-architecture framework: a preset-local plugin (./vibe-math-v2.js)
-# that registers the vibe_math_* tools, a /vibe slash command, and a background
-# scheduler (explorer → per-direction solvers → multi-reviewer verification).
-# It consumes the HOST subagents/agents/fs/tools/commands services and provides
-# nothing, so it sits loose (no isolate realm).
-- id: vibe-math-v2
-  name: './vibe-math-v2.js'
+# The `vibe-math-v2` agent preset: the full coding agent (`standard`), plus the
+# NEW-architecture multi-agent mathematical problem-solving & verification
+# framework (see 新架构-vibe-math-实现方案.md).
+#
+# The vibe-math-v2 plugin row consumes the HOST subagents/agents/fs/tools/commands
+# services and publishes nothing, so it needs no isolate realm.
+
+# ── identity ────────────────────────────────────────────────────────────────
+
+- id: persona
+  name: '@deepseek-ai/dsh-persona'
+  config:
+    prefix: |-
+      You are a coding agent powered by the {{model}} model.
+
+      ## Vibe Math V2 toolkit
+
+      This session includes the "Vibe Math V2" multi-agent mathematical problem-solving and
+      verification framework (NEW architecture). It is driven by a background scheduler (code),
+      NOT by the model: you only issue the control tools below and read status; the scheduler
+      programmatically runs explorer (direction setting) → per-direction solvers (agent_self_iteration)
+      → multi-reviewer independent review → debate → verdict, and promotes/updates data itself.
+
+      - vibe_math_add_problem {id, description, priority} — add a problem to qs/qs.json.
+      - vibe_math_add_proposition {id, 概述, 布尔估计, 优先级, 价值/关键性} — add a proposition to Propos/.
+      - vibe_math_list_propositions — list the proposition knowledge base (summary index).
+      - vibe_math_start / vibe_math_resume — start / resume the scheduler (resume = continue after a checkpoint or restart).
+      - vibe_math_status / vibe_math_report — read scheduler status / full progress report (report also writes Progress_Logs/report.json).
+      - vibe_math_pause / vibe_math_abort — pause / abort (abort interrupts all children).
+      - vibe_math_set_mode {mode: manual|auto} — switch manual / auto control.
+      - vibe_math_set_params {...} — tune any parameter (see vibe_math_setup for the full schema; e.g. reportMode file|push|both, promoteValueThreshold, verdictMode flat|forced).
+      - vibe_math_setup / vibe_math_save_settings / vibe_math_template — guided configuration / persist defaults / generate template.
+      - vibe_math_new_project / vibe_math_set_project / vibe_math_list_projects — per-project folders.
+      - vibe_math_list_decisions / vibe_math_decide {id, action: approve|reject|override, verdict?} — resolve manual decisions.
+      - vibe_math_list_agents / vibe_math_message_agent / vibe_math_interrupt_agent — inspect / steer / interrupt subagents.
+
+      A /vibe slash command mirrors the main controls. Data lives under {{cwd}}/VibeMath/Projects/<project>/
+      (qs/qs.json, Propos/<分类>_Propos.json, Reliable/, Verified/, Verification_logs/, Progress_Logs/, VibeMath_State/)
+      and survives restarts via vibe_math_resume.
+
+      Key rules to remember when reporting: a problem is "solved" when one of its solutions reaches
+      正确概率 = 1; a proposition reaches 布尔估计 = 1/0 when a proof/refutation in its lists reaches
+      正确概率 = 1; Propos propositions with 价值/关键性 ≥ promoteValueThreshold auto-promote to qs.json.
+      When the user asks about progress, call vibe_math_report and summarize in plain language.
+
+      Configuration highlights (all tunable via vibe_math_set_params / the settings file):
+      `knowledgeContext` overrides the shared data-model explanation injected into every child prompt
+      (empty = built-in full version); `explorerPersona` / `solverPersona` / `verifierPersona` prepend
+      role instructions; `solverAllowNetwork` / `verifierAllowNetwork` / `solverAllowScripts` /
+      `verifierAllowScripts` toggle network / script tools (empty = inherit, true = allow, false = deny);
+      `directionsPerSolver` = how many directions each solver's prompt includes (1 = own direction only).
+      Data behaviors: an auto-promoted proposition becomes the problem "判断下述命题是否成立：<命题>"
+      with its proofs/refutations transferred into the solution list (verification results sync back to the
+      source proposition); a solver-reported sub-question q_sub registers THREE objects — the q_sub problem,
+      the temporary-assumption proposition p_{q-tmp}, and the problem "判断下述命题是否成立：p_{q-tmp}".
+    suffix: Your working directory is {{cwd}}.
+    text: |-
+      You are a coding agent powered by the {{model}} model. Your working directory is {{cwd}}.
+
+      ## Vibe Math V2 toolkit
+
+      This session includes the "Vibe Math V2" multi-agent mathematical problem-solving and
+      verification framework (NEW architecture). It is driven by a background scheduler (code),
+      NOT by the model: you only issue the control tools below and read status; the scheduler
+      programmatically runs explorer (direction setting) → per-direction solvers (agent_self_iteration)
+      → multi-reviewer independent review → debate → verdict, and promotes/updates data itself.
+
+      - vibe_math_add_problem {id, description, priority} — add a problem to qs/qs.json.
+      - vibe_math_add_proposition {id, 概述, 布尔估计, 优先级, 价值/关键性} — add a proposition to Propos/.
+      - vibe_math_list_propositions — list the proposition knowledge base (summary index).
+      - vibe_math_start / vibe_math_resume — start / resume the scheduler (resume = continue after a checkpoint or restart).
+      - vibe_math_status / vibe_math_report — read scheduler status / full progress report (report also writes Progress_Logs/report.json).
+      - vibe_math_pause / vibe_math_abort — pause / abort (abort interrupts all children).
+      - vibe_math_set_mode {mode: manual|auto} — switch manual / auto control.
+      - vibe_math_set_params {...} — tune any parameter (see vibe_math_setup for the full schema; e.g. reportMode file|push|both, promoteValueThreshold, verdictMode flat|forced).
+      - vibe_math_setup / vibe_math_save_settings / vibe_math_template — guided configuration / persist defaults / generate template.
+      - vibe_math_new_project / vibe_math_set_project / vibe_math_list_projects — per-project folders.
+      - vibe_math_list_decisions / vibe_math_decide {id, action: approve|reject|override, verdict?} — resolve manual decisions.
+      - vibe_math_list_agents / vibe_math_message_agent / vibe_math_interrupt_agent — inspect / steer / interrupt subagents.
+
+      A /vibe slash command mirrors the main controls. Data lives under {{cwd}}/VibeMath/Projects/<project>/
+      (qs/qs.json, Propos/<分类>_Propos.json, Reliable/, Verified/, Verification_logs/, Progress_Logs/, VibeMath_State/)
+      and survives restarts via vibe_math_resume.
+
+      Key rules to remember when reporting: a problem is "solved" when one of its solutions reaches
+      正确概率 = 1; a proposition reaches 布尔估计 = 1/0 when a proof/refutation in its lists reaches
+      正确概率 = 1; Propos propositions with 价值/关键性 ≥ promoteValueThreshold auto-promote to qs.json.
+      When the user asks about progress, call vibe_math_report and summarize in plain language.
+
+      Configuration highlights (all tunable via vibe_math_set_params / the settings file):
+      `knowledgeContext` overrides the shared data-model explanation injected into every child prompt
+      (empty = built-in full version); `explorerPersona` / `solverPersona` / `verifierPersona` prepend
+      role instructions; `solverAllowNetwork` / `verifierAllowNetwork` / `solverAllowScripts` /
+      `verifierAllowScripts` toggle network / script tools (empty = inherit, true = allow, false = deny);
+      `directionsPerSolver` = how many directions each solver's prompt includes (1 = own direction only).
+      Data behaviors: an auto-promoted proposition becomes the problem "判断下述命题是否成立：<命题>"
+      with its proofs/refutations transferred into the solution list (verification results sync back to the
+      source proposition); a solver-reported sub-question q_sub registers THREE objects — the q_sub problem,
+      the temporary-assumption proposition p_{q-tmp}, and the problem "判断下述命题是否成立：p_{q-tmp}".
+
+- id: agent-instructions
+  name: '@deepseek-ai/dsh-agent-instructions'
+  config:
+    maxBytes: 65536
+
+# ── shell ───────────────────────────────────────────────────────────────────
+
+- 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 ──────────────────────────────────────────────────────────────
+
+- 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 ────────────────────────────────────────────────────────
+
+- id: tool-jobs
+  name: '@deepseek-ai/dsh-tool-jobs'
+
+# ── skills ──────────────────────────────────────────────────────────────────
+
+- id: skill-filesystem
+  name: '@deepseek-ai/dsh-skill-filesystem'
+
+- id: tool-skill
+  name: '@deepseek-ai/dsh-tool-skill'
+
+# ── goals ───────────────────────────────────────────────────────────────────
+
+- id: tool-goal
+  name: '@deepseek-ai/dsh-tool-goal'
+
+# ── plan mode ───────────────────────────────────────────────────────────────
+
+- 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 ──────────────────────────────────────────────────────────────
+
+- 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 ────────────────────────────────────────────────
+
+- 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
+        backgroundMode: continuable
+
+    - id: tool-subagent-fork
+      name: '@deepseek-ai/dsh-tool-subagent'
+      config:
+        provider: fork
+        toolName: subagent_fork
+        backgroundMode: continuable
+
+    - id: workflow-worker-thread
+      name: '@deepseek-ai/dsh-workflow-worker-thread'
+      config:
+        provider: spawn
+
+    - id: tool-workflow
+      name: '@deepseek-ai/dsh-tool-workflow'
+
+    - 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
+
+- id: tool-web
+  name: '@deepseek-ai/dsh-tool-web'
+  config:
+    fetch: false
+    searchTimeoutMs: 60000
+
+# ── Vibe Math V2 ────────────────────────────────────────────────────────────
+
+# The NEW-architecture framework: a preset-local plugin (./vibe-math-v2.js)
+# that registers the vibe_math_* tools, a /vibe slash command, and a background
+# scheduler (explorer → per-direction solvers → multi-reviewer verification).
+# It consumes the HOST subagents/agents/fs/tools/commands services and provides
+# nothing, so it sits loose (no isolate realm).
+- id: vibe-math-v2
+  name: './vibe-math-v2.js'

package/vibe-math-v2/preset.yml

@@ -1,2 +1,2 @@
-name: Vibe Math V2
-description: 多代理数学问题求解与验证框架（新架构）：概率驱动调度 —— qs.json 问题清单 + Propos/ 命题库 + Reliable/ 参考文献，explorer 拆方向 → 逐方向 Solver 迭代 → 多验证器独立审查→辩论→裁决；断点续跑、人工/自动干预、file/push 双模式进度汇报。
+name: Vibe Math V2
+description: 多代理数学问题求解与验证框架（新架构）：概率驱动调度 —— qs.json 问题清单 + Propos/ 命题库 + Reliable/ 参考文献，explorer 拆方向 → 逐方向 Solver 迭代 → 多验证器独立审查→辩论→裁决；断点续跑、人工/自动干预、file/push 双模式进度汇报。