@devflow-core/dsh-devflow 0.6.1 → 0.7.0

package/README.md

@@ -33,7 +33,7 @@ npx @deepseek-ai/dsh plugin --profile web add @devflow-core/dsh-devflow
 
 - **devflow-\* 权威覆盖**：目标文件与包内源文件字节相同 → 跳过；不同 → 覆盖。
 - 源不再包含的 devflow-\* 残留（升级后旧文件）→ 删除（prune）。
-- **非 devflow 资产永不触碰**：用户自装的 skill（如 `atlassian`、`rtk`）、
+- **非 devflow 资产永不触碰**：用户自装的 skill（如 `atlassian`）、
   自定义命令/脚本一律保留，不删除不覆盖。
 - **preset 目录完全由插件管理**：`~/.dsh/.agent-presets/devflow-2/` 整目录归
   插件所有，目录内非包内文件（含手动备份如 `agent.cordis.yml.bak-*`）会在

package/RELEASE.md

@@ -101,7 +101,7 @@ npx @deepseek-ai/dsh plugin --profile web update @devflow-core/dsh-devflow
 - 字节相同的文件跳过（不覆盖用户 mtime）
 - 不同的文件覆盖（devflow-* 权威）
 - 源不再包含的 devflow-* 残留 prune
-- 非 devflow 资产（atlassian、rtk 等）永不触碰
+- 非 devflow 资产（atlassian 等）永不触碰
 - `~/.dsh/.agent-presets/devflow-2/` 整目录归插件管理，目录内非包内文件会被清理
 
 ## 常见错误对照表

package/assets/presets/devflow-2/README.md

@@ -1,20 +1,21 @@
 # DevFlow 2.0 — DeepSeek Harness Agent Preset
 
 A DSH agent preset that anchors the FIRST model request on the Minimal
-surface, then promotes into a full DevFlow session: Code Mode (PTC) on the
-wire, the complete DevFlow persona, and the DevFlow lifecycle guaranteed.
+surface, then promotes into a full DevFlow session: the native tool surface,
+the complete DevFlow persona, and the DevFlow lifecycle guaranteed.
 
 ## What it is
 
 - `agent.cordis.yml` — two-phase composition (adapted from the `liangshen`
   preset). Phase 1 shows only the one-line Minimal persona
-  ("You are a helpful software engineer assistant."), persistent
+  ("You are a helpful software engineer assistant."),
   `bash` + `str_replace_editor`, no runtime contexts, no injected pre-step
-  messages, and a 1024 output budget. The anchor gate (first minimal-like
-  reasoning block, 4-step fallback, or first-response release) then promotes
-  the session: the wire switches to Code Mode (a single `run_code` tool), the
-  full DevFlow persona is restored, and workspace instructions (AGENTS.md
-  digest) plus the skill catalog are deferred one step.
+  messages, and — since 2026-09-10 — no output-token cap. The anchor gate
+  (first minimal-like reasoning block, 4-step fallback, or first-response
+  release) then promotes the session: the wire switches to the deployment
+  default presentation (`native` — 33 tool schemas, no `run_code`, no generated
+  SDK section), the full DevFlow persona is restored, and workspace
+  instructions (AGENTS.md digest) plus the skill catalog are deferred one step.
 - `tool-bootstrap.mjs` — the two-phase bootstrap plugin (from
   `xiaobright/dsh-anchored-standard`, MIT, extended by `dsh-liangshen`),
   with a `phase1Persona` swap so the DevFlow persona only appears after
@@ -49,18 +50,48 @@ cp dsh/agent-presets/devflow-2/NOTICE                ~/.dsh/.agent-presets/devfl
 Start a new session in the web UI and pick **DevFlow 2.0** in the
 preset picker. The roster may need a refresh or restart to show a newly added
 preset. Existing sessions keep their old phase; the two-phase behavior applies
-to new sessions.
+to new sessions. The same holds for the 2026-09-10 prompt-budget changes: a
+running session keeps the policy it mounted with, so start a new session to
+pick them up.
 
 ## Caveats
 
 - `~/.dsh/.agent-presets/` is plugin-maintained: a DSH plugin upgrade may
   regenerate it. Re-run `npm run install:user -- --home ~/.dsh --write --force`
   (or re-copy) after upgrades.
