Completing one stuck step need not close a support episode

In per-flow support recovery, completing the currently stuck step does not necessarily complete the flow or close its support episode. If another required pre-completion step remains, first synchronize the durable issue, preserve the same issue and episode with its follow-up timer, then evaluate automation against the newly current step.

A state-projected workflow graph may keep a wait-for-progress node active and replace the displayed stuck step instead of rendering a separate historical partial-progress branch. Operators must not interpret that projection as evidence that no progress occurred. This rule is for bounded automations whose ticket lifecycle follows whole-flow completion. A remaining post-completion or document-phase step may not gate resolution, so tests must use a genuinely pre-completion requirement.