hub 0.146.0 live: STATUS + REPORT-hub-system-page (release and live read-back)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012qRErfCoiTkvDK9N5XHbzb

REPORT-hub-system-page.md

@@ -10,7 +10,7 @@ package counts came first. The red „Approve now (guest + host)" sat in the mid
 
 No sideways scroll at 1280 px or at 390 px (measured: `scrollWidth == clientWidth` at both widths).
 
-Built and tested only. **No deploy, no release, no box touched.** It ships with the next hub release.
+**Released as hub 0.146.0 on the operator's word („Release the new hub version", 2026-10-10).** No box touched.
 
 ## Baseline
 
@@ -83,6 +83,21 @@ scratchpad, from `system-fixture*.html`. Those pages are written by `SYSTEM_PAGE
   page, so I left it.
 - Teardown: provisioned nothing. No machine, no host, no hub change.
 
+## Release (hub 0.146.0)
+
+- Version commit `9fbdee83` (CHANGELOG heading). Image `gitea.dooplex.hu/admin/felhom-hub:0.146.0`, digest
+  `sha256:c31ffdd8…`. Manifest commit `2db785da`.
+- ArgoCD after a hard refresh: OutOfSync on `Deployment/hub` **and** on three Secrets (`gitea-creds`,
+  `healthchecks-config`, `umami-config`) and `Deployment/umami`. So I synced **only** `Deployment/hub` (the
+  runbook's R-925 rule). The others are untouched. Sync phase `Succeeded`; app health `Healthy`.
+- The pod runs `felhom-hub:0.146.0`, ready. Its log: `felhom-hub 0.146.0 starting`, `Listening on :8080`.
+- Live check through the ClusterIP with the operator's Basic auth (the endpoint the browser calls): `GET /system` →
+  200. All four parts are there; 4 boxes open in place; 9 forms, each with `_csrf`. Today's real page: 4 boxes amber
+  (three „root files behind the vouched agent's"; Tester 2 „needs a restart since 2026-10-04", „agent behind 0.142.0 →
+  0.150.0", „could not read: default kernel, root files"). „Nothing waits for your approval." The Docker 29.9.0-1 and
+  Proxmox 9.2.21 sets are still being tested (1 of 2 healthy nights on demo-felhom).
+- No button was pressed.
+
 ## Questions for the operator
 
 1. Look at the five screenshots. Is the order right (problems first, then approvals, then boxes)? OK, or what to change?

STATUS.md

@@ -2,7 +2,7 @@
 
 **Ready for the first real tester (Tester-2): yes. Tester 2 (a laptop) is off; nothing was sent to it.**
 
-**Updated 2026-10-10 (afternoon): hub 0.145.0; demo-hp, demo-felhom and Tester 1 run agent 0.154.0 and controller
+**Updated 2026-10-10 (afternoon): hub 0.146.0; demo-hp, demo-felhom and Tester 1 run agent 0.154.0 and controller
 0.307.0. The open-items list is at 126 (was 138). Reports: `REPORT-register-shrink-2026-10-10.md`, `REPORT-new-apps-2026-10-10.md`, `REPORT-release-2026-10-10.md`, `REPORT-break-the-circle-2026-10-09.md`, `REPORT-dooplex-survival-2026-10-09.md`, `REPORT-day4-2026-10-09.md`.**
 
 ## Saturday 2026-10-10 (late afternoon): the list is shorter, and one sheet for you
@@ -113,6 +113,10 @@ Not on the sheet, on purpose: R-832, R-904 and R-920 are deferred by your earlie
   displays. It is written down as an open item.
 ## Saturday 2026-10-10: released — the security hole is closed, and the kernel button shows
 
+- **Hub 0.146.0 is live** (you asked for it). The System page now shows problems first, then what waits for your
+  approval, then a short box table; the rest is under "Details". Checked live: the page opens, and today it says all
+  four boxes need a look (three: root files older than the approved agent's; Tester 2: a restart and an old agent),
+  nothing waits for you, and the Docker and Proxmox sets are still in test. Report: `REPORT-hub-system-page.md`.
 - **Hub 0.145.0 is live** (you were present). One box's key could change another household's mail settings. Now it
   cannot: checked live with Tester 1's key against demo-felhom — refused (403); the same key for its own household —
   accepted. Nothing changed in either household.