feat(flow-debugger): carry site-side trace truncation on the route reply (ScadaBridge#54)

ScriptCallResult and RouteToCallResponse gain trailing Truncated/LogsTruncated,
filled from the site FlowTraceCollector after Complete(); RouteToCallResponseDto
fields 8/9 carry them (sitecommand regen). FlowDebugRunner ORs them into
FlowDebugRunResult on the script entry, and on the method entry through a new
optional truncation sink on RouteHelper.WithTraceSink (carried through every
With* clone). Previously a site run whose collector dropped rows came back as a
silently short list. Older sites send false.

Claude-Session: https://claude.ai/code/session_01GT67AEHd2Acv1YPwGfXEoV

docs/plans/2026-09-05-flow-debugger-design.md

@@ -170,7 +170,11 @@ attaches the list to the `ScriptCallResult` → `RouteToCallResponse` when `Trac
 collector applies `IAuditRedactor` inside `Add`, so the inline record is the same filtered event
 the writer persists, and it caps at `MaxTraceEventsPerRun` (500) **or** 1 MB of summed
 `DetailsJson` (`DefaultMaxBytes`), whichever comes first; beyond either bound it keeps the earlier
-events, sets `Truncated`, and the audit rows remain complete (arch-review F1). A site on an older build ignores
+events, sets `Truncated`, and the audit rows remain complete (arch-review F1). The site collector's
+`Truncated`/`LogsTruncated` ride back on `ScriptCallResult` → `RouteToCallResponse`
+(`RouteToCallResponseDto` fields 8/9, Gitea #54) and `FlowDebugRunner` ORs them into
+`FlowDebugRunResult` on both the script entry and (through `RouteHelper.WithTraceSink`'s truncation
+sink) the method entry, so a short site lane is labelled truncated. A site on an older build ignores
 `Trace`, returns no `TraceEvents`, and the UI labels its lane `site not traced (older build)`.
 `FlowStep` is a **central-side projection** (`Commons/Types/Debugging/FlowStepProjector`)
 computed from `AuditEvent` + `AuditDetails`; nothing serializes it.