REPORT: live tail round-trip completed (see felhom.eu REPORT)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PSK5g6qYLknKj8u3QAFEr6

REPORT.md

@@ -59,11 +59,15 @@
 - Method note: server-side pipeline exercised end-to-end (report cycle → hub ingest → hub DB); the
   hub UI click-path is render-tested (the hub operator password is Viktor-only — CC cannot log in).
 
+## Live tail round-trip — COMPLETED (Viktor logged the browser in; CC drove the hub UI)
+
+Request clicked (14:35:20Z) → "tail pending" badge + transparency event → 14:37:34Z report's ACK armed
+the controller → 14:52:34Z report: `log-tail collected for felhom-controller: 200 lines` (push 2,545 B →
+18,849 B) → hub stored tail #1, pending badge cleared (consume-once), ordered 200-line viewer +
+Download .log verified in the browser. Details in felhom.eu/REPORT.md.
+
 ## Residuals / notes
 
-- The LIVE tail round-trip needs one operator click (hub → customer demo-felhom → App Telemetry →
-  "Request log tail"); the tail then lands within ≤2 report cycles (≤30 min). The whole mechanism is
-  unit- + API-test-proven on both repos including the consume-once red-proofs.
-- The live tail on 9201 would exercise the `FetchContainerLogTail` path (no customer app deployed on
-  the demo right now); the `stacks.GetLogs` path is unit-covered via the fetch seam.
+- The live tail exercised the `FetchContainerLogTail` path (no customer app deployed on the demo right
+  now); the `stacks.GetLogs` path is unit-covered via the fetch seam.
 - Do NOT request tails from Peti's box as part of this task — Viktor's call from the UI (per spec).