# `WorkflowStem.Engines.StepwiseEngine`
[🔗](https://github.com/fosferon/workflow_stem/blob/main/lib/workflow_stem/engines/stepwise_engine.ex#L1)

Shim over `Mobus.Stepwise.Engine` for `:stepwise` workflows.

Since workflow_stem v0.2.0, this module delegates to the foundation
engine in `mobus_stepwise`. Consumers gain transitively:

  * telemetry span wrapping on all lifecycle phases
  * `{:wait, ...}` short-circuit in advance / entry-action stages
  * transition-policy hooks
  * projection-enricher hooks
  * `meta` passthrough to capability input
  * init-error propagation (`{:error, {:initial_entry_action_failed, ...}}`)

## Pipeline indirection

The engine reads `pipeline_mod` from `runtime_context` (set by
`WorkflowStem.Registry` for per-agent compiled pipelines). When no
pipeline is injected, defaults to `WorkflowStem.Pipelines.Stepwise`,
not the foundation's static pipeline, because workflow_stem components
carry additional action types (e.g. `:conversation`).

## Adapter configuration bridging

On application start, workflow_stem copies its own adapter config keys
(`:workflow_stem, :capability_runner_adapter` and
`:workflow_stem, :capability_runner_strict`) into mobus_stepwise's
application env so the foundation engine picks them up transparently.

---

*Consult [api-reference.md](api-reference.md) for complete listing*