d4e91d4597
The stepwise-coding IR had no workflow-step seam node, so a per-task enabledWorkflowSteps entry (e.g. browser verification) would never execute. Add the seam node on the success path (steps -> workflow-step -> review, once post-foreach) and declare browser-verification as an optional step, matching the coding workflow. Covers the dead-toggle gap with resolver and engine execution-divergence tests.
552 B
552 B
@runfusion/fusion
| @runfusion/fusion |
|---|
| minor |
Add workflow optional steps: workflows can declare optional step templates that tasks toggle on/off per task, with a workflow-level default. The built-in coding and stepwise-coding workflows expose agent browser verification as an optional step (the stepwise workflow gains a pre-merge workflow-step seam so enabled steps actually run). Optional steps are authorable in the node editor, preserved across node-editor saves, and selectable from a steps dropdown in both the quick-add card and the full New Task modal.