README §8e + REPORT: R-1250 hold, live proof on demo-hp

controller/README.md

@@ -3538,6 +3538,14 @@ best 10 s). The watch judges against the higher; the system settings page names
 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. State: settings.json `upwatch`. Spike: felhom.eu `audits/SPIKE-upload-watch-2026-10-23.md`.
 
+**A box whose torrent app seeds all day** (unreleased, R-1250; `internal/upwatch/linehold.go`): the agent's test needs 10
+quiet minutes, which such a box never gives. When the agent reports `waiting_for_quiet` (agent ≥ 0.165.0) and
+qBittorrent or Transmission runs, the 15-minute tick writes `upwatch.line_test_hold` (the app's limit as the app stored
+it), holds the app at 1 KiB/s (Transmission 1 kB/s), calls `POST /host/line-test/run` (about 55 s) and puts the old limit
+back — the household's own included; a change made during the test stays. A killed controller puts it back at start
+(`RecoverHold`, before any rule); the 50 % rule skips while a record exists. Proven on demo-hp with a real seed (felhom.eu
+`audits/dooplex-alarms-2026-10-24/`).
+
 ### 8d. Storage that knows its physical disks — the internal place, partitions (v0.317.0 build A, v0.318.0 build B)
 
 Design: felhom.eu `architecture/16-storage-physical-identity.md`. The host agent decides which physical disk a place sits on;