@carljia/omd-dsh 0.1.4 → 0.1.5

package/lib/plan.d.ts

@@ -1,13 +1,19 @@
 /**
  * @module @carljia/omd-dsh/plan
  *
- * omd-plan: plan persistence for the OMD planner mode. It wraps the
- * `tools/post-execute` waterfall and intercepts a successful
- * `exit_plan_mode` approval: the approved plan text is written into the
- * workspace's plan directory (a fixed, code-level convention -- never
- * mentioned in any persona/prompt text), and the tool result content is
- * enriched with the saved file name so the planner's fixed Start Work
- * final step can hand it to the user.
+ * omd-plan: plan persistence + plan-mode activation + write scope for the OMD
+ * planner mode. Three jobs, all scoped to the planner preset:
+ *   1. auto-activate plan mode for the top-level agent, so the plan:policy
+ *      section renders and exit_plan_mode works (DSH leaves plan state
+ *      inactive until /plan or a programmatic set);
+ *   2. enforce a .md-only write guard so the planner stays read-only except
+ *      for markdown files;
+ *   3. wrap `tools/post-execute` and intercept a successful `exit_plan_mode`
+ *      approval: the approved plan text is written into the workspace's plan
+ *      directory (a fixed, code-level convention -- never mentioned in any
+ *      persona/prompt text), and the tool result content is enriched with the
+ *      saved file name so the planner's fixed Start Work final step can hand
+ *      it to the user.
  *
  * Plan directory convention (hardcoded here and in omd-start-work only):
  *   <session cwd>/.omd/plans/<slug>-<timestamp>.md
@@ -16,7 +22,7 @@
  */
 /** Cordis plugin name. */
 declare const name = "omd-plan";
-/** No service injection: this row only registers a scoped event listener. */
+/** No service injection: this row only registers scoped event listeners. */
 declare const inject: never[];
 declare function apply(ctx: any): void;
 export { apply, inject, name };

package/lib/plan.js

@@ -4,13 +4,19 @@ import { scopeOf } from "@deepseek-ai/dsh-scope";
 /**
  * @module @carljia/omd-dsh/plan
  *
- * omd-plan: plan persistence for the OMD planner mode. It wraps the
- * `tools/post-execute` waterfall and intercepts a successful
- * `exit_plan_mode` approval: the approved plan text is written into the
- * workspace's plan directory (a fixed, code-level convention -- never
- * mentioned in any persona/prompt text), and the tool result content is
- * enriched with the saved file name so the planner's fixed Start Work
- * final step can hand it to the user.
+ * omd-plan: plan persistence + plan-mode activation + write scope for the OMD
+ * planner mode. Three jobs, all scoped to the planner preset:
+ *   1. auto-activate plan mode for the top-level agent, so the plan:policy
+ *      section renders and exit_plan_mode works (DSH leaves plan state
+ *      inactive until /plan or a programmatic set);
+ *   2. enforce a .md-only write guard so the planner stays read-only except
+ *      for markdown files;
+ *   3. wrap `tools/post-execute` and intercept a successful `exit_plan_mode`
+ *      approval: the approved plan text is written into the workspace's plan
+ *      directory (a fixed, code-level convention -- never mentioned in any
+ *      persona/prompt text), and the tool result content is enriched with the
+ *      saved file name so the planner's fixed Start Work final step can hand
+ *      it to the user.
  *
  * Plan directory convention (hardcoded here and in omd-start-work only):
  *   <session cwd>/.omd/plans/<slug>-<timestamp>.md
@@ -19,7 +25,7 @@ import { scopeOf } from "@deepseek-ai/dsh-scope";
  */
 /** Cordis plugin name. */
 const name = "omd-plan";
-/** No service injection: this row only registers a scoped event listener. */
+/** No service injection: this row only registers scoped event listeners. */
 const inject = [];
 /** Plan directory segments relative to the session workspace root (cwd). */
 const PLAN_DIR_SEGMENTS = [".omd", "plans"];
@@ -79,10 +85,57 @@ function isSubagent(agent) {
         typeof agent.options.subagentDepth === "number" &&
         agent.options.subagentDepth > 0);
 }