-- Phase 1 uses the persistent (PTY-backed) Minimal `bash` shell. On Windows
-  builds where DSH's PTY backend is unavailable, phase-1 `bash` calls fail but
-  `str_replace_editor` still works, and the first-response release /
-  composition-drift guard keep the session usable (Code Mode `run_code` does
-  not need the PTY).
+- Phase 1 uses the Minimal `bash`: the persistent PTY-backed shell on
+  linux/darwin, or the stateless Git-Bash-backed `custom-bash.mjs` on Windows,
+  where the PTY backend is unavailable. `str_replace_editor` is the phase-1
+  editor on both paths, and the first-response release / composition-drift
+  guard keep the session usable if either bootstrap tool is missing.
+
+## Changes 2026-09-10 (prompt budget)
+
+Three independent defects were measured on real session logs and fixed:
+
+- **Phase-1 output cap removed.** `bootstrapMaxTokens: 1024` capped every
+  pre-promotion request, and output tokens INCLUDE reasoning tokens: under
+  `reasoningEffort: max` the first request was hard-truncated at 1024
+  (`finish_reason=length`, reasoning-only blocks with no text and no tool call),
+  which the web UI reports as "已达到输出 token 上限 / 回答被截断". The cap was
+  the anchor's forcing function for the short We-need block, not a safety limit;
+  the gate still promotes through its other three paths.
+- **`promotedPresentation: code` → `native`.** `code` does NOT mean "PTC only".
+  In `@deepseek-ai/dsh-tools`, `presentAs(mode)` attaches the collapse + SDK
+  sections for every mode except `native`, while `wireSchemas()` narrows the
+  wire to `run_code` only for `ptc`; `code` falls through to the default branch.
+  `code` therefore behaves as `both`: native schemas AND `run_code` AND the
+  generated SDK section — measured at 33,805 + 35,333 chars, i.e. one 36-tool
+  catalog paid for twice. `native` keeps the tools and drops the duplicate
+  (~-48% prompt per request). Use `ptc` instead to keep PTC batching at about
+  the same saving, at the cost of routing every call through a program.
+- **Three never-used tool families disabled** (0 calls across 30 recorded
+  sessions): `tool-jobs` (`job_kill`/`job_list`/`job_output`, 1,508 B + a
+  384-char guidance section that the same plugin contributes), the `workflow`
+  rows (4,067 B — the largest single schema), and `tool-ralph` (845 B). Each is
+  commented out in place with its restore note. The `subagent` family is kept
+  (it has real calls); `herdr_*` is kept because this deployment installs
+  `@deepseek-ai/dsh-tool-herdr` deliberately via `~/.dsh/cordis.patch.yml`.
 
 ## Customize
 

package/assets/presets/devflow-2/agent.cordis.yml

@@ -4,13 +4,18 @@
 #
 # TWO-PHASE PERSONA: the FIRST model request sees only the one-line Minimal
 # persona ("You are a helpful software engineer assistant."), the minimal tool
-# pair (persistent `bash` + `str_replace_editor`), NO runtime contexts and NO
+# pair (`bash` + `str_replace_editor`), NO runtime contexts and NO
 # auto-injected pre-step messages. After the anchor gate passes (first
 # minimal-like reasoning block, 4-step fallback, or first-response release) the
-# session promotes: the wire switches to Code Mode (PTC — a single `run_code`
-# tool), the FULL DevFlow persona below is restored (with {{model}}/{{cwd}}),
-# and workspace instructions (AGENTS.md digest) + the skill catalog are
-# deferred one step, then stay current.
+# session promotes: the wire switches to the deployment default presentation
+# (`native` — all tool schemas, no `run_code`, no generated SDK section), the
+# FULL DevFlow persona below is restored (with {{model}}/{{cwd}}), and
+# workspace instructions (AGENTS.md digest) + the skill catalog are deferred
+# one step, then stay current.
+#
+# The pre-promotion requests carry NO output-token cap (2026-09-10): the
+# former `bootstrapMaxTokens: 1024` truncated the first request under
+# `reasoningEffort: max`, because output tokens include reasoning tokens.
 #
 # This row MUST stay the FIRST row: the pre-step strip relies on waterfall
 # reverse-registration order so request #1 stays minimal-exact.
@@ -24,12 +29,33 @@
     anchorGate: true
     maxBootstrapSteps: 4
     promoteAfterFirstResponse: true
