v0.345.0: release header (R-1292, live on Tester 1); README

CHANGELOG.md

@@ -1,4 +1,9 @@
-## Unreleased (next: v0.345.0) — the 50 % rule owns qBittorrent's NORMAL limit only (R-1292) (2026-10-26) — committed, not released
+## v0.345.0 (2026-10-26) — the 50 % rule owns qBittorrent's NORMAL limit only (R-1292) — attended release run (afternoon)
+
+Live before the release: Tester 1 on `0.345.0-rc.1` with a throwaway qBittorrent, alternative speed ON (the household's
+alternative limit 500 KiB/s): the first tick set the NORMAL limit to 5892096 B/s (50 % of 94.3 Mbit/s), the alternative
+stayed 512000; after a switch back to normal and one more tick the limit was still the box's own (no „household").
+9202 cannot show the rule (no tested line). felhom.eu `documentation/audits/r1292-qb-normal-slot-2026-10-26/`.
 
 **MinAgent: 0.158.1** (unchanged).
 

controller/README.md

@@ -3585,7 +3585,7 @@ host's **weekly iperf3 line test** (the agent's `GET /host/line-test`, agent ≥
 the tunnel, R-1247) and a floor learnt from the nightly off-site push (one-second samples of the controller's own counter;
 best 10 s). The watch judges against the higher; the system settings page names the source. qBittorrent gets a default
 upload limit of 50 % of the TESTED line only (D41; no test yet → no limit; never over a household's own limit), and its
-page says so in one line. The rule owns the NORMAL limit only (`up_limit` through app/preferences, unreleased, R-1292): the household's
+page says so in one line. The rule owns the NORMAL limit only (`up_limit` through app/preferences, v0.345.0, R-1292): the household's
 „alternative speed" limit is never read or written by it. State: settings.json `upwatch`. Spike: felhom.eu `audits/SPIKE-upload-watch-2026-10-23.md`.
 
 **A box whose torrent app seeds all day** (v0.343.0, R-1250; `internal/upwatch/linehold.go`): the agent's test needs 10