REPORT: the 2026-10-26 attended release run; CHANGELOG: v0.344.0 RELEASED (floor 09:07:47 UTC). Docs only.

REPORT.md

@@ -1,28 +1,30 @@
-# REPORT — six fixes for v0.344.0, committed, not released (2026-10-25 night, unattended)
+# REPORT — controller v0.344.0 released (2026-10-26, attended release run)
 
-**Plain words first.** Six controller fixes are on `main`. None is released: the release is Monday's, attended
-(felhom.eu `STATUS.md`, the Monday list). MinAgent stays 0.158.1. Each fix was seen failing first (red-proof), and four
-were seen working on a throwaway test VM (BYO install on demo-hp, guest 9201, test images `0.344.0-rc.1`…`rc.3`). The
-test VM is destroyed.
+**Plain words first.** Every box runs 0.344.0. The global floor was set at 09:07:47 UTC (MinAgent 0.158.1) on the
+operator's yes, after the three test boxes moved through their per-box floors and the release-build checks passed. New
+installs start on it too: golden 0.344.0 was baked and vouched the same day, and a fresh install came up on 0.344.0
+with no update step. The file manager restarted once at the update, as the release notes say.
 
-## Each fix, before → after
+## Release
 
-| Row | Commit | Before | After | Live proof |
-|---|---|---|---|---|
-| R-1261 | `a79a292` | the line test held only one seeder; a record of an app removed while held stopped the 50 % rule for good; qBittorrent's limit went back into whatever slot its speed mode showed | every running seeder is held; a removed app's record is dropped; qBittorrent's hold names its slot (`up_limit` / `alt_up_limit` through `app/preferences`) | yes — two seeders held, 94.8 Mbit/s, both limits back; a mode switch mid-test never left 1 KiB/s |
-| R-1288 | `b5863a9` | a restore of a set-aside unit set the replaced install aside at the NEXT backup, with a second alarm | set aside at the restore, no alarm | yes — one set-aside mail only |
-| R-1282 | `b5863a9` | the 03:30 „restart later" for the media library was forgotten by a controller restart | the time is stored and resumed at start, once | no — unit tests only |
-| R-1286 | `838c834` | every restore hold read „a failed restore whose rollback also failed" | each hold reason has its own sentence (start gate, boot sweep, `--restore-holds`) | read only (Kimai on demo-hp: `unhealthy_stop`, the 10-14 power drill); the hold was NOT cleared |
-| R-1281 | `7ea942a` | an app container reached FileBrowser on `traefik-public` and signed in with a forged header (200) | FileBrowser is on its own `felhom-files` network (traefik, and OnlyOffice while linked); an app gets no answer | yes — forged header 200 → 000; the household's file manager still 200, no cookie 401; the move-off path seen |
-| R-1278 | `fbec5cb` | a new install of an app with a kept backup gave no hint | the install page says a backup is kept and links the restore page (HU + EN) | no — render tests per branch |
+- Image `felhom-controller:0.344.0`, sha256 `9435165dab85b1200d94157ec49d8be065889139e1831a5476dc68f4b9474b8a`, built
+  from `0a59044` (CI 2355 ✓). The rc `0.344.0-rc.4` (same commit) ran on 9202 first; 9202 is back on 0.343.0.
+- Per-box floors 0.344.0 for Tester 1, demo-hp, demo-felhom (08:15 UTC; each moved by the normal update path, healthy),
+  then the global floor (read back from the hub DB with its WAL and from the hub log), then the per-box floors cleared.
+- Fleet after the floor: demo-felhom, demo-hp, tester-1 report 0.344.0; Tester-2 has no box since 2026-10-04 (R-862).
 
-**Upgrade note (R-1281):** the rendered FileBrowser compose changes, so FileBrowser is re-created once on upgrade.
+## Checks on the release build (felhom.eu `documentation/audits/release-monday-2026-10-26/`)
 
-## Gates and CI (by commit hash, `jobs` endpoint)
+| Row | Check | Result |
+|---|---|---|
+| R-1281 | FileBrowser's networks; a forged header from apps; the household's files; OnlyOffice linked | on all three boxes FileBrowser only on `felhom-filebrowser` + `felhom-files`; qBittorrent/Sonarr/Radarr/Prowlarr → 000 (control: controller 404, traefik 301); Tester 1: dashboard → pass → cookie → listing 200, no cookie 401; OnlyOffice joined `felhom-files`, editor config 200, the OnlyOffice container fetched the document 200 — closed |
+| R-1282 | „Később", then a controller restart | the stored 03:30 kept (start-up line + settings.json) — closed |
+| R-1278 | install page with a kept backup | hint + link shown; none before or after — closed |
+| R-1286 | Kimai's install id; the hold sentences | id written 07:01:55Z; `holdWhy` released — closed |
+| R-1288 | released | proven live on the night's rig — closed |
+| R-1261 | released | the live line test is Tuesday (R-1250's dated check) — stays VERIFY |
+| D47 | upgrade count | 0 set aside on all three boxes; every app has an install id |
 
-`a79a292` 2340 ✓ · `b5863a9` 2343 ✓ · `838c834` 2346 ✓ · `7ea942a` 2347 ✓ · `fbec5cb` 2348 ✓ — all `run_attempt` 1.
-
-## Evidence
-
-felhom.eu `documentation/audits/night-2026-10-25/` (red-proofs per row, `rig/` live output) and
-`REPORT-night-2026-10-25.md` there.
+**Observation (NOT-A-FINDING):** on 9202's rc start the first FileBrowser round logged a WARN „could not join felhom-files
+(files.<domain> stays unreachable)" because FileBrowser was being re-created in the same second; it joined 2 s later.
+Log only, no event; the three release boxes logged no WARN.