-    bootstrapMaxTokens: 1024
+    # DISABLED 2026-09-10: the phase-1 output cap collides with
+    # `reasoningEffort: max`. Output tokens INCLUDE reasoning tokens, so a
+    # 1024 cap hard-truncates the first request (finish_reason=length) and the
+    # web UI reports "已达到输出 token 上限 / 回答被截断". The cap is the
+    # anchor's forcing function for the short We-need block, not a safety
+    # limit: without it the gate still promotes via the anchor heuristic, the
+    # `maxBootstrapSteps` fallback, or `promoteAfterFirstResponse`.
+    # Re-enable only alongside a reasoningEffort low enough to fit under it.
+    # bootstrapMaxTokens: 1024
     # Core work set after a compaction, before re-promotion.
     compactionTools: [read, write, edit, glob, grep, todo_write, ask_user_question]
     deferredSources: [agent-instructions, skill-catalog]
     deferredGraceSteps: 1
-    promotedPresentation: code
+    # native (changed 2026-09-10, was `code`): `code` does NOT mean "PTC only".
+    # In @deepseek-ai/dsh-tools, presentAs(mode) attaches the collapse + SDK
+    # sections for every mode except `native`, while wireSchemas() narrows the
+    # wire to `run_code` ONLY for `ptc`; `code` falls through to the default
+    # branch, so it behaves as `both` — native schemas AND run_code AND the
+    # generated SDK section. Measured on a real session: 36 tool schemas
+    # (33,805 chars) plus a 35,333-char SDK section in the system prompt, i.e.
+    # one 36-tool catalog paid for twice (76,968 chars/request). `native` keeps
+    # the same 36 native tools and drops the duplicate SDK section
+    # (~40,065 chars/request, -48%). Trade-off: `run_code` disappears.
+    # Use `ptc` instead if the PTC batching surface is wanted: it saves about
+    # the same amount (drops the 33,805-char schema array instead) but forces
+    # every tool call through a program.
+    promotedPresentation: native
     # Aligned with liangshen 0.2.8 (issue #388): after promotion, replace the
     # full-text AGENTS.md injection with one non-imperative reference hint.
     instructionHint: true
@@ -157,8 +183,11 @@
 # registry is keyed by owning agent anyway. With the persistent shell, long
 # commands run through `&`; these controls still expose whatever the host
 # registry tracks.
-- id: tool-jobs
-  name: '@deepseek-ai/dsh-tool-jobs'
+# DISABLED 2026-09-10 (prompt-budget trim): `job_kill` / `job_list` /
+# `job_output` were never called in 30 recorded sessions. Uncomment to restore
+# background-job control. Long commands still work through `&` in the shell.
+# - id: tool-jobs
+#   name: '@deepseek-ai/dsh-tool-jobs'
 
 # ── skills ──────────────────────────────────────────────────────────────────
 
@@ -307,19 +336,25 @@
         enableRunInBackground: false
         maxDepth: provider-managed
 
-    - 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
+    # DISABLED 2026-09-10 (prompt-budget trim): the `workflow` schema is the
+    # single largest tool description in this catalog (4,067 chars) and was
+    # never called in 30 recorded sessions. Uncomment both rows to restore
+    # large multi-agent orchestration.
+    # - id: workflow-worker-thread
+    #   name: '@deepseek-ai/dsh-workflow-worker-thread'
+    #   config:
+    #     provider: spawn
+    #
+    # - id: tool-workflow
+    #   name: '@deepseek-ai/dsh-tool-workflow'
+
+    # DISABLED 2026-09-10 (prompt-budget trim): `ralph` was never called in 30
+    # recorded sessions. Uncomment to restore fresh-agent Ralph loops.
+    # - id: tool-ralph
+    #   name: '@deepseek-ai/dsh-tool-ralph'
+    #   config:
+    #     subagentProvider: spawn
+    #     maxRounds: 64
 
 # ── remaining model-facing rows ─────────────────────────────────────────────
 

package/assets/presets/devflow-2/preset.yml

@@ -1,3 +1,3 @@
 name: DevFlow 2.0
