R-1199 reopened: a box with no list of its own reads the household's from the hub and adopts it, pushes its default once only when no household saved one; every push names its source; an empty saved list stays empty; R-1216 (D28 = A): the install page's swap sentence only when host swap is really short (shared case table); unreleased

CHANGELOG.md

@@ -1,3 +1,33 @@
+## Unreleased — a rebuilt box never overwrites the household's mail list (R-1199 reopened); the host-swap sentence only when swap is really short (R-1216, D28 = A)
+
+**MinAgent: 0.158.1** (unchanged). Needs hub ≥ 0.165.0 for the read (an older hub: the box pushes nothing at start).
+Task: the 2026-10-22 day brief.
+
+- **R-1199 reopened — the household's list is never overwritten.** v0.338.0 pushed the box's DEFAULT list at every start
+  when nothing was saved on the box; on a rebuilt box that overwrote the list the household had saved on its old box —
+  measured on the hub: demo-felhom's own 13 events became the 17 defaults at 07:54:55 UTC the morning it shipped, and the
+  push repeated at every start (it saved nothing locally). Now (`cmd/controller/prefs_sync_wiring.go`
+  `startupPrefsSync`): a list saved on this box is re-pushed as before (R-922) as the household's; with nothing saved
+  the box READS the hub's list (`notify.FetchPreferences`, `GET /api/v1/preferences`) — one the household saved is
+  ADOPTED as this box's list and nothing is pushed; otherwise the default is pushed ONCE as `source: default` and saved
+  here, so the next start sends nothing; a hub that cannot be read gets nothing. Every push names its `source`
+  (`SyncPreferencesAs`; the settings page = `household`; the debug re-push by whether a list is saved). The hub keeps a
+  household's list over any default (felhom.eu hub 0.165.0). Tests `TestR1199Reopened_A/B/C/AnUnreadableHubGetsNothing`
+  (cmd/controller), `TestR1199Reopened_TheWire` (notify) — A, B and the unreadable hub red-proved against v0.338.0's rule.
+- **Fixed without a row — an empty list read back as the defaults.** A household that unticked every mail saved `[]`;
+  `omitempty` dropped it and the getter turned the missing list into the 17 defaults, so the page showed every mail
+  ticked while the hub mailed by the empty list. Measured live: Tester 1's and demo-hp's `settings.json` hold only
+  `{"cooldown_hours": 6}`. Now `enabled_events` keeps `[]`, and a SAVED list with no events reads as empty (an unsaved
+  box still shows the defaults). With it: the three one-time add-only seeds are marked done on a fresh settings file —
+  unset, they ran at a new box's second start and re-added a mail the household had just switched off.
+  `TestR1199Reopened_AnEmptySavedListStaysEmpty`, red-proved both ways.
+- **R-1216 / D28 = A (operator 2026-10-22) — the install page's swap sentence only when swap is really short.** The rule
+  (`hostSwapRuleShort`, the same as the hub's `host_swap_short`): no host swap, or less than 90 % of min(the guest's
+  swap allowance, 8192 MB) — 8192 MB being the most Proxmox's installer gives (read from its `Install.pm`). The morning's
+  rule (host swap < the guest's RAM) would have told every household with a guest above 8 GB to call us; the 8 GB
+  soak's burst used 2.7 GB. Shared case table `internal/web/testdata/host_swap_rule_cases.json`, byte-identical in the
+  hub (felhom.eu `scripts/host_swap_rule_gate.py`); `TestR1216_HostSwapRuleCases` red-proved against the morning's rule.
+
 ## v0.338.0 (2026-10-22) — D22: every restore puts the household's data back exactly on failure, and after a power cut (R-1177, R-1195, R-1178, R-1180)
 
 **MinAgent: 0.158.1** (unchanged — the install page's swap sentence reads agent ≥ 0.162.0's swap numbers and stays