Improvement: Add Step-by-Step Debug Mode

[mdabdulkarimqa456-code]

What should be improved?

Users need better control and visibility while testing automation flows, especially for complex workflows.

Current behavior

Automation runs as a whole without showing step-wise execution.

Proposed change

1. Introduce step-by-step execution mode
2. Highlight currently executing node
3. Allow users to pause and inspect each step

Affected service

None

Before submitting

• I searched existing issues and this hasn't been suggested yet.

[yannickmonney]

Triaged — valid feature, keeping open. Today automations run whole-run (results land in the Executions tab) and "Dry run" is limited (not supported for file-based workflows yet). True step-by-step debugging (pause, inspect, step) is non-trivial because the engine is server-side/async, so this needs a small design pass on how to surface per-step state interactively. Assigned to me. Related: #1487 (per-node status indicators), #1484 (dry-run error feedback).

[yannickmonney]

Step-by-step debug mode (pause/inspect/step through an automation run) is a sizeable feature that depends on the runtime execution-feedback work in #1484/#1487 landing first (you need per-step status before you can step through it). Keeping needs discussion — let's settle the execution-feedback surface first, then layer stepping on top. Keeping assigned.