even MORE code review

stateful to not deadhang, graph context -> output, more explicit state errors, other misc changes idfk any of those good thing theyre fixed tho

docs/current_roadmap.md

@@ -62,8 +62,9 @@ implementation state.
   `WorkflowBuilder.prepare_subgraph()` and `WorkflowBuilder.resume()` make the
   local runnable/resumable path available without core-runtime plumbing.
   Saved interrupting artifacts can now pause and resume through
-  `run_deployment`/`resume_run` while the MCP server process stays alive.
-  Persisted resume remains future work.
+  `run_deployment`/`resume_run` for the duration of the MCP server process
+  (in-memory only). Persisted resume across process restarts remains future
+  work.
 - **Concurrent foreach**: implemented in core with explicit scheduling,
   reducer/merge semantics, item error policy, async handler batching, and
   quiescent interrupt behavior. Remaining work is polish and future reuse of

docs/schema_validation.md

@@ -37,6 +37,9 @@ Final workflow output has two projection modes:
 - If `Workflow.output` is empty, legacy projection copies same-named top-level
   state keys listed in `workflow.output_schema.properties`.
 
+Prefer explicit `Workflow.output` bindings for new workflows. The same-named
+state projection exists for compatibility with older plans.
+
 The projected payload is then validated against `workflow.output_schema`.
 
 ## Why This Matters