From 5f230f6e110a438403f8394165fabcd27e9e5f44 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Thu, 2 Jul 2026 22:46:07 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20D4=20Scenario=20E=20evidence=20?= =?UTF-8?q?=E2=80=94=20first=20post-deploy=20report=20cycle=20accepted=20(?= =?UTF-8?q?22:45=20CEST,=20200=20from=20hub=200.30.0)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- REPORT.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/REPORT.md b/REPORT.md index d6c5cd1..987a15e 100644 --- a/REPORT.md +++ b/REPORT.md @@ -72,9 +72,11 @@ deployment "hub" successfully rolled out hub-757d8dcb46-pq84j 1/1 Running 0 13s [INFO] Listening on :8080 (felhom-hub 0.30.0) ``` -Scenario E: the demo controller pushes reports every 15 min; the first post-deploy cycle's -`Hub report pushed successfully` (controller side) + the dashboard LAST SEEN refresh is captured -below / marked pending at write time — see §9 for the state at report time. +Scenario E **passed**: hub deployed 22:40 CEST; the demo controller's next 15-minute cycle at +`2026/07/02 20:45:19 UTC (22:45 CEST)` logged `Hub report pushed successfully (5423 bytes)` — +an HTTP 200 from the freshly deployed hub's `/api/v1/report`, proving ingestion end-to-end after +the re-skin (the controller only logs success on a 2xx). The dashboard LAST SEEN visual +confirmation joins the authenticated Chrome pass (§8). ## 8. Chrome checks