dsh-vibe-math 1.0.2 → 1.2.0

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

@@ -0,0 +1,226 @@
+# The `vibe-math-v3` agent preset: the full coding agent (`standard`), plus the
+# THIRD-generation multi-agent mathematical problem-solving & verification
+# framework (see 实现方案.md): paper-style Markdown knowledge base
+# (Problems/ Progress/ Propos/ Methods/ Verified/), planner-agent scheduling
+# (one planner call decides the next N actions), and a universal theory/method
+# invention library (Method Keeper distills reusable theories/tools/methods).
+#
+# The vibe-math-v3 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 V3 toolkit
+
+      This session includes the "Vibe Math V3" multi-agent mathematical research and
+      verification framework (third-generation architecture). It is driven by a background
+      scheduler (code) + a PLANNER AGENT: the code builds a state brief and a planner agent
+      autonomously decides the next up-to-N actions (spawn solver/verifier/explorer/method-keeper,
+      interrupt, promote, wait), then the code validates and executes them. You do NOT schedule
+      manually — you only issue the control tools below and read status.
+
+      Data is a PAPER-STYLE MARKDOWN knowledge base under {{cwd}}/VibeMath/Projects/<project>/:
+      Problems/ (问题清单, one md per problem: 陈述/状态/依赖/被依赖/来源与动机/计划/解法候选),
+      Progress/ (研究日志, per-direction round narratives), Propos/ (结论/命题库, one md per
+      proposition), Methods/ (通用理论发明库: 理论体系/框架/工具/方法/思想 invented during
+      solving, distilled by the Method Keeper), Verified/ (绝对可信, scheduler-generated read-only),
+      Reliable/ (user references), Notes/, Logs/, State/ (scheduler-private).
+      TRUST RULE: only Verified/ (and Propos/ entries marked 已验证·真/假) are absolutely
+      trustworthy; everything else — unverified propositions, Progress/ journals, Method claims —
+      is experiential reference.
+
+      - vibe_math_add_problem {id, description, priority, dependencies?} — add a problem (creates Problems/<id>.md).
+      - vibe_math_add_proposition {id, 概述, 概率, 优先级, 价值/关键性, 分类} — add a proposition (Propos/<分类>/<id>.md).
+      - vibe_math_list_propositions — list the proposition knowledge base.
+      - vibe_math_start / vibe_math_resume — start / resume the scheduler (resume = continue after checkpoint/restart).
+      - vibe_math_status / vibe_math_report — read status / full progress report (report writes Progress_Logs/report.json + Logs/报告.md).
+      - vibe_math_pause / vibe_math_abort — pause / abort.
+      - vibe_math_set_mode {mode: manual|auto} — switch manual / auto (manual gates: 计划审批 / 裁决 / 方法晋升).
+      - vibe_math_set_params {...} — tune any parameter (see vibe_math_setup; V3 additions: planningHorizon,
+        plannerEnabled/plannerProvider/plannerModel/plannerPersona, planMinIntervalMs, plannerMaxFails,
+        methodKeepIntervalMs/methodKeepEvery, methodAutoPromote, indexAutoRebuild, projectLockTimeoutMs).
+      - vibe_math_plan {force?} — show queued plan / last plan, or force a planning round.
+      - vibe_math_index — rebuild State/index.json from the Markdown knowledge base.
+      - vibe_math_method_add / vibe_math_method_list — manually add / list method cards (Methods/ + global).
+      - vibe_math_lock_status — project lock occupancy.
+      - 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 (/vibe start|resume|pause|abort|status|report|mode
+      <auto|manual>|setup|save|add <id> <desc>|add-proposition <id> <概述>|list-propositions|methods|index|plan|lock|...).
+      Data survives restarts via vibe_math_resume.
+
+      Key rules when reporting: a problem is "solved" when one of its 解法候选 entries reaches 概率 = 1
+      (the scheduler writes Verified/问题/<id>.md); a proposition reaches 已验证·真/假 when a 证明/证伪
+      entry reaches 概率 = 1 (Verified/命题/<id>.md); Propos propositions with 价值/关键性 ≥
+      promoteValueThreshold auto-promote into Problems/ as "判断下述命题是否成立：<命题>" (verification
+      results sync back to the source proposition); a solver-reported sub-question q_sub registers THREE
+      objects (q_sub problem + judge problem + p-tmp temporary-assumption proposition) with full 来源与动机.
+      When the user asks about progress, call vibe_math_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 V3 ────────────────────────────────────────────────────────────
+
+# The THIRD-generation framework: a preset-local plugin (./vibe-math-v3.js)
+# that registers the vibe_math_* tools, a /vibe slash command, and a background
+# scheduler (planner-agent scheduling → explorer → per-direction solvers →
+# multi-reviewer verification; method library + Method Keeper; paper-style
+# Markdown knowledge base). It consumes the HOST subagents/agents/fs/tools/commands
+# services and provides nothing, so it sits loose (no isolate realm).
+- id: vibe-math-v3
+  name: './vibe-math-v3.js'

package/vibe-math-v3/preset.yml

@@ -0,0 +1,2 @@
+name: Vibe Math V3
+description: 多代理数学研究与验证框架（第三代架构）：论文式 Markdown 知识库（Problems/ 问题清单+依赖+来源动机、Progress/ 研究日志、Propos/ 命题库、Methods/ 通用理论发明库、Verified/ 绝对可信）+ 规划代理自主调度（一次安排接下来 n 次各代理任务）+ 方法库沉淀循环（Method Keeper 提炼理论/框架/工具/方法/思想）；断点续跑、人工/自动干预、多会话并行隔离。