dev-flow-deepseek 0.7.7 → 0.8.0

package/README.md

@@ -90,6 +90,10 @@ digest、method profiles、live schemas 和恰好十五个工具，再创建或
 Task 可选择 `plain`、`spec-kit` 或 `openspec` profile。Core 管理 current node、legal transitions、
 destination、Recovery、blocker 和 terminal outcome；Adapter 负责执行当前节点工作、呈现完整 Action
 并通过当前 Action 指定的提交工具转发节点结果。
+Design、Tasks 与 Implementation 节点结果不发送 `requirements_revision`、`design_revision` 与
+`task_plan_revision`；Core 确认当前 Action 身份后从同一 Task 快照填充。已证明零写入的
+`required_member_missing` 只可按 `allowed_paths` 和当前节点已有事实修正一次；需要新的用户决定时
+DeepSeek 停止并请求输入。
 
 ## 两仓声明、Workspace Root 与可选索引
 

package/package.json

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

package/skills/dev-flow/SKILL.md

@@ -250,8 +250,10 @@ 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 baseline
-   revisions, work-item IDs, record IDs, acceptance and evidence sets.
+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.
 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`.
@@ -382,6 +384,11 @@ condition holds:
 6. the corrected value follows directly from the returned `rule`, with no source-code guessing;
 7. every other submitted fact keeps the same meaning.
 
+A `required_member_missing` failure lists exactly the member Core could not find. Fill it from the
+facts the current node work already established. When the missing member needs a new user decision,
+such as a user confirmation that has not been obtained yet, stop and request that input instead of
+generating it.
+
 Stop immediately when the second submission also fails. Do not submit a third candidate payload;
 report only the exact `path`, `rule`, and that the bounded correction still failed. Never report
 either submitted field value.

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

@@ -5,6 +5,12 @@ is the exact input contract. The Host sends current work results; Core fills rev
 process identity, source cursor, repository binding, artifact roles, method step identity/order/status
 and the internal payload envelope.
 
+Core also fills the system-state members `requirements_revision` (Design baseline),
+`design_revision` (Tasks baseline) and `task_plan_revision` (Implementation) from the current Task
+snapshot after it verifies the current Action. Node templates omit them. A client that still sends
+the exact current value is accepted; a different value is refused as `current_value_required` with
+the exact member path.
+
 ## Common input
 
 Every ordinary submission contains exactly:
@@ -47,7 +53,7 @@ Use the live tool schema for types and nested members. These are the closed top-
 | Requirements | `problem_class`, `baseline`, `unresolved_questions`, `changed_paths`, `no_file_changes` |
 | Design | `problem_class`, `baseline`, `findings`, `changed_paths`, `no_file_changes` |
 | Tasks | `problem_class`, `baseline`, `findings`, `changed_paths`, `no_file_changes` |
-| Implementation | `problem_class`, `task_plan_revision`, `completed_work_item_ids`, `changed_paths`, `no_file_changes`, `deviations`, `findings` |
+| Implementation | `problem_class`, `completed_work_item_ids`, `changed_paths`, `no_file_changes`, `deviations`, `findings` |
 | 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` |