[Feature Request] Some way to conditionally run a step, but still supply the last cached result to subsequent steps

[brianjenkins94]

Problem

There's no way to conditionally skip a step at runtime while still making its output available to downstream steps via prev and steps. Any conditional logic today must live inside the handler itself.

Proposed solution

{ cache: true } or { cache: "24h" } on a step config could tell the engine: for a given workflow input, if this step has already produced a result within the TTL, reuse it and skip re-execution.

Alternatives considered

Some additional thoughts on skipping can be found here.