dsh-vibe-math 2.7.1 → 2.7.3

package/vibe-math-v2//345/256/236/347/216/260/346/226/271/346/241/210.md

@@ -484,4 +484,8 @@ v2 **没有会话投影**，所以记录与待办一起持久化在 v2 自己的
   `require` 档**必须**出现（那里门禁真的会搁置裁定）。
 - `kind='def'/'lemma'` 运行未通过时，工具返回值**不得**声称"可直接 import 复用"。
 
-套件支持 `V2_PLUGIN` 环境变量指向变异副本，供灵敏度探针使用。
+套件支持 `V2_PLUGIN` 环境变量指向变异副本，供灵敏度探针使用。
+
+## 状态 / 报告字段：`verifyTasksView`（单一来源）
+
+v2 的 **status 与 report 两个视图**里出现的验证任务列表由**同一个** helper `verifyTasksView(tasks)` 产出（`vibe-math-v2.js:2995`；调用点 `:2046` 与 `:4039`），因此两处字段必须**逐个字段一致**；任何"在某一侧顺手补一个字段"的改动都会让两个视图分叉。该一致性由 `tests/formal-verify-v2.test.mjs:1694-1698` 钉住（两侧取自同一 helper 且字段集合相等）。

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

@@ -56,6 +56,7 @@
       - 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 (the lock is a renewed lease: while a session is running it never expires; taking it over needs override=true, or happens automatically once the owner's lease has clearly expired after a crash).
+      - vibe_math_claim_write / vibe_math_release_write — (member) 写共用 Markdown（含 Progress/<qid>/<dirId>.md）前先取该文件的写锁、写完立刻释放；锁被别的成员持有时报出持有者，不要硬写。
         Only ONE session may run a project: a second session is refused with PROJECT_LOCKED instead of silently writing the same knowledge base in parallel.
       - 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.
@@ -69,7 +70,7 @@
 
       - math_computation {op: probe|run|receipt|install, engine, mode: code|file|expr, …} — 先 probe 预检引擎/包/许可，再调引擎计算并把脚本与输出归档成可复核回执；缺引擎/缺包只报告与给安装指引/计划；shell 兜底不算归档。
       - 替代必须声明（诚实性）：当替代方案改变了**精确性或结论强度**时（精确符号解 → 数值近似、闭式解 → 采样/求积、改了精度/容差/假设、换了算法类），结论里**必须写明**，不得读起来像得到了原本（精确/所要求的）结果；拿不到精确结果就直说。
-      - 归档→编辑→重跑：mode:'code' 的脚本原件在回执的 scriptPath（Computation/<id>/script.<ext>），你可以用普通文件工具打开并编辑它；编辑后用 mode:'file' 指向它重跑，会写出一份**新回执/新 attempt**（含新的 scriptHash）。**旧回执对修改后的代码无效**——报告里必须引用与当前代码哈希一致的那份回执；工具会在 scriptChanged / scriptChangedDuringRun 为 true 时显式告警。
+      - 归档→编辑→重跑：mode:'code' 的脚本原件在回执的 scriptPath（Computation/<id>/script.<ext>，**相对项目根**）；**成员的文件工具是按会话 cwd 解析的**，所以读它要用**绝对路径** `receipt.scriptAbs`，或把 `receipt.cwd` 与 `receipt.scriptPath` 拼起来（回执两个字段都有）。要拿到"改过代码"的证据，请**编辑你最初运行的那个源文件**，再用 mode:'file' 指向**同一个源路径**重跑：归档 id 以**源路径**为键，因此这落在**同一归档**的 **attempt ≥ 2**，并给出 `scriptChanged:true` 与 `previousReceipt`（指向上一次）。**指向归档副本本身**（`receipt.scriptAbs` 那个路径）按设计是**另一份新归档**：新 id、attempt 1、没有 `previousReceipt`、`scriptChanged:false`；旧 attempt 绝不会被覆盖，但它**不是**"同一归档的新 attempt"——工具会用 `fileIsArchivedScript` 与 `ARCHIVED_SCRIPT_RERUN` 警告明确说明。**旧回执对修改后的代码无效**——报告里必须引用与当前代码哈希一致的那份回执；工具会在 scriptChanged / scriptChangedDuringRun 为 true 时显式告警。
 
       A /vibe slash command mirrors the main controls (/vibe start [override]|resume [override]|pause|abort|status|report|mode
       <auto|manual>|setup|save|template [global|project]|add <id> <desc>|add-proposition <id> <概述>|list-propositions|methods|index|plan|lock|project [list|new <name>|<name>]|decisions|agents|paper [lang=zh|en] [format=both|md|tex] [force]).
@@ -95,8 +96,15 @@
           match the proposition as stated) | 'require' (same, plus a gate: a true/false verdict is
           withheld as 未定论 with reason formal-required until the object is Lean-passed or carries an
           explicit, reasoned blocker record; the scheduler is never wedged by it).
