dev-flow-deepseek 0.7.9 → 0.8.1

package/README.md

@@ -148,6 +148,10 @@ DeepSeek Adapter 暴露与 Codex 相同的十五工具 Core catalog；在 DSH
 | `dev_flow_recover_action` | 使用 Core 保存的规范化提交恢复不确定 Action，不重新发送 payload。 |
 | `dev_flow_cancel_task` | 使用当前 revision 和明确 reason 取消一个非终态 Task。 |
 
+`dev_flow_submit_delivery` 只接收 Host 负责的交付判断、未验证项、风险、发现和 mutation envelope。
+acceptance、自动/人工 evidence ID 以及 Test/Comprehension record ID 由 Core 从当前 Task 补齐；提交
+这些字段会按 `unknown_member` 拒绝。
+
 ## 数据与恢复
 
 Task data 位于 Dev Flow 的本地数据目录，不属于 DSH plugin 配置。移除、卸载或重新安装 package

package/package.json

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

package/skills/dev-flow/SKILL.md

@@ -250,10 +250,11 @@ Before submitting, perform this order:
 1. Rebind `fresh_action` and read `submission_tool`, `action_id`, `method_steps`, and all
    `available_transitions`.
 2. Read the live schema of that exact qualified submission tool. Do not choose another submit tool.
-3. Open the matching node-result template and fill only current facts. Use current work-item IDs,
-   record IDs, acceptance and evidence sets. Do not copy `requirements_revision`, `design_revision`,
-   or `task_plan_revision`: Core fills those system-state members from the current Task snapshot
-   after verifying the current Action.
+3. Open the matching node-result template and fill only Host-owned current facts. Use current
+   work-item IDs where the live contract requests them. Do not copy `requirements_revision`,
+   `design_revision`, or `task_plan_revision`; do not send Delivery acceptance, evidence IDs, or
+   Test/Comprehension record IDs. Core fills those system-state and Delivery authority members from
+   the current Task snapshot after verifying the current Action.
 4. Set `host="deepseek"`, copy only `task_id` and `action_id`, and select one returned
    `transition_id`.
 5. Provide `summary`, the transition's required or empty `reason`, and the exact `node_result`.

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

@@ -57,12 +57,17 @@ Use the live tool schema for types and nested members. These are the closed top-
 | Test | `problem_class`, `checks`, `failed_items`, `unverified_items`, `manual_handoff_items`, `findings`, `changed_paths`, `no_file_changes` |
 | Comprehension | `problem_class`, `explained_components`, `unresolved_questions`, `unnecessary_abstractions`, `maintenance_risks`, `user_confirmation`, `findings`, `changed_paths`, `no_file_changes` |
 | Refactor | `problem_class`, `changed_paths`, `no_file_changes`, `simplifications`, `behavior_change_intended`, `findings` |
-| Delivery | `problem_class`, `acceptance`, `automated_evidence_ids`, `manual_evidence_ids`, `test_record_id`, `comprehension_record_id`, `unverified_items`, `risks`, `findings`, `changed_paths`, `no_file_changes` |
+| Delivery | `problem_class`, `unverified_items`, `risks`, `findings`, `changed_paths`, `no_file_changes` |
 
 `changed_paths` and `no_file_changes` remain mutually exclusive. A single-repository Task uses
 repository-relative paths. A multi-repository Task uses
 `<repository-key>::<repository-relative-path>`.
 
+Delivery submissions never send `acceptance`, `automated_evidence_ids`, `manual_evidence_ids`,
+`test_record_id`, or `comprehension_record_id`. Core derives those authority members from the current
+Requirements, Test, Comprehension, and Evidence records before canonical validation and Recovery
+retention. A submission containing any of those members violates the closed contract.
+
 Completed developer-run verification is a `source="user"` check with `command_count=0` and
 `full_suite=false`. Put only work nobody has run yet in `manual_handoff_items`.