dev-flow-deepseek 0.6.0 → 0.7.1

package/README.md

@@ -11,21 +11,27 @@ macOS arm64 Core executable。
 
 | 项目 | 当前支持 |
 | --- | --- |
-| Package | `dev-flow-deepseek@0.6.0` |
-| Bundled Core | `0.5.1` |
+| Package | `dev-flow-deepseek@0.7.1` |
+| Bundled Core | `0.6.0` |
 | Platform | macOS arm64 |
 | Node.js | `>=24` |
 | DSH | `>=0.1.0-rc.6` |
-| Release | [deepseek-v0.6.0](https://github.com/Innocent-children/dev-flow/releases/tag/deepseek-v0.6.0) |
+| Release | [deepseek-v0.7.1](https://github.com/Innocent-children/dev-flow/releases/tag/deepseek-v0.7.1) |
 
-`0.6.0` 的 normal release 已通过 registry package 安装、显式触发、Core handshake、
+`0.7.1` 的 normal release 已通过 registry package 安装、显式触发、Core handshake、
 restart/resume、`DONE`、remove、uninstall、retained reopen 和 repository-unchanged 门禁。上表
 记录已验证的精确公开版本；下面的安装命令使用 npm `latest` dist-tag 获取当前最新稳定 package。
 
 ## 安装与验证
 
-先安装 DSH，再在一个可写目录中把 Dev Flow 安装到真实 profile。下面使用 `web`；需要其他
-profile 时修改 `PROFILE` 的值，不要把 `<profile>` 原样输入 shell。
+DSH 是前置 Host。`create-dev-flow` 独立发布后，用户只需指定真实 Profile，默认使用 `web`：
+
+```bash
+npx create-dev-flow@latest
+```
+
+当前公开稳定制品尚未包含该新 manager package。发布前或诊断恢复时继续使用以下 Host 原生命令；
+需要其他 Profile 时修改 `PROFILE` 的值，不要把 `<profile>` 原样输入 shell：
 
 ```bash
 npm install -g @deepseek-ai/dsh@latest
@@ -55,7 +61,7 @@ process、Skill、guard 和 MCP child 合成到指定 profile。安装后按照
 | `dsh --profile "$PROFILE" --dump-config` | 输出 profile 的有效配置，用于检查 `dev-flow-deepseek` bundle contribution 是否存在；不会修改 Dev Flow Task。 |
 | `dsh plugin --profile "$PROFILE" remove dev-flow-deepseek` | 从指定 profile 移除 package 与 bundle contribution；保留 Task data、目标 Git 仓库和 Codex-owned state。 |
 
-更新或重新安装时，按照 profile lifecycle 停止使用该 profile，然后执行：
+统一生命周期入口负责升级、修复、重装、卸载和清空后重装。Host 原生更新或重新安装仍按以下顺序：
 
 ```bash
 PROFILE=web
@@ -130,7 +136,7 @@ DeepSeek Adapter 暴露与 Codex 相同的六工具 Core catalog；在 DSH 中
 | `dev_flow_open_task` | 为 Workspace Root 内显式声明的主/附加仓库创建一个 Task，或从任一参与仓库恢复同一 Task。 |
 | `dev_flow_get_task` | 读取持久化 Task；可附带 operation probe 获取 Recovery assessment。 |
 | `dev_flow_get_next_action` | 读取当前节点的权威 Action、验证预算、method steps 和全部合法 transition。 |
-| `dev_flow_apply_action` | 使用当前 revision、Action identity、repository binding 和 closed payload 应用一次 Core 声明的 transition。 |
+| `dev_flow_apply_action` | 使用当前 revision、Action identity、repository binding 和 closed payload 应用一次 Core 声明的 transition；允许写入的 node result 提交精确 `changed_paths` 或 `no_file_changes`，artifact references 只作为证据。 |
 | `dev_flow_cancel_task` | 使用当前 revision 和明确 reason 取消一个非终态 Task。 |
 
 ## 数据与恢复

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-flow-deepseek",
-  "version": "0.6.0",
+  "version": "0.7.1",
   "private": false,
   "description": "Explicit DeepSeek Harness adapter for the Dev Flow process graph.",
   "license": "Apache-2.0",

package/skills/dev-flow/references/node-payloads.md

@@ -21,12 +21,14 @@ Before every ordinary apply:
    artifact exists, submit `"artifacts": []`.
 5. Allowed ArtifactReference roles are only `requirements`, `design`, `task_plan`,
    `implementation`, `test`, `comprehension`, `refactor`, `delivery`, and `other_process`.
-   For every ArtifactReference path, work-item `expected_paths`, Implementation `changed_paths`, and
-   Refactor `changed_paths`, use an ordinary repository-relative path for a single-repository Task
+   For every ArtifactReference path, work-item `expected_paths`, and node-result `changed_paths`, use
+   an ordinary repository-relative path for a single-repository Task
    and `<repository-key>::<repository-relative-path>` for a multi-repository Task. The key must
    already belong to the immutable Core Scope. Do not add a payload field or a second digest.
-6. Preserve the complete `node_result` branch wrapper. Never flatten baseline fields or encode an
-   array as prose.
+6. Preserve the complete `node_result` branch wrapper. Every standard node result reports exact
+   `changed_paths` or `no_file_changes`; exactly one of a nonempty path list or
+   `no_file_changes=true` describes the current effect. Artifact references remain evidence and do
+   not replace this mutation envelope. Never flatten baseline fields or encode an array as prose.
 7. Submit exactly one MethodEvidence item for every current Action method step, in Action order.
    For completed `plain` work use `"status": "plain_fallback"` and `"capability": ""`.
 8. Replace every value beginning `placeholder-` and every exemplar revision/ID with the current
@@ -59,7 +61,9 @@ Before every ordinary apply:
       "constraints": ["placeholder-constraint"],
       "assumptions": []
     },
-    "unresolved_questions": []
+    "unresolved_questions": [],
+    "changed_paths": ["specs/placeholder-feature/spec.md"],
+    "no_file_changes": false
   }
 }
 ```
@@ -93,7 +97,9 @@ closed `baseline` object.
       "complexity_justification": [],
       "risks": []
     },
-    "findings": []
+    "findings": [],
+    "changed_paths": ["specs/placeholder-feature/plan.md"],
+    "no_file_changes": false
   }
 }
 ```
