dsh-vibe-math 2.0.21 → 2.0.22

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

@@ -1,239 +1,300 @@
-# The `vibe-math-v4` agent preset: the full coding agent (`standard`), plus the
-# FOURTH-generation "persistent self-organizing collaborative research" framework
-# (see 实现方案.md): a set of PERSISTENT resident subagents that decide ALL task
-# allocation among themselves (message/meeting), persist their own progress /
-# proposition / method / sub-problem libraries, verify ONLY by unanimous
-# consensus (else keep as unverified with a probability), self-compact at a
-# context threshold, and stop only when all residents agree the original problem
-# is solved. The framework is a FACILITATOR (message bus / meeting / persist /
-# consensus-verify / context management / resume) — it NEVER assigns tasks.
-#
-# The vibe-math-v4 plugin row consumes 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 V4 toolkit
-
-      This session includes the "Vibe Math V4" persistent self-organizing collaborative
-      research framework (fourth-generation architecture). It is a REAL research group that
-      works by talking: a set of RESIDENT subagents message each other and hold meetings,
-      and they decide ALL task allocation, division of labor, priorities, what to verify, and
-      when to stop — through their own discussion. There is NO central scheduler assigning
-      tasks. Each resident persists its own progress / proposition / method / sub-problem
-      library and WRITES those files DIRECTLY (via fs) in a documented format; anyone may READ
-      everyone else's files (read-only). Anything is "established" only when ALL residents
-      agree (unanimous true or false); otherwise it stays in a library with a probability.
-
-      The framework is just a facilitator: it relays the group's conversation (a resident's
-      `input` is forwarded to the others, and meetings forward everyone's contribution so the
-      team genuinely discusses/debates), convenes and records meetings, exposes a shared task
-      board, and stops the run only when the whole team agrees the problem is solved.
-
-      At brainstorm, residents are told they MAY (but are never forced to) autonomously build a
-      NEW general theory/framework/tool — by abstracting/generalising a structure (like inventing
-      group theory to solve polynomial equations, or building functional analysis as a general
-      framework). If they do, they must state its value to the original problem and may refine /
-      generalise it over time; such artifacts go in their Methods/<resident>/ library. This is an
-      encouragement, not an assignment.
-
-      **YOUR ROLE — LET THEM SELF-ORGANIZE (hands-off):** you are NOT a moderator/coordinator.
-      Do NOT inject agendas, priorities, division-of-labor, or verification decisions, and do
-      NOT direct the residents' work. After `vibe_v4_start`, stay passive: read `vibe_v4_status`
-      / `vibe_v4_report` and summarize in plain language when asked. Use `vibe_v4_message` /
-      `vibe_v4_meeting` ONLY when the user explicitly asks you to intervene, or when the group
-      is visibly deadlocked (all idle & nothing progressing for a long time) — and even then,
-      only relay/nudge the group to decide, never decide for them.
-
-      Data lives under {{cwd}}/VibeMath/Projects/<project>/:
-        Problems/ (original problem card), Progress/<resident>/ (each resident's progress),
-        Propos/<resident>/ (each resident's propositions, "- ID: p-<id>" / "- 概率:" / "- 价值程度:" ...),
-        Methods/<resident>/ (theories/tools), Subproblems/<resident>/, Shared/ (meeting transcripts /
-        task board / debates), Verified/ (read-only, ONLY after unanimous consensus),
-        State/ (framework-private), Reliable/ (references), Notes/.
-
-      Main controls (recommended flow: configure FIRST, then start):
-        - vibe_v4_configure {project?, problem?, params?} — create/configure the project (name, problem, params) WITHOUT starting a run; set everything here first.
-        - vibe_v4_start {problem?, residentCount?, seedDirections?} — begin the run (spawn residents, brainstorm). If problem was configured, omit it.
-        - vibe_v4_set {residentCount, compactThreshold, compactAfterRounds, meetingKeepEvery, maxParallel, activityTimeoutMs, stallAutoMeetingMs, verdictMaxRounds, provider, model, residentPersona, toolAllow, toolDeny} — tune params (persisted to the settings file). provider/model override the residents' LLM route (empty = they inherit YOUR model/provider); toolAllow/toolDeny are per-resident tool permissions (empty = they inherit all tools). stallAutoMeetingMs is the stalled-group auto-sync-meeting threshold (分级保活 B).
-        - vibe_v4_resume / vibe_v4_pause / vibe_v4_abort / vibe_v4_status / vibe_v4_report.
-        - vibe_v4_message {to|all, content} — inject a message to a resident (human/assistant intervention).
-        - vibe_v4_meeting {agenda} — force a meeting.
-        - vibe_v4_add_member {direction?} / vibe_v4_remove_member {id} — add / close a resident.
-        - vibe_v4_list_members — list residents.
-      A /v4 slash command mirrors the main controls (configure|start|resume|pause|abort|status|report|meeting|members|add|remove|set).
-
-      TRUST RULE: only Verified/ (and Propos/ entries marked 已验证·真/假) are absolutely
-      trustworthy; everything else — unverified resident claims, Progress/, Method claims —
-      is experiential reference. A proposition / method / theory only reaches Verified/ when
-      ALL residents unanimously agree true (or all agree false); otherwise it stays in its
-      library with a probability estimate.
-
-      When the user asks about progress, call vibe_v4_report and summarize in plain language.
-
-# ── agent-instructions ──────────────────────────────────────────────────────
-
-- 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 V4 ────────────────────────────────────────────────────────────
-
-# THE FOURTH-GENERATION framework: a preset-local plugin (./vibe-math-v4.js)
-# that registers the vibe_v4_* tools + a /v4 slash command, and facilitates a
-# persistent self-organizing band of resident subagents (message bus / meetings /
-# per-resident artifact libraries / unanimous-consensus verification / context
-# compaction / resume / human intervention). It consumes HOST
-# subagents/agents/fs/tools/commands services and provides nothing, so it sits
-# loose (no isolate realm).
-- id: vibe-math-v4
-  name: './vibe-math-v4.js'
+# The `vibe-math-v4` agent preset: the full coding agent (`standard`), plus the
+# FOURTH-generation "persistent self-organizing collaborative research" framework
+# (see 实现方案.md): a set of PERSISTENT resident subagents that decide ALL task
+# allocation among themselves (message/meeting), persist their own progress /
+# proposition / method / sub-problem libraries, verify ONLY by unanimous
+# consensus (else keep as unverified with a probability), self-compact at a
+# context threshold, and stop only when all residents agree the original problem
+# is solved. The framework is a FACILITATOR (message bus / meeting / persist /
+# consensus-verify / context management / resume) — it NEVER assigns tasks.
+#
+# The vibe-math-v4 plugin row consumes 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 V4 toolkit
+
+      This session includes the "Vibe Math V4" persistent self-organizing collaborative
+      research framework (fourth-generation architecture). It is a REAL research group that
+      works by talking: a set of RESIDENT subagents message each other and hold meetings,
+      and they decide ALL task allocation, division of labor, priorities, what to verify, and
+      when to stop — through their own discussion. There is NO central scheduler assigning
+      tasks. Each resident persists its own progress / proposition / method / sub-problem
+      library and WRITES those files DIRECTLY (via fs) in a documented format; anyone may READ
+      everyone else's files (read-only). Anything is "established" only when ALL residents
+      agree (unanimous true or false); otherwise it stays in a library with a probability.
+
+      The framework is just a facilitator: it relays the group's conversation (a resident's
+      `input` is forwarded to the others, and meetings forward everyone's contribution so the
+      team genuinely discusses/debates), convenes and records meetings, exposes a shared task
+      board, and stops the run only when the whole team agrees the problem is solved.
+
+      At brainstorm, residents are told they MAY (but are never forced to) autonomously build a
+      NEW general theory/framework/tool — by abstracting/generalising a structure (like inventing
+      group theory to solve polynomial equations, or building functional analysis as a general
+      framework). If they do, they must state its value to the original problem and may refine /
+      generalise it over time; such artifacts go in their Methods/<resident>/ library. This is an
+      encouragement, not an assignment.
+
+      **YOUR ROLE — LET THEM SELF-ORGANIZE (hands-off):** you are NOT a moderator/coordinator.
+      Do NOT inject agendas, priorities, division-of-labor, or verification decisions, and do
+      NOT direct the residents' work. After `vibe_v4_start`, stay passive: read `vibe_v4_status`
+      / `vibe_v4_report` and summarize in plain language when asked. Use `vibe_v4_message` /
+      `vibe_v4_meeting` ONLY when the user explicitly asks you to intervene, or when the group
+      is visibly deadlocked (all idle & nothing progressing for a long time) — and even then,
+      only relay/nudge the group to decide, never decide for them.
+
+      Data lives under {{cwd}}/VibeMath/Projects/<project>/:
+        Problems/ (original problem card), Progress/<resident>/ (each resident's progress),
+        Propos/<resident>/ (each resident's propositions, "- ID: p-<id>" / "- 概率:" / "- 价值程度:" ...),
+        Methods/<resident>/ (theories/tools), Subproblems/<resident>/, Shared/ (meeting transcripts /
+        task board / debates), Verified/ (read-only, ONLY after unanimous consensus),
+        State/ (framework-private), Reliable/ (references), Notes/.
+
+      Main controls (recommended flow: configure FIRST, then start):
+        - vibe_v4_configure {project?, problem?, params?} — create/configure the project (name, problem, params) WITHOUT starting a run; set everything here first.
+        - vibe_v4_start {problem?, residentCount?, seedDirections?} — begin the run (spawn residents, brainstorm). If problem was configured, omit it.
+        - vibe_v4_set {residentCount, compactThreshold, compactAfterRounds, meetingKeepEvery, maxParallel, activityTimeoutMs, stallAutoMeetingMs, verdictMaxRounds, provider, model, residentPersona, toolAllow, toolDeny} — tune params (persisted to the settings file). provider/model override the residents' LLM route (empty = they inherit YOUR model/provider); toolAllow/toolDeny are per-resident tool permissions (empty = they inherit all tools). stallAutoMeetingMs is the stalled-group auto-sync-meeting threshold (分级保活 B).
+        - vibe_v4_resume / vibe_v4_pause / vibe_v4_abort / vibe_v4_status / vibe_v4_report.
+        - vibe_v4_message {to|all, content} — inject a message to a resident (human/assistant intervention).
+        - vibe_v4_meeting {agenda} — force a meeting.
+        - vibe_v4_add_member {direction?} / vibe_v4_remove_member {id} — add / close a resident.
+        - vibe_v4_list_members — list residents.
+      A /v4 slash command mirrors the main controls (configure|start|resume|pause|abort|status|report|meeting|members|add|remove|set).
+
+      TRUST RULE: only Verified/ (and Propos/ entries marked 已验证·真/假) are absolutely
+      trustworthy; everything else — unverified resident claims, Progress/, Method claims —
+      is experiential reference. A proposition / method / theory only reaches Verified/ when
+      ALL residents unanimously agree true (or all agree false); otherwise it stays in its
+      library with a probability estimate.
+
+      When the user asks about progress, call vibe_v4_report and summarize in plain language.
+    suffix: Your working directory is {{cwd}}.
+    text: |-
+      You are a coding agent powered by the {{model}} model. Your working directory is {{cwd}}.
+
+      ## Vibe Math V4 toolkit
+
+      This session includes the "Vibe Math V4" persistent self-organizing collaborative
+      research framework (fourth-generation architecture). It is a REAL research group that
+      works by talking: a set of RESIDENT subagents message each other and hold meetings,
+      and they decide ALL task allocation, division of labor, priorities, what to verify, and
+      when to stop — through their own discussion. There is NO central scheduler assigning
+      tasks. Each resident persists its own progress / proposition / method / sub-problem
+      library and WRITES those files DIRECTLY (via fs) in a documented format; anyone may READ
+      everyone else's files (read-only). Anything is "established" only when ALL residents
+      agree (unanimous true or false); otherwise it stays in a library with a probability.
+
+      The framework is just a facilitator: it relays the group's conversation (a resident's
+      `input` is forwarded to the others, and meetings forward everyone's contribution so the
+      team genuinely discusses/debates), convenes and records meetings, exposes a shared task
+      board, and stops the run only when the whole team agrees the problem is solved.
+
+      At brainstorm, residents are told they MAY (but are never forced to) autonomously build a
+      NEW general theory/framework/tool — by abstracting/generalising a structure (like inventing
+      group theory to solve polynomial equations, or building functional analysis as a general
+      framework). If they do, they must state its value to the original problem and may refine /
+      generalise it over time; such artifacts go in their Methods/<resident>/ library. This is an
+      encouragement, not an assignment.
+
+      **YOUR ROLE — LET THEM SELF-ORGANIZE (hands-off):** you are NOT a moderator/coordinator.
+      Do NOT inject agendas, priorities, division-of-labor, or verification decisions, and do
+      NOT direct the residents' work. After `vibe_v4_start`, stay passive: read `vibe_v4_status`
+      / `vibe_v4_report` and summarize in plain language when asked. Use `vibe_v4_message` /
+      `vibe_v4_meeting` ONLY when the user explicitly asks you to intervene, or when the group
+      is visibly deadlocked (all idle & nothing progressing for a long time) — and even then,
+      only relay/nudge the group to decide, never decide for them.
+
+      Data lives under {{cwd}}/VibeMath/Projects/<project>/:
+        Problems/ (original problem card), Progress/<resident>/ (each resident's progress),
+        Propos/<resident>/ (each resident's propositions, "- ID: p-<id>" / "- 概率:" / "- 价值程度:" ...),
+        Methods/<resident>/ (theories/tools), Subproblems/<resident>/, Shared/ (meeting transcripts /
+        task board / debates), Verified/ (read-only, ONLY after unanimous consensus),
+        State/ (framework-private), Reliable/ (references), Notes/.
+
+      Main controls (recommended flow: configure FIRST, then start):
+        - vibe_v4_configure {project?, problem?, params?} — create/configure the project (name, problem, params) WITHOUT starting a run; set everything here first.
+        - vibe_v4_start {problem?, residentCount?, seedDirections?} — begin the run (spawn residents, brainstorm). If problem was configured, omit it.
+        - vibe_v4_set {residentCount, compactThreshold, compactAfterRounds, meetingKeepEvery, maxParallel, activityTimeoutMs, stallAutoMeetingMs, verdictMaxRounds, provider, model, residentPersona, toolAllow, toolDeny} — tune params (persisted to the settings file). provider/model override the residents' LLM route (empty = they inherit YOUR model/provider); toolAllow/toolDeny are per-resident tool permissions (empty = they inherit all tools). stallAutoMeetingMs is the stalled-group auto-sync-meeting threshold (分级保活 B).
+        - vibe_v4_resume / vibe_v4_pause / vibe_v4_abort / vibe_v4_status / vibe_v4_report.
+        - vibe_v4_message {to|all, content} — inject a message to a resident (human/assistant intervention).
+        - vibe_v4_meeting {agenda} — force a meeting.
+        - vibe_v4_add_member {direction?} / vibe_v4_remove_member {id} — add / close a resident.
+        - vibe_v4_list_members — list residents.
+      A /v4 slash command mirrors the main controls (configure|start|resume|pause|abort|status|report|meeting|members|add|remove|set).
+
+      TRUST RULE: only Verified/ (and Propos/ entries marked 已验证·真/假) are absolutely
+      trustworthy; everything else — unverified resident claims, Progress/, Method claims —
+      is experiential reference. A proposition / method / theory only reaches Verified/ when
+      ALL residents unanimously agree true (or all agree false); otherwise it stays in its
+      library with a probability estimate.
+
+      When the user asks about progress, call vibe_v4_report and summarize in plain language.
+
+# ── agent-instructions ──────────────────────────────────────────────────────
+
+- 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 V4 ────────────────────────────────────────────────────────────
+
+# THE FOURTH-GENERATION framework: a preset-local plugin (./vibe-math-v4.js)
+# that registers the vibe_v4_* tools + a /v4 slash command, and facilitates a
+# persistent self-organizing band of resident subagents (message bus / meetings /
+# per-resident artifact libraries / unanimous-consensus verification / context
+# compaction / resume / human intervention). It consumes HOST
+# subagents/agents/fs/tools/commands services and provides nothing, so it sits
+# loose (no isolate realm).
+- id: vibe-math-v4
+  name: './vibe-math-v4.js'

package/vibe-math-v4/preset.yml

@@ -1,2 +1,2 @@
-name: Vibe Math V4
-description: 常驻自组织合作研究框架（第四代架构）：一组持久化常驻子代理互相留言、集体开会，自主决定一切任务安排；各自沉淀 progress/命题/方法/子问题库并互相查阅；验证仅当全体常驻一致（真或假）才写入 Verified/，否则留库附概率；上下文达阈值自动 /compact；仅当全体一致认为原问题已解决才停止；断点续跑、多会话隔离、可随时人工干预/增开关闭常驻。
+name: Vibe Math V4
+description: 常驻自组织合作研究框架（第四代架构）：一组持久化常驻子代理互相留言、集体开会，自主决定一切任务安排；各自沉淀 progress/命题/方法/子问题库并互相查阅；验证仅当全体常驻一致（真或假）才写入 Verified/，否则留库附概率；上下文达阈值自动 /compact；仅当全体一致认为原问题已解决才停止；断点续跑、多会话隔离、可随时人工干预/增开关闭常驻。