docs: D4 Scenario E evidence — first post-deploy report cycle accepted (22:45 CEST, 200 from hub 0.30.0)

This commit is contained in:
2026-07-02 22:46:07 +02:00
parent 3d60b19b89
commit 5f230f6e11
+5 -3
View File
@@ -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