dev-flow-deepseek 0.6.0-beta.1 → 0.7.0

package/README.md

@@ -11,14 +11,14 @@ macOS arm64 Core executable。
 
 | 项目 | 当前支持 |
 | --- | --- |
-| Package | `dev-flow-deepseek@0.5.2` |
-| Bundled Core | `0.5.1` |
+| Package | `dev-flow-deepseek@0.7.0` |
+| Bundled Core | `0.6.0` |
 | Platform | macOS arm64 |
 | Node.js | `>=24` |
 | DSH | `>=0.1.0-rc.6` |
-| Release | [deepseek-v0.5.2](https://github.com/Innocent-children/dev-flow/releases/tag/deepseek-v0.5.2) |
+| Release | [deepseek-v0.7.0](https://github.com/Innocent-children/dev-flow/releases/tag/deepseek-v0.7.0) |
 
-`0.5.2` 的 normal release 已通过 registry package 安装、显式触发、Core handshake、
+`0.7.0` 的 normal release 已通过 registry package 安装、显式触发、Core handshake、
 restart/resume、`DONE`、remove、uninstall、retained reopen 和 repository-unchanged 门禁。上表
 记录已验证的精确公开版本；下面的安装命令使用 npm `latest` dist-tag 获取当前最新稳定 package。
 
@@ -89,6 +89,36 @@ Task 可选择 `plain`、`spec-kit` 或 `openspec` profile。Core 管理 current
 destination、Recovery、blocker 和 terminal outcome；Adapter 负责执行当前节点工作、呈现完整 Action
 并转发 closed payload。
 
+## 两仓声明、Workspace Root 与可选索引
+
+启动 DSH 时的 canonical `Workspace Root` 是完整权限边界，可以是两个 Git 仓库的非 Git 共同父
+目录。主仓库、附加仓库和 symlink 解析结果都必须位于该 Root 内。以 `/workspace` 为 Root、
+`/workspace/core` 和 `/workspace/docs` 为两个仓库时，可以发送：
+
+```text
+/dev-flow Use /workspace/core as primary repository key core and add repository key docs at /workspace/docs. Update core::internal/api.go and docs::reference/api.md, then run only the targeted checks.
+```
+
+路径必须替换为真实绝对路径。Scope 总数为一至八，创建后不可变；Adapter 在 task-bearing open 前
+拒绝 Root 外路径和 symlink escape。系统不扫描父目录、相邻目录、依赖或索引结果来发现仓库。
+单仓库请求不需要 key，继续使用普通相对路径；从任一参与仓库恢复仍返回同一 Task。
+DeepSeek 与 Codex 共用同一 Repository Scope、scoped path、Action 和唯一
+`repository_binding_digest` Core 合同；Host 权限检查不创建第二套流程状态。
+
+可选代码索引偏好来自只读配置：
+
+```json
+{
+  "codex": { "codebase_memory": false },
+  "deepseek": { "codebase_memory": true }
+}
+```
+
+文件路径固定为 `$HOME/.dev-flow/config.json`。文件不存在时偏好为 false，Dev Flow 不创建或修改
+它。true 只允许使用当前 DSH 会话中已经可见且可用的 codebase-memory；缺失、不完整或中途不可用
+时，DeepSeek 每个 Dev Flow 会话最多提示一次并立即回退到内置检索，不阻塞 Task，也不安装、配置
+或启动索引能力。索引覆盖不能放宽 Workspace Root，也不能决定 Scope、权限、Recovery 或流程流转。
+
 ## MCP 工具
 
 DeepSeek Adapter 暴露与 Codex 相同的六工具 Core catalog；在 DSH 中会使用限定后的 tool name，
@@ -96,11 +126,11 @@ DeepSeek Adapter 暴露与 Codex 相同的六工具 Core catalog；在 DSH 中
 
 | MCP 工具 | 作用 |
 | --- | --- |
-| `dev_flow_server_info` | 读取 Core identity、能力、process、method profile 和工具目录；有效 admission 后必须首先调用。 |
-| `dev_flow_open_task` | 为当前 canonical repository 创建新 Task，或恢复其现有 Task。 |
+| `dev_flow_server_info` | 读取 Core identity、能力、process、method profile、工具目录和 DeepSeek 有效索引偏好；有效 admission 后必须首先调用。 |
+| `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-beta.1",
+  "version": "0.7.0",
   "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
   }
 }
 ```
@@ -183,7 +191,9 @@ implementation result.
     "failed_items": [],
     "unverified_items": [],
     "manual_handoff_items": [],
-    "findings": []
+    "findings": [],
+    "changed_paths": [],
+    "no_file_changes": true
   }
 }
 ```
@@ -208,7 +218,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 +245,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 +300,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
   }
 }
 ```