dev-flow-deepseek 0.7.0 → 0.7.1

package/README.md

@@ -11,21 +11,27 @@ macOS arm64 Core executable。
 
 | 项目 | 当前支持 |
 | --- | --- |
-| Package | `dev-flow-deepseek@0.7.0` |
+| 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.7.0](https://github.com/Innocent-children/dev-flow/releases/tag/deepseek-v0.7.0) |
+| Release | [deepseek-v0.7.1](https://github.com/Innocent-children/dev-flow/releases/tag/deepseek-v0.7.1) |
 
-`0.7.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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-flow-deepseek",
-  "version": "0.7.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

@@ -186,7 +186,8 @@ 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": [],
@@ -199,6 +200,11 @@ implementation result.
 ```
 <!-- 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
 {