feat(central-ui): Flow Debugger drill-ins from Audit Log + Execution Chain; TraceAllCalls checkbox on the method form

'Open in Flow Debugger' (data-test open-flow-debugger) beside 'View execution chain' in
AuditEventDetail (rendered only with an ExecutionId) and beside 'View this execution in
the Audit Log' on the Execution Chain page — both target
/deployment/flow-debugger?executionId=… which replays on first render. ApiMethodForm gains a
'Trace all calls (Flow Debugger)' form-check under Timeout, loaded from and saved to
ApiMethod.TraceAllCalls on both the update and create paths, with the ~7-rows-per-call
guidance as help text.

Claude-Session: https://claude.ai/code/session_01GSLkkHKz9JrAtmJjmQK3cP
This commit is contained in:
Joseph Doherty
2026-09-06 00:33:37 -04:00
parent 254118a467
commit 66d5a67e4f
5 changed files with 135 additions and 2 deletions
@@ -164,5 +164,10 @@
@onclick="ViewExecutionChain">
View execution chain
</button>
<button class="btn btn-outline-secondary btn-sm"
data-test="open-flow-debugger"
@onclick="OpenInFlowDebugger">
Open in Flow Debugger
</button>
}
</div>
@@ -295,6 +295,16 @@ public partial class AuditEventDetail
Navigation.NavigateTo(uri);
}
/// <summary>
/// Flow Debugger replay drill-in (design 2026-09-05 §4): rebuilds this execution's
/// whole flow — inbound row, route call, traced site steps — as a swimlane.
/// </summary>
private void OpenInFlowDebugger()
{
if (Event.ExecutionId is not { } exec) return;
Navigation.NavigateTo($"/deployment/flow-debugger?executionId={exec}");
}
/// <summary>
/// Build a cURL command from an audit event. The URL comes from
/// <c>Target</c>; when the RequestSummary parses as