dev-flow-deepseek 0.8.8 → 0.9.0

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

@@ -47,33 +47,48 @@ For a file-scope blocker, `dev_flow_resolve_blocker` also requires `choice` (`al
 `expand_scope`, or `reject`) and a non-empty `reason`. Omit both members for repository-recovery and
 automatic-verification blockers.
 
+For `task_relocation_pending`, provide the retained `relocation_id` and every
+`relocation_destinations[{key,repository_path}]`. For `workspace_history_conflict`, provide
+`history_resolution` with exactly `choice="accept_current_history"` and a non-empty `reason` after
+explicit review. File-scope, relocation, and history members are mutually exclusive; use only the
+branch selected by the current blocker and live schema.
+
 ## Node-result members
 
 Use the live tool schema for types and nested members. These are the closed top-level members:
 
 | Submission tool | Required `node_result` members |
 | --- | --- |
-| 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`, `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` |
-| 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>`. Contract paths use `/` separators on every Host;
-backslashes are invalid even on Windows.
+| Requirements | `problem_class`, `baseline`, `unresolved_questions` |
+| Design | `problem_class`, `baseline`, `findings` |
+| Tasks | `problem_class`, `baseline`, `findings` |
+| Implementation | `problem_class`, `completed_work_item_ids`, `deviations`, `findings` |
+| Test | `problem_class`, `checks`, `failed_items`, `unverified_items`, `manual_handoff_items`, `findings`, `budget_adjustment` |
+| Comprehension | `problem_class`, `explained_components`, `unresolved_questions`, `unnecessary_abstractions`, `maintenance_risks`, `user_confirmation`, `findings` |
+| Refactor | `problem_class`, `simplifications`, `behavior_change_intended`, `findings` |
+| Delivery | `problem_class`, `unverified_items`, `risks`, `findings` |
+
+The Host never submits file-effect fields. Core observes the dedicated worktree before applying an
+Action and computes the Action delta and current Task surface from Git facts.
 
 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`.
+The Tasks baseline contains `work_items` plus `verification_plan`. The plan contains `checks[]` with
+`name` and `rationale`, `initial_budget`, `full_suite_expected`, and
+`test_code_changes_expected`. Core fills only `design_revision`.
+
+Every Test submission includes `budget_adjustment`. Normal pass/failure transitions send `null`.
+`verification_budget_increased` sends a closed adjustment with `basis`, `additional_checks`,
+`additional_automatic_commands`, `allow_full_suite`, and `allow_manual_handoff`; all check and result
+lists stay empty and the transition reason gives the concrete need. Every check includes
+`full_suite_reason`: it is empty unless `full_suite=true`, in which case it records the current
+suite-specific risk.
+
+Completed developer-run verification is a `source="user"` check with `command_count=0`,
+`full_suite=false`, and `full_suite_reason=""`. Put only work nobody has run yet in `manual_handoff_items`.
 
 ## Requirements example
 
@@ -104,9 +119,7 @@ Completed developer-run verification is a `source="user"` check with `command_co
       "constraints": [],
       "assumptions": []
     },
-    "unresolved_questions": [],
-    "changed_paths": [],
-    "no_file_changes": true
+    "unresolved_questions": []
   }
 }
 ```