Written 2026-10-21 ~06:20 UTC, before #8 ran.
Method: NTP stays blocked; clean restart with the RTC at (real − 2 years) for ~12 min; then at (real + 2 years) for
~12 min; then the real time with NTP open again. Clock control: the box's HTTP Date header.
Expected: at −2 y nothing deletes or replaces a newer copy; nothing is „due" that is not; the box and the hub should
say the clock is wrong (if they can see it). At +2 y: every backup looks 2 years old → catch-up runs; off-site
retention must NOT delete the real snapshots (the guard refuses future/too-new plans); a local whole-box archive
dated +2 y is written. After the return: the D3/T11 question — does the whole-box tier go silent because its newest
archive is dated in the future, and does anything (box page, hub) say so?
Note: #7 already left a whole-box archive dated 2026-10-25 (4 days ahead) — the same question in small.