-description: DevFlow 开发工作流 + 梁神式两阶段锚定：首个请求只暴露一行 persona（You are a helpful software engineer assistant.）+ 最小工具对（持久 bash + str_replace_editor），无运行时上下文与任何注入；anchorGate 门控（首个 minimal-like 推理块或 4 步兜底）+ 1024 输出预算稳定锚定后，晋升为 Code Mode（单一 run_code），恢复完整 DevFlow 人设并自动激活 devflow-core 生命周期（Brainstorm → Spec/Cut → Plan → Build → Prove）与验证完成闭环；workspace 指令与技能目录延迟一步注入。
+description: DevFlow 开发工作流 + 梁神式两阶段锚定：首个请求只暴露一行 persona（You are a helpful software engineer assistant.）+ 最小工具对（bash + str_replace_editor），无运行时上下文、无任何注入、无输出 token 上限；anchorGate 门控（首个 minimal-like 推理块或 4 步兜底）晋升后切换为 native 工具面（33 个工具，无 run_code、无 SDK 重复表达），恢复完整 DevFlow 人设并自动激活 devflow-core 生命周期（Brainstorm → Spec/Cut → Plan → Build → Prove）与验证完成闭环；workspace 指令与技能目录延迟一步注入。
 order: 6

package/assets/presets/devflow-2/tool-bootstrap.mjs

@@ -29,10 +29,16 @@
  * `we` and no `let me`) or the `maxBootstrapSteps` fallback.
  * `promoteAfterFirstResponse` promotes a tool-less first response once it has
  * responded, and also releases an anchor-gated session when its first turn
- * ends (`turn/end`). With `promotedPresentation: code` the promoted catalog
- * is presented as Code Mode (PTC): the wire shows a single `run_code` tool
- * backed by the generated SDK, switched at the step boundary so the current
- * step's native calls are never interrupted. `deferredSources` and
+ * ends (`turn/end`). `promotedPresentation` is passed verbatim to
+ * `tools.presentAs(mode)`, so the promoted wire depends on which mode string
+ * the preset names: `native` = every tool schema and no SDK section; `ptc` =
+ * the `run_code` transport plus the generated SDK; `both`, and any other
+ * string — including `code`, which this preset used before 2026-09-10 and
+ * which `dsh-tools` falls through to the default branch — = every tool schema
+ * AND `run_code` AND the SDK section, i.e. one catalog paid for twice. Only
+ * `ptc` narrows `wireSchemas()` to the `run_code` transport. The switch
+ * happens at the step boundary so the current step's native calls are never
+ * interrupted. `deferredSources` and
  * `deferredGraceSteps` delay selected injected message kinds (workspace
  * instructions, skill catalog) for a few steps after promotion.
  *

package/assets/scripts/devflow-plan.js

@@ -369,20 +369,24 @@ function splitTasksV2(body) {
 }
 
 /** Validate one v2 task: files, change intent, acceptance, proof, and exclusion. */