-        - Paths: work file Formal/<id>.lean; archived proof Verified/Lean/<id>.lean; reusable
-          definitions VibeMath/Formal/Lib/; proved lemmas VibeMath/Formal/Proved/.
+        - Paths (every path here is resolved against the SESSION WORKING DIRECTORY, i.e. the cwd
+          printed at the end of this prompt; the project root is the `Data lives under …`
+          directory above):
+          institute work file `<project root>/Formal/<id>.lean`;
+          archived proof `<project root>/Verified/Lean/<id>.lean`;
+          reusable definitions `VibeMath/Formal/Lib/` (workspace-root relative);
+          proved lemmas `VibeMath/Formal/Proved/` (workspace-root relative);
+          short form `Formal/<id>.lean` (project-root relative) names the SAME file as
+          `<project root>/Formal/<id>.lean`.
         - The toolchain knobs leanCommand / leanArgs / leanTimeoutMs / leanAsync / leanInitiative / leanSearchPaths / leanJobsMaxParallel are tunable as well
           (e.g. leanCommand='lake' with leanArgs=['env','lean']); a missing Lean binary is
           reported as LEAN_NOT_FOUND and still lets the code be written and archived.
@@ -104,6 +112,31 @@
           formalization TODO (Formal/TODO.md). The framework never installs Lean and never judges
           fidelity for you.
       When the user asks about progress, call vibe_math_report and summarize in plain language.
