v0.342.0 (unreleased): the upload and CPU watch — an app that sends or burns far more than its own numbers explain is one operator-only alarm; the line learnt from the off-site push; qBittorrent's default upload limit (never over the household's)

internal/upwatch: exact per-container counters from the Docker Engine API, per-app judging (upload >= max(5 Mbit/s,
25% of the line) for 15 min; CPU >= max(150%, 50% x cores) for 30 min), explainers qBittorrent / Transmission / Plex,
app_unexplained_upload / app_unexplained_cpu + _cleared (hub 0.169.0). The off-site push is sampled once a second
for the line (a lower bound). qBittorrent limit = 50% of the line, the household's limit always wins. 20 red-proofs.
Spike + design: felhom.eu audits/SPIKE-upload-watch-2026-10-23.md, architecture/08 section 9. Not released.

controller/internal/web/i18n_cases_a_test.go

@@ -239,6 +239,7 @@ func i18nCasesA() []i18nCase {
 			d["MemorySupported"], d["MemoryReachable"] = true, true
 			d["MemoryAllocatedMB"], d["MemoryUsageMB"], d["MemoryMinMB"], d["MemoryMaxMB"] = 4096, 2048, 2048, 8192
 			d["PowerOffSupported"] = true // R-998: the power-off card with its button
+			d["UplinkLine"] = "47"        // the upload watch's measured line (the other three cases: still learning)
 			return d
 		}},
 		{"settings_system_failed", "settings_system", func() map[string]interface{} {