feat(workflow): orchestrate resumable dataflow handoffs

README.md

@@ -20,10 +20,13 @@ fields, connected nodes, and permitted loops for correction and retry paths.
 Dataflow uses the same graph contract with its own acyclic transformation
 library.
 
-The current slice deliberately stops before executing process instances.
-Instance state, resumable transitions, human activities, retries, and event
-subscriptions must build on the pinned definition and versioned module
-capabilities rather than bypassing them.
+The executable runtime persists revision-pinned instances, append-only
+transition evidence, resumable human handoffs, retries, cancellation, and
+stable external output references. Dataflow nodes enqueue work through
+Dataflow's lifecycle capability; Workflow never imports Dataflow internals.
+Core's periodic worker reconciles linked runs after re-resolving the stored
+automation principal, while the operator surface exposes progress, review
+actions, evidence references, and direct navigation to Dataflow results.
 
 Definitions can be complete flows or non-runnable templates at system,
 tenant, group, or user scope. Policy resolves whether a definition can be
@@ -33,9 +36,10 @@ and records its hash, node-library version, source scope, actor, Policy
 decision, and effective ancestor limits.
 
 The start-node library distinguishes explicit user, API, scheduled, event, and
-parent-workflow starts. These are definition contracts only until the
-resumable Workflow instance runtime is implemented; the UI reports that
-limitation rather than presenting automation as operational.
+parent-workflow starts. Manual starts and Dataflow/human handoffs are
+operational. The other trigger and generic capability nodes remain explicit
+definition contracts until their event/schedule dispatchers and versioned
+operation providers are implemented.
 
 See [docs/CONCEPT.md](docs/CONCEPT.md) for the complete module concept.