strikethroo 3.9.0 → 3.10.0

package/templates/harness/skills/st-execute-task/SKILL.md

@@ -136,8 +136,32 @@ Preserve all other frontmatter fields exactly.
 
 ### 8. Execute the task
 
-Deploy an agent using your internal Task tool. The agent MUST perform these
-steps in order:
+Before deploying a native agent, consult the bundled policy/dispatch runtime:
+
+```text
+scripts/dispatch-task-execution.cjs <task-file> <current-harness> <workspace> <plan-id> <task-id>
+```
+
+`<current-harness>` is the exact supported harness identifier running this
+skill; `<workspace>` is the project working directory. Read the one-line JSON
+result and act exactly once:
+
+- `native-default`: use the ordinary native Task dispatch below with no
+  execution-setting prose.
+- `native-override`: use native dispatch and explicitly require the subagent
+  to use the exact returned `model`. Mention `reasoningEffort` only when that
+  property is present.
+- `fallback`: visibly record the returned reason and detail, then use ordinary
+  native dispatch with no execution-setting prose. This is a pre-launch
+  fallback only.
+- `launched-success`: the external harness has completed the task; do not
+  dispatch a native agent. Continue directly with status and evidence review.
+- `launched-failure` (the script exits 1): treat it as an execution failure.
+  Do not dispatch or retry natively; follow steps 9–11's failed-status and
+  error-hook path.
+
+For either native dispatch outcome, deploy an agent using your internal Task
+tool. The agent MUST perform these steps in order:
 
 1. **Pre-flight validation**: Read and execute
    `<root>/config/hooks/PRE_TASK_EXECUTION.md` before starting any