docs: D4 authenticated Chrome pass complete (scenarios A-E), v0.30.1 follow-up noted

REPORT.md

@@ -6,7 +6,7 @@
 
 # REPORT — TASK-D4: Felhom Hub re-skin (design system v2, final surface) → hub v0.30.0
 
-**Date:** 2026-07-02 · **Deployed:** k3s felhom-system `deploy/hub` @ `felhom-hub:0.30.0` (rolled out, pod Running)
+**Date:** 2026-07-02 · **Deployed:** k3s felhom-system `deploy/hub` @ `felhom-hub:0.30.1` (0.30.0 + the badge no-wrap follow-up; rolled out)
 
 ## 1. Baselines
 
@@ -78,21 +78,32 @@ an HTTP 200 from the freshly deployed hub's `/api/v1/report`, proving ingestion
 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
+## 8. Chrome checks (authenticated pass — operator logged in)
 
-- `/login` renders on 0.30.0 with the retinted v2 button (screenshot) — reachable without auth.
-- **Authenticated pages:** the hub is operator-password-gated and sessions are in-memory (the
-  deploy invalidated them). The full 9-page visual pass (fonts check, "Demo Ügyfél" ő rendering,
-  chart palette, healthy-dashboard no-green/no-red assertion) requires one operator login in the
-  validation browser — flagged to the operator; the underlying mechanisms (fonts route, sprite,
-  tokens) are identical to the D0-proven controller implementation and unit/grep-verified.
+- **Dashboard (Scenario A/B):** two-tone "Felhom Hub", navy tokens, hairline rows. DOM-asserted:
+  **0 green** and **0 red** elements on the healthy fleet; OK = blue outline tag + dot
+  (`rgb(46,168,245)`); PENDING (Peti Debian) = quiet neutral tag with hollow dot; 0 radii beyond
+  0/2px/50%. (First load showed the OLD skin from the browser's 1-hour /style.css cache — a hard
+  reload fixed it; noted in Observations.)
+- **Fonts (Scenario C):** `document.fonts.check` true for both faces; woff2 served from
+  `/static/fonts/`; **0 external requests**; "Demo Ügyfél" renders in Plus Jakarta Sans
+  (screenshots — dashboard + customer page H1).
+- **Charts (Scenario D):** app_detail (nextcloud) memory trend — avg `#2EA8F5` filled, peak
+  `#8E7CE8` dashed, catalog-limit `#E0A93E` dashed; clearly distinguishable (screenshot).
+  Severity `warn` chips filled amber in Known Issues (exceptions loud).
+- **Scenario E visual:** dashboard LAST SEEN "4 min ago" + Controller 0.98.3 in the version
+  column — the post-deploy report cycle rendered.
+- Customers/customer_unified, Apps, Hosts (blue ONLINE tag, neutral NO REPORT), Configuration
+  (rendered read-only, nothing submitted; the artifact manifest shows agent 0.60.0 / golden
+  0.85.1 selected — unchanged) all render v2.
+- **v0.30.1 follow-up:** the pass caught multi-word badges (PENDING / NO REPORT) wrapping between
+  the CSS dot and label in narrow columns — fixed with `white-space: nowrap` on `.status-badge`,
+  built + deployed (manifest bumped).
 
 ## 9. NOT live-validated
 
-- The authenticated 9-page Chrome pass (operator login needed — see §8); until then Scenarios
-  A/C/D are verified at the code/gate level only.
 - warn/crit fleet states (no customer is currently degraded) — truth-table-tested only.
-- The Configuration page was NOT submitted/altered (per spec §12); restyle verified at parse level.
+- The Configuration page was NOT submitted/altered (per spec §12).
 
 ## 10. Observations (not acted on)