@@ -129,7 +135,9 @@ Use the current requirements revision. The field `complexity` is forbidden; the
         }
       ]
     },
-    "findings": []
+    "findings": [],
+    "changed_paths": ["specs/placeholder-feature/tasks.md"],
+    "no_file_changes": false
   }
 }
 ```
@@ -178,17 +186,25 @@ implementation result.
   "node_result": {
     "problem_class": "none",
     "checks": [
-      {"source": "automated", "name": "placeholder-check-name", "status": "passed", "summary": "placeholder-check-result", "command_count": 1, "full_suite": false}
+      {"source": "automated", "name": "placeholder-check-name", "status": "passed", "summary": "placeholder-check-result", "command_count": 1, "full_suite": false},
+      {"source": "user", "name": "placeholder-developer-check", "status": "passed", "summary": "placeholder-developer-result", "command_count": 0, "full_suite": false}
     ],
     "failed_items": [],
     "unverified_items": [],
     "manual_handoff_items": [],
-    "findings": []
+    "findings": [],
+    "changed_paths": [],
+    "no_file_changes": true
   }
 }
 ```
 <!-- node-payload-template:test:end -->
 
+Completed developer-run verification is a `source="user"` check with `command_count=0` and
+`full_suite=false`; the human command is described in `summary` and never charged to the automatic budget.
+`manual_handoff_items` contains only bounded checks still awaiting user execution. Once the developer reports a
+completed result, record the user check and remove that item from `manual_handoff_items`.
+
 <!-- node-payload-template:comprehension-complexity:start -->
 ```json
 {
@@ -208,7 +224,9 @@ implementation result.
     "unnecessary_abstractions": ["placeholder-unnecessary-abstraction"],
     "maintenance_risks": [],
     "user_confirmation": null,
-    "findings": ["placeholder-matching-complexity-fact"]
+    "findings": ["placeholder-matching-complexity-fact"],
+    "changed_paths": [],
+    "no_file_changes": true
   }
 }
 ```
@@ -233,7 +251,9 @@ implementation result.
     "unnecessary_abstractions": [],
     "maintenance_risks": [],
     "user_confirmation": {"source": "user", "status": "passed", "summary": "placeholder-explicit-user-verdict-summary"},
-    "findings": []
+    "findings": [],
+    "changed_paths": [],
+    "no_file_changes": true
   }
 }
 ```
@@ -286,7 +306,9 @@ No AI or method capability may create the passing user confirmation.
     "comprehension_record_id": "placeholder-current-comprehension-record-id",
     "unverified_items": [],
     "risks": [],
-    "findings": []
+    "findings": [],
+    "changed_paths": [],
+    "no_file_changes": true
   }
 }
 ```