felhom-controller/REPORT.md

REPORT — controller v0.345.0 released (2026-10-26 afternoon, attended at the STOPs)

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.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.

The fix (R-1292)

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): 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.