docs: teach draft explain codes

2026-06-28 03:06:53 +07:00
parent df2882e606
commit c9e4d965e9
4 changed files with 17 additions and 2 deletions
@@ -108,6 +108,9 @@ top-level `compiled_plan` key from the CLI output.
 - Do not request unbounded traces.
 - Do not treat wrapper hints as semantic guarantees.
 - If validation fails, run `wf explain <code>` or `wf explain --input-file <validation-output.json>`.
+- For draft validation errors, run `wf explain <code>`. If routes point to a
+  missing step, create the target step first or repair routes with
+  `wf draft handle` / `wf draft branch`.
 - Do not use planning-session specs or implementation plans as user-facing runtime guidance.
 - Do not confuse draft shape with raw plan shape: drafts use `steps/routes/use`;
  raw plans use `nodes/edges/node`.