`MAZENG-FT-30` · Monitor and review infrastructure executions

Feature intent

Users need trustworthy live and historical visibility into infrastructure executions, including after navigation or reconnection.

Why it matters

Users need trustworthy live and historical visibility into infrastructure executions, including after navigation or reconnection.

Users can follow an attributable execution in order and later review a sanitized, read-only history with an authoritative final status.

Correlate output with project, action, actor, and execution ID and stream events in order.
Show authoritative active, succeeded, failed, and cancelled outcomes across navigation and reconnection.
Retain read-only sanitized terminal history that excludes credentials and secret variable values.
Preserve the requested action type across credential-completion flows and derive final state from actual execution completion.

Acceptance

01
Output is correlated to project, action, actor, and execution ID and streams in order.
02
The UI shows authoritative active, succeeded, failed, and cancelled outcomes, including after navigation or reconnection.
03
History is read-only, sanitized, and excludes credentials and secret variable values.

None recorded.

Uncorrelated or out-of-order events can attach output and terminal state to the wrong execution.
Unsanitized history can retain credentials or secret variable values.
Incorrect action dispatch or asynchronous early completion can report a result for an action that did not actually finish.

No authoritative Architecture tasks are linked.