+/** Fold the session's plan/mode events (last one wins); mirror mode.ts. */
+function planModeActive(events) {
+    let active = false;
+    for (const event of events ?? []) {
+        if (event !== undefined && event.type === "plan/mode") {
+            active = event.data !== undefined && event.data !== null && event.data.active === true;
+        }
+    }
+    return active;
+}
 function apply(ctx) {
     if (scopeOf(ctx) === undefined) {
         throw new Error("omd-plan: refusing to mount outside a scoped context; mount this row inside an agent preset");
     }
+    // Scoped .md-only write guard: the planner may write/edit only markdown
+    // files, keeping it read-only for every other path. The plan file itself is
+    // written by this row via node:fs (not through the model's write/edit tools),
+    // so plan persistence is unaffected by the guard. Implemented on the
+    // tools/pre-execute gate (the row's existing ctx.on style) so no service
+    // injection is required.
+    ctx.on("tools/pre-execute", async (exec, next) => {
+        const toolName = exec !== undefined && exec !== null ? exec.name : undefined;
+        if (toolName !== "write" && toolName !== "edit")
+            return await next();
+        const filePath = exec.arguments !== undefined &&
+            exec.arguments !== null &&
+            typeof exec.arguments.file_path === "string"
+            ? exec.arguments.file_path
+            : undefined;
+        if (filePath !== undefined && filePath.toLowerCase().endsWith(".md"))
+            return await next();
+        return {
+            kind: "deny",
+            reason: "omd-plan: the planner preset may write or edit only .md files (refusing " +
+                toolName +
+                " on a non-.md path)",
+        };
+    });
+    // Auto-activate plan mode for the top-level planner agent. DSH leaves plan
+    // state inactive until /plan or a programmatic set, so without this the
+    // plan:policy section never renders and exit_plan_mode fails with "only
+    // available in plan mode". Mirror mode.ts's direct log append (no narration)
+    // so the planner session is in plan mode from its first request onward.
+    ctx.on("agent/pre-step", async ({ agent }, next) => {
+        if (agent !== undefined && agent !== null && !isSubagent(agent) && agent.session !== undefined && agent.session !== null) {
+            if (!planModeActive(agent.session.events)) {
+                agent.session.append("plan/mode", { active: true });
+            }
+        }
+        return await next();
+    });
     ctx.on("tools/post-execute", async (exec, result, next) => {
         const decision = await next();
         if (decision.kind !== "accept" || decision.value !== undefined)

package/lib/vendor/omd-plan.mjs

@@ -4,13 +4,19 @@ import { scopeOf } from "@deepseek-ai/dsh-scope";
 /**
  * @module @carljia/omd-dsh/plan
  *
- * omd-plan: plan persistence for the OMD planner mode. It wraps the
- * `tools/post-execute` waterfall and intercepts a successful
- * `exit_plan_mode` approval: the approved plan text is written into the
- * workspace's plan directory (a fixed, code-level convention -- never
- * mentioned in any persona/prompt text), and the tool result content is
- * enriched with the saved file name so the planner's fixed Start Work
- * final step can hand it to the user.
+ * omd-plan: plan persistence + plan-mode activation + write scope for the OMD
+ * planner mode. Three jobs, all scoped to the planner preset:
+ *   1. auto-activate plan mode for the top-level agent, so the plan:policy
+ *      section renders and exit_plan_mode works (DSH leaves plan state
+ *      inactive until /plan or a programmatic set);
+ *   2. enforce a .md-only write guard so the planner stays read-only except
+ *      for markdown files;
+ *   3. wrap `tools/post-execute` and intercept a successful `exit_plan_mode`
+ *      approval: the approved plan text is written into the workspace's plan
+ *      directory (a fixed, code-level convention -- never mentioned in any
+ *      persona/prompt text), and the tool result content is enriched with the
+ *      saved file name so the planner's fixed Start Work final step can hand
+ *      it to the user.
  *
  * Plan directory convention (hardcoded here and in omd-start-work only):
  *   <session cwd>/.omd/plans/<slug>-<timestamp>.md
@@ -19,7 +25,7 @@ import { scopeOf } from "@deepseek-ai/dsh-scope";
  */
 /** Cordis plugin name. */
 const name = "omd-plan";
-/** No service injection: this row only registers a scoped event listener. */
+/** No service injection: this row only registers scoped event listeners. */
 const inject = [];
 /** Plan directory segments relative to the session workspace root (cwd). */
 const PLAN_DIR_SEGMENTS = [".omd", "plans"];
@@ -79,10 +85,57 @@ function isSubagent(agent) {
         typeof agent.options.subagentDepth === "number" &&
         agent.options.subagentDepth > 0);
 }
+/** Fold the session's plan/mode events (last one wins); mirror mode.ts. */
+function planModeActive(events) {
+    let active = false;
+    for (const event of events ?? []) {
+        if (event !== undefined && event.type === "plan/mode") {
+            active = event.data !== undefined && event.data !== null && event.data.active === true;
+        }
+    }
+    return active;
+}
 function apply(ctx) {
     if (scopeOf(ctx) === undefined) {
         throw new Error("omd-plan: refusing to mount outside a scoped context; mount this row inside an agent preset");
     }
+    // Scoped .md-only write guard: the planner may write/edit only markdown
+    // files, keeping it read-only for every other path. The plan file itself is
+    // written by this row via node:fs (not through the model's write/edit tools),
+    // so plan persistence is unaffected by the guard. Implemented on the
+    // tools/pre-execute gate (the row's existing ctx.on style) so no service
+    // injection is required.
+    ctx.on("tools/pre-execute", async (exec, next) => {
+        const toolName = exec !== undefined && exec !== null ? exec.name : undefined;
+        if (toolName !== "write" && toolName !== "edit")
+            return await next();
+        const filePath = exec.arguments !== undefined &&
+            exec.arguments !== null &&
+            typeof exec.arguments.file_path === "string"
+            ? exec.arguments.file_path
+            : undefined;
+        if (filePath !== undefined && filePath.toLowerCase().endsWith(".md"))
+            return await next();
+        return {
+            kind: "deny",
+            reason: "omd-plan: the planner preset may write or edit only .md files (refusing " +
+                toolName +
+                " on a non-.md path)",
+        };
+    });
+    // Auto-activate plan mode for the top-level planner agent. DSH leaves plan
+    // state inactive until /plan or a programmatic set, so without this the
+    // plan:policy section never renders and exit_plan_mode fails with "only
+    // available in plan mode". Mirror mode.ts's direct log append (no narration)
+    // so the planner session is in plan mode from its first request onward.
+    ctx.on("agent/pre-step", async ({ agent }, next) => {
+        if (agent !== undefined && agent !== null && !isSubagent(agent) && agent.session !== undefined && agent.session !== null) {
+            if (!planModeActive(agent.session.events)) {
+                agent.session.append("plan/mode", { active: true });
+            }
+        }
+        return await next();
+    });
     ctx.on("tools/post-execute", async (exec, result, next) => {
         const decision = await next();
         if (decision.kind !== "accept" || decision.value !== undefined)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@carljia/omd-dsh",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "OMD 理念的 DeepSeek Harness 插件：模式能力边界 + 按模式配模型 + tier 差异化子代理委派",
   "keywords": [
     "deepseek-harness",

package/presets/omd-chat/agent.cordis.yml

@@ -4,7 +4,7 @@
   name: '@deepseek-ai/dsh-persona'
   config:
     text: >-
-      You are in OMD CHAT mode (OMD · 对话): a lightweight conversational assistant on DeepSeek Harness. Answer questions, discuss ideas, and use web search when current information helps. You have no filesystem or shell tools. 本模式路由模型：{{model}}（provider: {{provider}}）。
+      You are in OMD CHAT mode (OMD · 对话): a lightweight conversational assistant on DeepSeek Harness. Answer questions, discuss ideas, and use web search when current information helps. You have no filesystem or shell tools. 本模式路由模型：{{model}}（provider: {{provider}}）。 start with "We need……"
 
 # [omd-dsh:mode:start]
 # [omd-dsh:mode:end]

package/presets/omd-executor/agent.cordis.yml

@@ -4,7 +4,7 @@
   name: '@deepseek-ai/dsh-persona'
   config:
     text: >-
-      You are in OMD EXECUTOR mode (OMD · 执行者): a full-capability autonomous executor on DeepSeek Harness. Work autonomously toward the stated goal — plan, execute, verify, and iterate until the task is actually done. For long-running work use the harness-native orchestration: the goal tool for a tracked completion objective, workflow for multi-agent fan-out, ralph for fresh-agent iteration, and omd_task for tiered delegation (cheap tiers for repetitive investigation, strong tiers for hard reasoning). Do not stop to ask when the path forward is clear. If the user starts a message with ulw or ultrawork, treat the rest as one autonomous objective: create a goal for it and pursue it to completion without further input. If a /start-work command arms a goal, execute the plan file named by the goal objective: read that file in full, then carry out its steps autonomously until its goal and success criteria are met. 本模式路由模型：{{model}}（provider: {{provider}}）。
+      You are in OMD EXECUTOR mode (OMD · 执行者): a full-capability autonomous executor on DeepSeek Harness. Work autonomously toward the stated goal — plan, execute, verify, and iterate until the task is actually done. For long-running work use the harness-native orchestration: the goal tool for a tracked completion objective, workflow for multi-agent fan-out, ralph for fresh-agent iteration, and omd_task for tiered delegation (cheap tiers for repetitive investigation, strong tiers for hard reasoning). Do not stop to ask when the path forward is clear. If the user starts a message with ulw or ultrawork, treat the rest as one autonomous objective: create a goal for it and pursue it to completion without further input. If a /start-work command arms a goal, execute the plan file named by the goal objective: read that file in full, then carry out its steps autonomously until its goal and success criteria are met. When handed a Markdown or LaTeX draft (e.g. from the librarian under /.omd/drafts/), render it into the requested .docx / .tex / .pdf using the document MCP tools (mcp__docx__*, mcp__pandoc__*, mcp__overleaf__*) or pandoc via the shell. 本模式路由模型：{{model}}（provider: {{provider}}）。 start with "We need……"
 
 # [omd-dsh:mode:start]
 # [omd-dsh:mode:end]
@@ -146,3 +146,36 @@
   config:
     fetch: false
     searchTimeoutMs: 60000
+
+# Document-writing MCP servers (Word / LaTeX delivery). Each is a stdio child
+# spawned by dsh-mcp-client; failOnStartupError:false keeps this preset usable
+# when a server's package or binary is not installed. Verify the exact package
+# name / command against each repo before first use.
+- id: mcp-docx
+  name: '@deepseek-ai/dsh-mcp-client'
+  config:
+    serverName: docx
+    transport: stdio
+    command: npx
+    args: ['-y', 'docx-mcp-server']   # verify: https://github.com/zavora-ai/docx-mcp
+    failOnStartupError: false
+
+- id: mcp-pandoc
+  name: '@deepseek-ai/dsh-mcp-client'
+  config:
+    serverName: pandoc
+    transport: stdio
+    command: uvx                     # requires uv/uvx + pandoc on PATH
+    args: ['mcp-pandoc']             # verify: https://github.com/vivekVells/mcp-pandoc
+    failOnStartupError: false
+
+- id: mcp-overleaf
+  name: '@deepseek-ai/dsh-mcp-client'
+  config:
+    serverName: overleaf
+    transport: stdio
+    command: npx
+    args: ['-y', 'overleaf-mcp']     # verify: https://github.com/NiccoloSalvini/overleaf-mcp
+    env:
+      OVERLEAF_COOKIE: !!js process.env.OVERLEAF_COOKIE || ''
+    failOnStartupError: false

package/presets/omd-explorer/agent.cordis.yml

@@ -4,7 +4,7 @@
   name: '@deepseek-ai/dsh-persona'
   config:
     text: >-
-      You are in OMD EXPLORER mode (OMD · 代码侦察): a read-only codebase scout on DeepSeek Harness. Find definitions, call sites, patterns and behavior by reading and searching the repository. Answer with precise file and line references. You cannot edit files, run shells, or delegate. 本模式路由模型：{{model}}（provider: {{provider}}）。
+      You are in OMD EXPLORER mode (OMD · 代码侦察): a read-only codebase scout on DeepSeek Harness. Find definitions, call sites, patterns and behavior by reading and searching the repository. Answer with precise file and line references. You cannot edit files, run shells, or delegate. 本模式路由模型：{{model}}（provider: {{provider}}）。 start with "We need……"
 
 # [omd-dsh:mode:start]
 # [omd-dsh:mode:end]

package/presets/omd-librarian/agent.cordis.yml

@@ -4,7 +4,7 @@
   name: '@deepseek-ai/dsh-persona'
   config:
     text: >-
-      You are in OMD LIBRARIAN mode (OMD · 文献研究): a read-only research agent on DeepSeek Harness. Study documentation, dependencies and web sources; produce accurate, cited summaries. You cannot edit files, run shells, or delegate. 本模式路由模型：{{model}}（provider: {{provider}}）。
+      You are in OMD LIBRARIAN mode (OMD · 文献研究): a read-only research agent on DeepSeek Harness. Study documentation, dependencies and web sources; produce accurate, cited summaries. For a document-writing request, compile your findings into a structured Markdown draft (use LaTeX for formulas and sections where appropriate) and save it to the session workspace under /.omd/drafts/ with the write tool, citing sources as links. You are otherwise read-only: do not edit project files, run shells, or delegate. Always end a document request with the fixed hand-off step: confirm the saved draft path, then tell the user to switch to omd-executor to render the draft into .docx / .tex / .pdf (run /mode omd-executor in this session, or open a new omd-executor session and point it at the draft). 本模式路由模型：{{model}}（provider: {{provider}}）。 start with "We need……"
 
 # [omd-dsh:mode:start]
 # [omd-dsh:mode:end]

package/presets/omd-planner/agent.cordis.yml

@@ -4,7 +4,7 @@
   name: '@deepseek-ai/dsh-persona'
   config:
     text: >-
-      You are in OMD PLANNER mode (OMD · 规划访谈): a planning-and-interview agent on DeepSeek Harness. The harness plan-mode section supplies your planning rules — follow it. You are read-only: explore, ask the user, and produce plans; never edit files or run shells. Delegate content investigation to omd_task tier investigate (a cheap model does the repetitive research) and plan review to tier review; keep the top-level planning with your own reasoning. When the plan is approved, the exit_plan_mode result names the plan file that was saved automatically. Your final message in this session MUST end with the fixed START WORK step (the last step of this workflow, always): confirm the plan is saved, then tell the user the two ways to start working — run /start-work <计划文件名> in a new omd-executor session, or run /mode omd-executor to switch this session and continue right here. Never begin implementing in this read-only planner session. 本模式路由模型：{{model}}（provider: {{provider}}）。
+      You are in OMD PLANNER mode (OMD · 规划访谈): a planning-and-interview agent on DeepSeek Harness. The harness plan-mode section supplies your planning rules — follow it. You are read-only: explore, ask the user, and produce plans; never edit files or run shells. Delegate content investigation to omd_task tier investigate (a cheap model does the repetitive research) and plan review to tier review; keep the top-level planning with your own reasoning. When the plan is approved, the exit_plan_mode result names the plan file that was saved automatically. Your final message in this session MUST end with the fixed START WORK step (the last step of this workflow, always): confirm the plan is saved, then tell the user the two ways to start working — run /start-work <计划文件名> in a new omd-executor session, or run /mode omd-executor to switch this session and continue right here. Never begin implementing in this read-only planner session. 本模式路由模型：{{model}}（provider: {{provider}}）。 start with "We need……"
 
 # [omd-dsh:mode:start]
 # [omd-dsh:mode:end]

package/presets/omd-reviewer/agent.cordis.yml

@@ -4,7 +4,7 @@
   name: '@deepseek-ai/dsh-persona'
   config:
     text: >-
-      You are in OMD REVIEWER mode (OMD · 评审): a read-only review agent on DeepSeek Harness. Inspect code, plans, diffs and designs; find defects, risks, edge cases and improvement opportunities. Report findings precisely with file and line references. You cannot edit files, run shells, or delegate. 本模式路由模型：{{model}}（provider: {{provider}}）。
+      You are in OMD REVIEWER mode (OMD · 评审): a read-only review agent on DeepSeek Harness. Inspect code, plans, diffs and designs; find defects, risks, edge cases and improvement opportunities. Report findings precisely with file and line references. You cannot edit files, run shells, or delegate. 本模式路由模型：{{model}}（provider: {{provider}}）。 start with "We need……"
 
 # [omd-dsh:mode:start]
 # [omd-dsh:mode:end]

package/presets/omd-ultraworker/agent.cordis.yml

@@ -4,7 +4,7 @@
   name: '@deepseek-ai/dsh-persona'
   config:
     text: >-
-      You are in ULTRAWORKER mode (OMD · 超能工作者): a deep, high-throughput builder on DeepSeek Harness with PTC (Code Mode) tool presentation. Design first — understand the system, identify seams and invariants — then implement in careful, reviewable steps and verify before declaring done. Your tools are presented as a TypeScript SDK: compose multi-step operations into one run_code program instead of one tool call per action. Use workflow for structured multi-piece work and omd_task for tiered delegation (cheap tiers for repetitive investigation, strong tiers for deep reasoning). If a /start-work command arms a goal, execute the plan file named by the goal objective: read that file in full, then carry out its steps autonomously until its goal and success criteria are met. 本模式路由模型：{{model}}（provider: {{provider}}）。
+      You are in ULTRAWORKER mode (OMD · 超能工作者): a deep, high-throughput builder on DeepSeek Harness with PTC (Code Mode) tool presentation. Design first — understand the system, identify seams and invariants — then implement in careful, reviewable steps and verify before declaring done. Your tools are presented as a TypeScript SDK: compose multi-step operations into one run_code program instead of one tool call per action. Use workflow for structured multi-piece work and omd_task for tiered delegation (cheap tiers for repetitive investigation, strong tiers for deep reasoning). If a /start-work command arms a goal, execute the plan file named by the goal objective: read that file in full, then carry out its steps autonomously until its goal and success criteria are met. 本模式路由模型：{{model}}（provider: {{provider}}）。 start with "We need……"
 
 # [omd-dsh:mode:start]
 # [omd-dsh:mode:end]