REPORT: the 2026-10-26 afternoon run. Docs only.

REPORT.md

@@ -1,30 +1,27 @@
-# REPORT — controller v0.344.0 released (2026-10-26, attended release run)
+# REPORT — controller v0.345.0 released (2026-10-26 afternoon, attended at the STOPs)
 
-**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.
+**Plain words first.** Every live box runs 0.345.0 (global floor 13:27:04 UTC, MinAgent 0.158.1, on the operator's yes).
+The one change: qBittorrent's 50 % upload rule now sets only the NORMAL limit. Before, with the household's „alternative
+speed" on, it changed the alternative limit or gave up for good (R-1292, closed).
 
 ## Release
 
-- 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).
+- Image `felhom-controller:0.345.0`, sha256 `2dc2c0a5ad34d08ebe4b8ae7b48708f00ff36ec36bc8249d6be7ecdff933a069`, from
+  `6bfb784` (CI 2368 ✓); the fix `2619191` (CI 2365 ✓). Test image `0.345.0-rc.1` on 9202 (then back to 0.343.0 as found)
+  and Tester 1.
+- Per-box floors for Tester 1, demo-hp, demo-felhom → each „Post-update startup: update successful", healthy; the
+  https-only check green on all three; then the global floor (read back from the hub DB with its WAL and the hub log);
+  the per-box floors cleared.
 
-## Checks on the release build (felhom.eu `documentation/audits/release-monday-2026-10-26/`)
+## The fix (R-1292)
 
-| 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 |
+`internal/upwatch/qblimit.go`: `QBLimiter` is `NormalLimit`/`SetNormalLimit` — `up_limit` through `app/preferences` (the
+R-1261 slot helpers), never `transfer/uploadLimit`/`setUploadLimit` (they act on the current speed mode's slot).
+Test `TestR1292_TheRuleSetsTheNormalSlotWhileTheAlternativeIsOn`, red-proved against the current-mode calls.
+**Live on Tester 1** (9202 has no tested line, so the rule never acts there): alternative speed ON with a 500 KiB/s
+alternative limit → the first tick set the normal limit to 5892096 B/s (50 % of 94.3 Mbit/s), the alternative stayed;
+after a switch back and one more tick the limit was still the box's own. Evidence: felhom.eu
+`documentation/audits/r1292-qb-normal-slot-2026-10-26/` (run 1 was an instrument failure in the probe, kept).
 
-**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.
+**Observation (NOT-A-FINDING):** 9202's first FileBrowser round after leaving 0.343.0 logged „could not join felhom-files"
+again (healed in 3 s; log only); every live box is past that move.