docs: record draft CLI diagnostic guidance

docs/current_roadmap.md

@@ -297,16 +297,15 @@ stable.
   only; optional inputs are surfaced in wrapper-hint notes for explicit binding.
   Implementation plan:
   [`required-only wrapper inputs`](historical/superpowers/plans/2026-06-29-required-only-wrapper-inputs.md).
+- Completed: `wf draft set-input` rejects `local.x` targets before RPC and
+  shows the equivalent bare-target mapping.
+- Completed: `wf draft add-step --route` errors include declared outcomes and
+  direct add/remove repair guidance.
+- Completed: repeated idempotent `wf draft bind input/state -> local` behavior
+  is covered by regression tests.
 
 Planned challenge-driven UX follow-ups:
 
-- Improve `wf draft set-input` diagnostics when agents write local targets as
-  `local.x`; the command expects bare local field names such as `x`.
-- Improve `wf draft add-step --route` diagnostics when agents route undeclared
-  outcomes, for example `error=fail` on a single-`ok` capability. The error
-  should include declared outcomes and a compact repair hint.
-- Add an explicit re-invocation regression for idempotent
-  `wf draft bind input.x -> local.x` / `state.x -> local.x` repairs.
 - Design a separate composite-binding/data-shaping slice for cases such as
   mapping state fields into a structured `report` object. Do not hide this
   behind the existing path binding syntax without a deliberate model.

docs/wf_cli.md

@@ -328,7 +328,9 @@ wf draft compile concat_ws
 ```
 
 `set-input` maps graph source paths to node-local input fields:
-`input.text=text` means `input.text -> local.text`.
+`input.text=text` means `input.text -> local.text`. Targets are bare
+node-local field names: write `--map input.text=text`, not
+`--map input.text=local.text`.
 
 `set-output` maps node-local output fields to workflow state paths:
 `text=state.text` means `local.text -> state.text`.
@@ -396,7 +398,9 @@ the corresponding workflow input/state schema fields from the capability input
 schema.
 When the capability declares multiple outcomes, provide exactly one
 `--route OUTCOME=TARGET` for each declared outcome. Missing or unknown outcomes
-are rejected before the draft is mutated.
+are rejected before the draft is mutated. When `add-step --route` rejects an
+outcome, use the declared outcomes and repair text from the error. Remove
+unknown route entries and add one route for each missing declared outcome.
 
 ```bash
 wf draft add-step report_ws \

skills/wf-cli/SKILL.md

@@ -140,6 +140,10 @@ top-level `compiled_plan` key from the CLI output.
   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.
+- `set-input --map` is `GRAPH_SOURCE=BARE_LOCAL_FIELD`; never prefix the target
+  with `local.`.
+- For `add-step --route`, route only outcomes reported by `wf cap inspect` or
+  the command error's `declared_outcomes` field.
 - Do not confuse draft shape with raw plan shape: drafts use `steps/routes/use`;
   raw plans use `nodes/edges/node`.
 - Use `wf schema` to list workflow document/component shapes.

skills/wf-workflow/references/draft-workspaces.md

@@ -119,7 +119,8 @@ For single-field `input.*` and `state.*` sources, missing public output schema
 fields are projected automatically from the source schema.
 
 `set-input` direction: `input.text=text` means graph source `input.text` maps to
-node-local target `local.text`.
+node-local target `local.text`. Targets are bare node-local field names; never
+prefix the target with `local.`.
 
 `set-output` direction: `text=state.text` means node-local source `local.text`
 maps to graph target `state.text`.
@@ -162,7 +163,10 @@ wf draft validate <workspace_id>
   `--route OUTCOME=TARGET` for each outcome; when omitted and the capability
   declares a single outcome, that outcome routes to `__end__`. Multi-outcome
   capabilities require exact route coverage; missing or unknown outcomes are
-  rejected before mutation. It still requires explicit choices; if you do not
+  rejected before mutation. When `add-step --route` rejects an outcome, the
+  error reports declared outcomes and direct add/remove repair guidance. Remove
+  unknown route entries and add one route for each missing declared outcome. It
+  still requires explicit choices; if you do not
   know a map, inspect the capability or run validation rather than guessing.
   Explicit top-level `--input input.x=x` and `--input state.x=x` mappings
   project the corresponding workflow input/state schema fields from the