dev-flow-deepseek 0.7.1 → 0.7.2

package/README.md

@@ -11,14 +11,14 @@ macOS arm64 Core executable。
 
 | 项目 | 当前支持 |
 | --- | --- |
-| Package | `dev-flow-deepseek@0.7.1` |
-| Bundled Core | `0.6.0` |
+| Package | `dev-flow-deepseek@0.7.2` |
+| Bundled Core | `0.6.1` |
 | Platform | macOS arm64 |
 | Node.js | `>=24` |
 | DSH | `>=0.1.0-rc.6` |
-| Release | [deepseek-v0.7.1](https://github.com/Innocent-children/dev-flow/releases/tag/deepseek-v0.7.1) |
+| Release | [deepseek-v0.7.2](https://github.com/Innocent-children/dev-flow/releases/tag/deepseek-v0.7.2) |
 
-`0.7.1` 的 normal release 已通过 registry package 安装、显式触发、Core handshake、
+`0.7.2` 的 normal release 已通过 registry package 安装、显式触发、Core handshake、
 restart/resume、`DONE`、remove、uninstall、retained reopen 和 repository-unchanged 门禁。上表
 记录已验证的精确公开版本；下面的安装命令使用 npm `latest` dist-tag 获取当前最新稳定 package。
 
@@ -27,7 +27,7 @@ restart/resume、`DONE`、remove、uninstall、retained reopen 和 repository-un
 DSH 是前置 Host。`create-dev-flow` 独立发布后，用户只需指定真实 Profile，默认使用 `web`：
 
 ```bash
-npx create-dev-flow@latest
+npx @imotong/create-dev-flow@latest
 ```
 
 当前公开稳定制品尚未包含该新 manager package。发布前或诊断恢复时继续使用以下 Host 原生命令；
@@ -136,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；允许写入的 node result 提交精确 `changed_paths` 或 `no_file_changes`，artifact references 只作为证据。 |
+| `dev_flow_apply_action` | 使用当前 revision、Action identity、repository binding 和 closed payload 应用一次 Core 声明的 transition；允许写入的 node result 提交精确 `changed_paths` 或 `no_file_changes`，artifact references 只作为证据。输入 Schema 是单个封闭对象，`action_kind` 与 `payload` 在 Host callable 中完整可见；精确分支由 Core 校验，失败时返回字段级 `error.details[]`、`error.guard` 与一次 `correct_current_action` 纠正许可。 |
 | `dev_flow_cancel_task` | 使用当前 revision 和明确 reason 取消一个非终态 Task。 |
 
 ## 数据与恢复

package/package.json

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

package/skills/dev-flow/SKILL.md

@@ -239,8 +239,11 @@ and packaged template.
 
 1. Rebind the complete `fresh_action` and read its `action_kind`, `current_node`, `payload_contract`,
    `method_steps`, and all `available_transitions`.
-2. Read the live `mcp__dev_flow__dev_flow_apply_action` `inputSchema`; under `allOf`, choose the `oneOf` payload
-   branch whose `action_kind.const` matches the current action kind and source node.
+2. Read the live `mcp__dev_flow__dev_flow_apply_action` `inputSchema`. It is one closed object:
+   `action_kind` is a top-level `enum` of every action kind and `payload` is a closed object whose
+   `node_result` declares the union of every node result member. The schema does not narrow `payload`
+   by `action_kind`, so select the branch from `fresh_action.action_kind` plus
+   `fresh_action.payload_contract` and send only that branch's members.
 3. Open the corresponding marked template in `references/node-payloads.md`.
 4. Preserve the template's complete common envelope and `node_result` wrapper; replace only dynamic
    values with facts from the current Task, Action, user decision, repository work, and actual check.
@@ -304,10 +307,10 @@ apply_arguments = {
 that request inside an outer `payload` object. For an ordinary mutation, omit `recovery_apply` or
 send `recovery_apply=null`.
 
-If Core returns `INVALID_ARGUMENT`, treat it as a complete payload-contract rejection. Stop the
-current mutation, report the failing action/payload contract without private data, and do not delete
-fields, submit a second candidate payload for the same Action, automatically retry, or treat the
-result as transport uncertainty.
+If Core returns `INVALID_ARGUMENT`, treat it as a complete payload-contract rejection, not transport
+uncertainty. Use the bounded-correction section only when the complete result explicitly authorizes
+`correct_current_action`; otherwise stop and report the failing contract without private data. Never
+alter a field from source-code inspection or another guessed payload.
 
 ## Comprehension user interaction
 
@@ -425,6 +428,32 @@ uncertainty. Never convert or treat that domain error as missing or transport fa
 `retry_safe=false` and `action=none`, stop; do not call `mcp__dev_flow__dev_flow_get_next_action` or
 `mcp__dev_flow__dev_flow_apply_action`.
 
+## Bounded correction of the current action
+
+A complete structured domain error may carry field-level detail. `error.details[]` names the exact
+failing member as `path`, a closed `rule`, and a fixed non-sensitive `message`. A refused transition
+may instead carry `error.guard` with the Core `guard_id` and the same failure shape.
+
+Submit exactly one corrected payload for the same Action only when every condition holds:
+
+1. the original result is a complete structured Core domain error;
+2. `recovery.action` is `correct_current_action`;
+3. `recovery.retry_safe` is `true`;
+4. Task revision, action ID, process identity, source cursor, and repository binding are unchanged;
+5. the corrected request uses a new `request_id`;
+6. only members listed in `recovery.allowed_paths` change;
+7. the corrected value follows directly from the returned `rule`, with no source-code guessing;
+8. every other payload byte keeps the same meaning.
+
+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.
+
+Never treat these as correctable: an uncertain mutation result, a possible store commit, a missing or
+truncated response, a stale action identity, repository drift, an absent or inaccurate
+`allowed_paths`, or `INTERNAL_ERROR`. Those keep `retry_safe=false` and require the
+recovery-before-retry contract.
+
 ## Evidence and verification budget
 
 - Count verification commands exactly against Core's immutable budget.
@@ -434,6 +463,12 @@ uncertainty. Never convert or treat that domain error as missing or transport fa
 - Keep static inspection, simulated Core execution, user-performed evidence, and native automated
   evidence distinctly labelled.
 - Submit actual sources and outcomes. Never relabel failed, skipped, or unavailable work as passed.
+- `source=automated` uses `command_count` 1 to 20 and may set `full_suite` when the budget allows it.
+- `source=user`, `source=static`, and `source=host_observed` use `command_count=0` and
+  `full_suite=false`. Shell commands a person ran by hand belong in that check's `summary`; they
+  never consume the automatic command budget.
+- A verification the user already completed belongs in `checks` with `source=user`. Remove it from
+  `manual_handoff_items`; that list keeps only work nobody has executed yet.
 
 ## Blocked and terminal behavior
 

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

@@ -12,9 +12,12 @@ Before every ordinary apply:
    `method_steps`, and every `available_transition`.
 2. Select only a transition returned by that Action. Never submit `destination`, `next_node`,
    `next_cursor`, resume node, guard result, or caller classification.
-3. Select the matching `dev_flow_apply_action` `inputSchema` branch and use exactly the six common
-   payload members: `transition_id`, `summary`, `reason`, `artifacts`, `method_evidence`, and
-   `node_result`.
+3. The live `dev_flow_apply_action` `inputSchema` is one closed object. `action_kind` is a top-level
+   `enum` of every action kind and `payload.node_result` declares the union of every node result
+   member, so the schema does not narrow the payload by `action_kind`. Select the branch from the
+   fresh Action's `action_kind` and `payload_contract`, send only that branch's `node_result` members,
+   and use exactly the six common payload members: `transition_id`, `summary`, `reason`, `artifacts`,
+   `method_evidence`, and `node_result`.
    Set `reason=""` whenever the selected transition has `reason_required=false`; provide a nonempty
    reason only when the selected transition has `reason_required=true`.
 4. `required_evidence` and `artifacts` are different concepts. `repository_observation` is a Core evidence requirement, not an ArtifactReference role. When no real repository-relative process
@@ -36,8 +39,12 @@ Before every ordinary apply:
    evidence sets always come from the latest Task projection and are never guessed.
 9. Do not include repository facts, payload digests, raw command/output/environment data, or
    unknown members.
-10. `INVALID_ARGUMENT` is a completed Core domain rejection: stop, report a payload-contract error,
-    and do not probe with another payload or treat it as transport uncertainty.
+10. `INVALID_ARGUMENT` and `TRANSITION_NOT_ALLOWED` are completed Core domain rejections, never
+    transport uncertainty. When the result carries `error.details[]` or `error.guard`,
+    `recovery.action="correct_current_action"`, and `recovery.retry_safe=true`, submit exactly one
+    corrected payload for the same Action: change only the members in `recovery.allowed_paths`, derive
+    each corrected value from the returned closed `rule`, and use a new `request_id`. Stop after a
+    second failure and report the exact `path` and `rule`; never probe with a third candidate payload.
 
 <!-- node-payload-template:requirements:start -->
 ```json