-function checkTaskV2(task) {
+function checkTaskV2(task, enforceGranularity = true) {
   const missing = v2TaskFields.filter((field) => !v2FieldPatterns[field].test(task.body));
   const files = v2FieldBlock(task.body, "Files");
   const change = v2FieldBlock(task.body, "Change");
+  const acceptance = v2FieldBlock(task.body, "Acceptance");
   const verify = v2FieldBlock(task.body, "Verify");
   const notDoing = v2FieldBlock(task.body, "Not doing");
   const fileEntries = parseFileEntries(files);
   const invalidFiles = fileEntries.filter(({ match }) => !match).map(({ line }) => line);
   const unlocatedCodeFiles = findUnlocatedCodeFiles(fileEntries);
   const unresolved = findMatches(task.body, unresolvedPatterns);
-  const vague = findMatches([change, v2FieldBlock(task.body, "Acceptance"), verify].join("\n"), vaguePatterns);
+  const vague = findMatches([change, acceptance, verify].join("\n"), vaguePatterns);
   // v2 不强制精确改法；只要求 Change 说出可执行意图，具体实现归 Build。
   const missingChange = !implementationVerbPattern.test(change) || genericMechanicsPattern.test(change);
   const incompleteVerification = !hasVerificationExpectation(verify);
+  // 单结果保守代理：Acceptance 含分号即视为多交付单元；先剔除反引号代码片段，避免命令里的半角分号误报。语义判据（"且"连接独立结果、镜像合并）在技能指南，checker 只强制可静态判定的子集。
+  const acceptanceText = acceptance.replace(/`[^`]*`/g, "");
+  const multiResult = enforceGranularity && /[；;]/.test(acceptanceText);
 
   return {
     number: task.number,
@@ -393,6 +397,7 @@ function checkTaskV2(task) {
     unlocatedCodeFiles,
     missingChange,
     incompleteVerification,
+    multiResult,
     missingNotDoing: !notDoing,
     ok:
       missing.length === 0 &&
@@ -402,6 +407,7 @@ function checkTaskV2(task) {
       unlocatedCodeFiles.length === 0 &&
       !missingChange &&
       !incompleteVerification &&
+      !multiResult &&
       Boolean(notDoing)
   };
 }
@@ -409,13 +415,15 @@ function checkTaskV2(task) {
 /** Validate the v2 plan contract: slim header, task rows, Progress table, and Cut subtraction. */
 function checkPlanV2(body) {
   const tasks = splitTasksV2(body);
-  const taskResults = tasks.map(checkTaskV2);
-  const missingGlobal = v2GlobalFields.filter((field) => !v2FieldPatterns[field].test(body));
-  const cutBlock = v2FieldBlock(body, "Cut");
-  const missingRejected = !/Rejected\s*:\s*\S/im.test(cutBlock);
   const statusMatch = body.match(statusPattern);
   const status = statusMatch ? statusMatch[1].trim() : "legacy";
   const invalidStatus = statusMatch ? !validStatuses.includes(status) : false;
+  // 粒度代理只在活跃计划（draft/approved/in-progress）上强制；done 计划是历史记录，不重判，避免既有 v2 计划校验回归。
+  const enforceGranularity = status !== "done";
+  const taskResults = tasks.map((task) => checkTaskV2(task, enforceGranularity));
+  const missingGlobal = v2GlobalFields.filter((field) => !v2FieldPatterns[field].test(body));
+  const cutBlock = v2FieldBlock(body, "Cut");
+  const missingRejected = !/Rejected\s*:\s*\S/im.test(cutBlock);
   const progress = [...body.matchAll(progressRowPattern)].map((match) => ({
     number: Number(match[1]),
     state: match[3],
@@ -806,6 +814,7 @@ function report(body, filePath, json) {
           ...task.vague.map((match) => `vague ${match}`),
           ...task.invalidFiles.map((line) => `unclassified file ${line}`),
           ...task.unlocatedCodeFiles.map((line) => `missing file symbol/anchor ${line}`),
+          ...(task.multiResult ? ["Acceptance lists multiple results; split the task or state one observable result"] : []),
           ...(task.missingChange ? ["Change needs an executable intent verb"] : []),
           ...(task.missingNotDoing ? ["missing Not doing exclusion"] : []),
           ...(task.incompleteVerification ? ["Verify needs command/scenario and expected result"] : [])
@@ -1046,7 +1055,7 @@ function selfTest() {
     "Files:",
     "- Modify: scripts/devflow-plan.js | symbol: `checkPlanV2` | validate the slim contract",
     "Change: add v2 field validation and dispatch",
-    "Acceptance: v2 plans pass and legacy plans keep passing",
+    "Acceptance: v2 plans pass the slim contract",
     "Verify: run `node scripts/devflow-plan.js --self-test` expect exit 0",
     "Not doing: changing legacy validation",
     "",
@@ -1058,6 +1067,24 @@ function selfTest() {
   ].join("\n");
   if (!detectV2(validV2Plan)) throw new Error("Self-test expected v2 detection to pass");
   if (!checkPlan(validV2Plan).ok) throw new Error("Self-test expected valid v2 plan to pass");
+  const multiResultV2Plan = validV2Plan.replace(
+    "Acceptance: v2 plans pass the slim contract",
+    "Acceptance: v2 plans pass；legacy plans keep passing"
+  );
+  if (checkPlan(multiResultV2Plan).ok) throw new Error("Self-test expected a semicolon-joined Acceptance to fail");
+  const doneMultiResultV2Plan = multiResultV2Plan
+    .replace("Status: approved", "Status: done")
+    .replace("| 1 | Add v2 validation | todo | - |", "| 1 | Add v2 validation | done | run `node scripts/devflow-plan.js --self-test` |");
+  if (!checkPlan(doneMultiResultV2Plan).ok) {
+    throw new Error("Self-test expected a done plan to keep validating without granularity re-judging");
+  }
+  const codeSpanSemicolonV2Plan = validV2Plan.replace(
+    "Acceptance: v2 plans pass the slim contract",
+    "Acceptance: `node -e \"a;b\"` prints one result"
+  );
+  if (!checkPlan(codeSpanSemicolonV2Plan).ok) {
+    throw new Error("Self-test expected a semicolon inside a code span to stay valid");
+  }
   if (checkPlan(validV2Plan.replace(/Rejected:[^\n]*/, "Rejected:")).ok) throw new Error("Self-test expected missing Rejected to fail");
   if (checkPlan(validV2Plan.replace("| 1 | Add v2 validation | todo | - |", "| 1 | Add v2 validation | done | - |")).ok) {
     throw new Error("Self-test expected a done Progress row without evidence to fail");
@@ -1089,7 +1116,7 @@ function selfTest() {
   if (missingArtifact.length === 0) throw new Error("Self-test expected a missing requirement artifact to fail");
 
   console.log("DevFlow plan self-test passed");
-  console.log("Checked v2 and legacy plan contracts, Progress evidence, Cut Rejected, code-level fields, precise file locations, verification expectations, documentation-only exception, external-skill declaration, and plan landing guidance");
+  console.log("Checked v2 and legacy plan contracts, Progress evidence, Cut Rejected, single-result Acceptance granularity, code-level fields, precise file locations, verification expectations, documentation-only exception, external-skill declaration, and plan landing guidance");
 }
 
 const args = process.argv.slice(2);

package/assets/skills/devflow-build/SKILL.md

@@ -46,7 +46,7 @@ When saving a plan file, use `docs/plans/YYYY-MM-DD-<short-kebab-name>.md`, reso
 
 For multi-step work, tasks must cite the approved source, be small and verifiable, and follow the six-field contract (`Task` / `Files` / `Change` / `Acceptance` / `Verify` / `Not doing`) in `skills/devflow-plan/SKILL.md`. Legacy plans with `Change mechanics` and `Prewalk` stay executable under their own contract.
 
-No unresolved markers. `Change` states the executable intent and boundary; add exact mechanics only when the change crosses a module contract, is irreversible, or touches security or data boundaries. Otherwise Build chooses the smallest implementation and records it as Progress evidence. The verification step keeps its trigger/input, expected result, and command or manual scenario. A task whose files are all documentation paths is documentation-only. No "add tests" without naming the behavior, no "handle edge cases" without naming the edge case, no "similar to Task N" shortcuts.
+No unresolved markers. `Change` states the executable intent and boundary; add exact mechanics only when the change crosses a module contract, is irreversible, touches security or data boundaries, or the mechanism cannot be inferred from the task's named anchors by a different session or model. Otherwise Build chooses the smallest implementation and records it as Progress evidence. The verification step keeps its trigger/input, expected result, and command or manual scenario. A task whose files are all documentation paths is documentation-only. No "add tests" without naming the behavior, no "handle edge cases" without naming the edge case, no "similar to Task N" shortcuts.
 
 Close each task by writing back its `## Progress` row: `doing` when starting, `done` with the command and key result when its `Verify` passes. A `done` row without evidence fails the checker. On a legacy plan without a Progress table, report the same evidence in the completion message. When every task is `done`, advance the requirement row in `docs/requirements.md` to `built`.
 

package/assets/skills/devflow-plan/SKILL.md

@@ -18,7 +18,7 @@ Turn an A/B `CUT_PASS`-bounded approved design or confirmed Spec into one review
 1. Read only source material, code, tests, and conventions relevant to the approved scope. Load `skills/devflow-spec/references/spec-plan-methods.md` and `skills/devflow-plan/references/plan-methods.md` before applying Plan Pack mechanics.
 2. Map the intended touch set once: list the files and the responsibility each one carries. Reuse existing modules and name the intended file operation.
 3. Do the bounded investigation needed to write correct tasks. Keep that evidence in the conversation or in a learning card; it is not a plan field.
-4. Split independent deliverables into small, reviewable tasks. Each task carries `Files`, `Change`, `Acceptance`, `Verify`, and `Not doing` so an executor can act on it without reading another task.
+4. Split by delivery unit: one task = one independently verifiable deliverable and the smallest unit worth a fresh reviewer's gate — split only where a reviewer could meaningfully reject one task while approving its neighbor, and fold setup, configuration, scaffolding, and documentation into the task whose deliverable needs them. Split whenever `Acceptance` needs `且`/`and` to join two independently verifiable results; keep one task when the same rule mirrors across files — mirrored edits are one delivery unit, not one task per file. Each task carries `Files`, `Change`, `Acceptance`, `Verify`, and `Not doing` so an executor can act on it without reading another task.
 5. Write the plan using the required header, task contract, and `## Progress` table below.
 6. Self-review Cut fidelity, touch-set coverage, acceptance proof, scope exclusions, and Progress row count against the task count.
 7. Run `node scripts/devflow-plan.js <plan-file>` when the project-level checker exists. Otherwise resolve the user-level checker according to `core-methods.md` Script Path Resolution.
@@ -49,7 +49,7 @@ Files:
 - Create: <path> | new file | <responsibility>
 - Modify: <path> | <symbol or stable anchor> | <responsibility>
 - Test: <path> | <symbol or stable anchor> | <behavior proved>  # only when applicable
-Change: <what changes and its boundary; add the smallest mechanics only when the change crosses a module contract, is irreversible, or touches security or data boundaries>
+Change: <what changes and its boundary; add the smallest mechanics (pseudocode, exact replacement, or key fragment) only when the change crosses a module contract, is irreversible, touches security or data boundaries, or the mechanism cannot be inferred from the task's named anchors by a different session or model>
 Acceptance: <specific observable condition>
 Verify: <exact command or manual scenario, trigger/input, and expected result>
 Not doing: <scope excluded by this task>
@@ -77,15 +77,15 @@ Files:
 - Create: <path> | new file | <responsibility>
 - Modify: <path> | <symbol or stable anchor> | <responsibility>
 - Test: <path> | <symbol or stable anchor> | <behavior proved>  # only when applicable
-Change: <what changes and its boundary; exact mechanics only when the change crosses a module contract, is irreversible, or touches security or data boundaries>
+Change: <what changes and its boundary; exact mechanics (pseudocode, exact replacement, or key fragment) only when the change crosses a module contract, is irreversible, touches security or data boundaries, or the mechanism cannot be inferred from the task's named anchors by a different session or model>
 Acceptance: <specific observable condition>
 Verify: <exact command or manual scenario, trigger/input, and expected result>
 Not doing: <scope excluded by this task>
 ```
 
-Use only `Create`, `Modify`, and `Test` file-operation labels. `Create` rows use `new file`; every other row names a symbol or stable anchor. `Change` states the executable intent and its boundary in one or two lines; it does not restate current behavior, target behavior, call impact, or interfaces unless the task changes a cross-module contract. The Plan no longer classifies tasks by `Task type`: a task whose files are all documentation paths is documentation-only, and the checker treats it that way.
+Use only `Create`, `Modify`, and `Test` file-operation labels. `Create` rows use `new file`; every other row names a symbol or stable anchor. `Change` states the executable intent and its boundary in one or two lines; it does not restate current behavior, target behavior, call impact, or interfaces unless the task changes a cross-module contract. When the mechanism cannot be inferred from the task's named anchors — the common case when a different session or model executes the plan — `Change` carries the smallest runnable mechanics (pseudocode, exact replacement, or key fragment) so the executor acts without the author's session context. The Plan no longer classifies tasks by `Task type`: a task whose files are all documentation paths is documentation-only, and the checker treats it that way.
 
-Six fields per task is the whole contract: ordering, the touch set, the intent, the acceptance condition, the proof command, and the exclusion. Investigation traces, handoff facts, per-task worklists, architecture, tech stack, spec coverage, and comment locations are owned by other nodes or stay in the conversation. `Prewalk`, `File Structure`, `Interfaces`, `Current behavior`, `Target behavior`, `Change mechanics`, `Call impact`, and `Comments` are not part of the v2 contract; a plan that still carries them is treated as legacy.
+Six fields per task is the whole contract: ordering, the touch set, the intent, the acceptance condition, the proof command, and the exclusion. `Acceptance` states one observable result; a `；`/`;`-joined multi-result acceptance is a split signal and the checker fails it while the plan is active. Plan length has no fixed total line cap: it grows with the number of delivery units while every task keeps the six-field, one-result shape. Investigation traces, handoff facts, per-task worklists, architecture, tech stack, spec coverage, and comment locations are owned by other nodes or stay in the conversation. `Prewalk`, `File Structure`, `Interfaces`, `Current behavior`, `Target behavior`, `Change mechanics`, `Call impact`, and `Comments` are not part of the v2 contract; a plan that still carries them is treated as legacy.
 
 Keep one task understandable on its own. Do not use cross-task shorthand, generic test additions, unnamed edge cases, or cleanup entries. Name a test file only when the stated behavior needs one.
 
@@ -103,6 +103,8 @@ Plan generation does not repeat Cut, perform Build or Prove, prescribe independe
 | "The checker proves the architecture." | It proves structure only; the author must review scope and design consistency. |
 | "The plan is approved, so Cut can be skipped." | Plan generation requires an existing `CUT_PASS`; it cannot replace the earlier reuse and scope decision. |
 | "The task details can broaden the solution." | If a task exceeds the Cut Decision, return the scope-drift facts to `devflow-core`; do not directly enter Build. |
+| "Two results can share one task when they ship together." | Two independently verifiable results are two delivery units; split the task or reduce `Acceptance` to one observable result. |
+| "A different session or model will figure out the how." | If the mechanism cannot be inferred from the task's named anchors, `Change` must carry the smallest runnable mechanics; otherwise the handoff stalls. |
 
 ## Verification
 
@@ -114,6 +116,8 @@ Before leaving this skill, confirm:
 - [ ] Approved design or saved spec is cited as optional `Source`.
 - [ ] Header, tasks, and `## Progress` match the v2 contract; each task has six fields and no legacy field.
 - [ ] Every task is independently understandable and has no unresolved or vague placeholder.
+- [ ] Each task is exactly one delivery unit: no `；`/`;`-joined `Acceptance`, and a mirrored rule was not split per file.
+- [ ] Every task is executable by a different session or model from its six fields plus named anchors: a non-inferable mechanism carries the smallest runnable mechanics.
 - [ ] Progress row count equals task count; every `done` row carries evidence.
 - [ ] The checker passed when available.
 - [ ] The user reviewed the written plan.

package/assets/skills/devflow-plan/references/plan-methods.md

@@ -8,6 +8,17 @@ State the intended touch set once, before tasks: the files and the responsibilit
 
 The v2 Plan Pack has no `File Structure` table. The per-task `Files` rows are the touch set; a global table would only restate them.
 
+## Delivery Unit
+
+Split by delivery unit, not by file or by step: one task = one independently verifiable deliverable.
+
+- Splitting test: if `Acceptance` needs `且`/`and` to join two independently verifiable results, they are two delivery units — split them.
+- Mirror test: the same rule edited across several files is one delivery unit; do not split it per file.
+- Right-sizing test: a task is the smallest unit worth a fresh reviewer's gate — split only where a reviewer could meaningfully reject one task while approving its neighbor; fold setup, configuration, scaffolding, and documentation into the task whose deliverable needs them.
+- `Acceptance` states one observable result. The checker fails a v2 task whose `Acceptance` contains a `；`/`;` separator outside backtick code spans as the conservative static proxy for this rule; it applies while the plan is active (draft/approved/in-progress), while done plans stay historical records. The semantic tests above still govern mirrored and independently verifiable cases.
+- Handoff density: when the mechanism cannot be inferred from the task's named anchors — a different session or model executes the plan — `Change` carries the smallest runnable mechanics (pseudocode, exact replacement, or key fragment); otherwise it stays intent plus boundary.
+- No fixed total line cap: plan length grows with the number of delivery units; the six-field shape keeps each task slim.
+
 ## Task Rows
 
 Each task carries exactly six fields:
@@ -21,7 +32,7 @@ Verify: <command or manual scenario with trigger, input, and expected result>
 Not doing: <scope excluded by this task>
 ```
 
-`Change` states the executable intent. Add exact mechanics only when the change crosses a module contract, is irreversible, or touches security or data boundaries. Otherwise the executor chooses the smallest implementation inside the task boundary. This is the deliberate trade: the plan stops pre-deciding every edit, and Build regains bounded implementation authority. That trade is the fix for the bloated-plan problem, not a relaxation of proof.
+`Change` states the executable intent. Add exact mechanics (pseudocode, exact replacement, or key fragment) only when the change crosses a module contract, is irreversible, touches security or data boundaries, or the mechanism cannot be inferred from the task's named anchors by a different session or model. Otherwise the executor chooses the smallest implementation inside the task boundary. This is the deliberate trade: the plan stops pre-deciding every edit, and Build regains bounded implementation authority. That trade is the fix for the bloated-plan problem, not a relaxation of proof.
 
 Investigation evidence does not belong in the plan. Keep it in the conversation, or in a `.copilot/cards/` learning card when it is reusable across tasks.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devflow-core/dsh-devflow",
-  "version": "0.6.1",
+  "version": "0.7.0",
   "description": "DevFlow for DeepSeek Harness: devflow-2 agent preset + skills + commands + verification scripts, synced into ~/.dsh on host startup.",
   "type": "module",
   "engines": {