+
+      DISCLOSURES (existing behaviour, not rules to follow):
+        - DISCLOSURE (existing behaviour): the FINAL PAPER flow can finish without you — when it hits
+          its round/token cap the framework force-finalises the paper (`forcedAfterCap`) and reaps an
+          in-flight writer that never came back; the activity log says so. You do not lose the paper,
+          you lose the chance to keep iterating on it.
+        - DISCLOSURE (existing behaviour): switching the mode to `auto` immediately resolves EVERY
+          pending decision as auto-decided (the activity log records "auto-resolved N pending
+          decision(s)"). Anything you leave pending will not wait for you.
+        - DISCLOSURE (existing behaviour): the framework itself pushes a progress update to the office
+          (reportMode / reportIntervalMs) — a summary you did not ask for can arrive at a round
+          boundary; it is a report, not a new instruction.
+        - DISCLOSURE (existing behaviour): a second session can TAKE OVER the project lock
+          (the activity log records "project lock taken over from session …") — another office may
+          resume the same project while you are away; the state file stays authoritative and is not
+          merged.
+        - DISCLOSURE (existing behaviour): the framework can adjust problem/proposition priorities
+          itself (priorityAdjust / proposPriorityAdjust) — the activity log records "priorities
+          auto-adjusted (…)"; a problem you deprioritised can come back on its own.
+        - DISCLOSURE (existing behaviour): when mathMode is `typed`, the shell fallback is refused
+          (the math tool returns REFUSED with reason=policy) instead of silently falling back.
+        - math_computation policy: mathComputation = off | auto | on (off = the math surface is
+          not mentioned in prompts at all); mathMode = typed | typed+shell (typed refuses the shell
+          fallback); mathEngines (cli / python / …); mathTimeoutMs; mathPackages + mathInstallScope
+          for preflight package installs (missing packages are reported with an install plan only).
     suffix: Your working directory is {{cwd}}.
     text: |-
       You are a coding agent powered by the {{model}} model. Your working directory is {{cwd}}.
@@ -148,6 +181,7 @@
       - 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 (the lock is a renewed lease: while a session is running it never expires; taking it over needs override=true, or happens automatically once the owner's lease has clearly expired after a crash).
+      - vibe_math_claim_write / vibe_math_release_write — (member) 写共用 Markdown（含 Progress/<qid>/<dirId>.md）前先取该文件的写锁、写完立刻释放；锁被别的成员持有时报出持有者，不要硬写。
         Only ONE session may run a project: a second session is refused with PROJECT_LOCKED instead of silently writing the same knowledge base in parallel.
       - 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.
@@ -161,7 +195,7 @@
 
       - math_computation {op: probe|run|receipt|install, engine, mode: code|file|expr, …} — 先 probe 预检引擎/包/许可，再调引擎计算并把脚本与输出归档成可复核回执；缺引擎/缺包只报告与给安装指引/计划；shell 兜底不算归档。
       - 替代必须声明（诚实性）：当替代方案改变了**精确性或结论强度**时（精确符号解 → 数值近似、闭式解 → 采样/求积、改了精度/容差/假设、换了算法类），结论里**必须写明**，不得读起来像得到了原本（精确/所要求的）结果；拿不到精确结果就直说。
-      - 归档→编辑→重跑：mode:'code' 的脚本原件在回执的 scriptPath（Computation/<id>/script.<ext>），你可以用普通文件工具打开并编辑它；编辑后用 mode:'file' 指向它重跑，会写出一份**新回执/新 attempt**（含新的 scriptHash）。**旧回执对修改后的代码无效**——报告里必须引用与当前代码哈希一致的那份回执；工具会在 scriptChanged / scriptChangedDuringRun 为 true 时显式告警。
+      - 归档→编辑→重跑：mode:'code' 的脚本原件在回执的 scriptPath（Computation/<id>/script.<ext>，**相对项目根**）；**成员的文件工具是按会话 cwd 解析的**，所以读它要用**绝对路径** `receipt.scriptAbs`，或把 `receipt.cwd` 与 `receipt.scriptPath` 拼起来（回执两个字段都有）。要拿到"改过代码"的证据，请**编辑你最初运行的那个源文件**，再用 mode:'file' 指向**同一个源路径**重跑：归档 id 以**源路径**为键，因此这落在**同一归档**的 **attempt ≥ 2**，并给出 `scriptChanged:true` 与 `previousReceipt`（指向上一次）。**指向归档副本本身**（`receipt.scriptAbs` 那个路径）按设计是**另一份新归档**：新 id、attempt 1、没有 `previousReceipt`、`scriptChanged:false`；旧 attempt 绝不会被覆盖，但它**不是**"同一归档的新 attempt"——工具会用 `fileIsArchivedScript` 与 `ARCHIVED_SCRIPT_RERUN` 警告明确说明。**旧回执对修改后的代码无效**——报告里必须引用与当前代码哈希一致的那份回执；工具会在 scriptChanged / scriptChangedDuringRun 为 true 时显式告警。
 
       A /vibe slash command mirrors the main controls (/vibe start [override]|resume [override]|pause|abort|status|report|mode
       <auto|manual>|setup|save|template [global|project]|add <id> <desc>|add-proposition <id> <概述>|list-propositions|methods|index|plan|lock|project [list|new <name>|<name>]|decisions|agents|paper [lang=zh|en] [format=both|md|tex] [force]).
@@ -187,8 +221,15 @@
           match the proposition as stated) | 'require' (same, plus a gate: a true/false verdict is
           withheld as 未定论 with reason formal-required until the object is Lean-passed or carries an
           explicit, reasoned blocker record; the scheduler is never wedged by it).
-        - Paths: work file Formal/<id>.lean; archived proof Verified/Lean/<id>.lean; reusable
-          definitions VibeMath/Formal/Lib/; proved lemmas VibeMath/Formal/Proved/.
+        - Paths (every path here is resolved against the SESSION WORKING DIRECTORY, i.e. the cwd
+          printed at the end of this prompt; the project root is the `Data lives under …`
+          directory above):
+          institute work file `<project root>/Formal/<id>.lean`;
+          archived proof `<project root>/Verified/Lean/<id>.lean`;
+          reusable definitions `VibeMath/Formal/Lib/` (workspace-root relative);
+          proved lemmas `VibeMath/Formal/Proved/` (workspace-root relative);
+          short form `Formal/<id>.lean` (project-root relative) names the SAME file as
+          `<project root>/Formal/<id>.lean`.
         - The toolchain knobs leanCommand / leanArgs / leanTimeoutMs / leanAsync / leanInitiative / leanSearchPaths / leanJobsMaxParallel are tunable as well
           (e.g. leanCommand='lake' with leanArgs=['env','lean']); a missing Lean binary is
           reported as LEAN_NOT_FOUND and still lets the code be written and archived.
@@ -197,6 +238,31 @@
           fidelity for you.
       When the user asks about progress, call vibe_math_report and summarize in plain language.
 
+      DISCLOSURES (existing behaviour, not rules to follow):
+        - DISCLOSURE (existing behaviour): the FINAL PAPER flow can finish without you — when it hits
+          its round/token cap the framework force-finalises the paper (`forcedAfterCap`) and reaps an
+          in-flight writer that never came back; the activity log says so. You do not lose the paper,
+          you lose the chance to keep iterating on it.
+        - DISCLOSURE (existing behaviour): switching the mode to `auto` immediately resolves EVERY
+          pending decision as auto-decided (the activity log records "auto-resolved N pending
+          decision(s)"). Anything you leave pending will not wait for you.
+        - DISCLOSURE (existing behaviour): the framework itself pushes a progress update to the office
+          (reportMode / reportIntervalMs) — a summary you did not ask for can arrive at a round
+          boundary; it is a report, not a new instruction.
+        - DISCLOSURE (existing behaviour): a second session can TAKE OVER the project lock
+          (the activity log records "project lock taken over from session …") — another office may
+          resume the same project while you are away; the state file stays authoritative and is not
+          merged.
+        - DISCLOSURE (existing behaviour): the framework can adjust problem/proposition priorities
+          itself (priorityAdjust / proposPriorityAdjust) — the activity log records "priorities
+          auto-adjusted (…)"; a problem you deprioritised can come back on its own.
+        - DISCLOSURE (existing behaviour): when mathMode is `typed`, the shell fallback is refused
+          (the math tool returns REFUSED with reason=policy) instead of silently falling back.
+        - math_computation policy: mathComputation = off | auto | on (off = the math surface is
+          not mentioned in prompts at all); mathMode = typed | typed+shell (typed refuses the shell
+          fallback); mathEngines (cli / python / …); mathTimeoutMs; mathPackages + mathInstallScope
+          for preflight package installs (missing packages are reported with an install plan only).
+
 # ── agent-instructions ──────────────────────────────────────────────────────
 
 - id: agent-instructions