Both demo machines powered down for the move home, and MUTED on the hub

Operator is moving back from the vacation home. Guests shut down cleanly first
(checked: no running PVE task, no guest lock, no vzdump/restic in flight — the
"reboot mid-vzdump leaves a stale lock and the guest won't autostart" trap),
then the hosts. Confirmed off at the FABRIC rather than inferred from silence:
the tailnet is healthy, dooplex is up, and both peers report "offline, last
seen 1m ago". An absent ping is not evidence; an offline peer on a working
tailnet is.

Both customers blocked on the hub so the 30-minute host_stale and 60-minute
host_down transitions do not fire four false alarms during the drive.
IsCustomerBlocked gates every monitor plus the notification intake; it does NOT
gate config pull or report intake, so the boxes return normally on power-up.

STATUS.md carries a banner at the very top because the mute has a tail: while
blocked, a box that FAILS to come back is equally silent. Unblocking on arrival
is now the first thing anyone reads.

STATUS.md

@@ -10,6 +10,25 @@
 > *Rebuilt from the register on 2026-08-07, from 258 lines. The old "what shipped recently" log is what
 > the per-repo `CHANGELOG.md` files and the register are for, and is not restated here.*
 
+## ⚠ BOTH DEMO MACHINES ARE OFF AND MUTED — unmute them when they are home
+
+**Powered down 2026-08-09 14:08 CEST** for the move back from the vacation home. Guests stopped
+cleanly first (no vzdump was running, no locks), then the hosts. Confirmed off at the fabric, not
+merely unreachable: the tailnet is healthy and both peers report *"offline, last seen 1m ago"*.
+
+**Both customers are BLOCKED on the hub, deliberately, to stop four false alarms an hour into the
+drive.** Blocking gates every monitor and the notification intake; it does **not** gate config pull or
+report intake, so the boxes come back normally on power-up.
+
+> **THE TAIL, and it is the reason this banner exists: while they are blocked, a box that FAILS to
+> come back up is also silent.** When the machines are home and powered on, unblock them and confirm
+> both report:
+>
+> Hub → Customers → **demo-hp** → Unblock, and **demo-felhom** → Unblock.
+>
+> Then check both read ONLINE on Hosts. **Until that is done, the hub cannot tell you either box is
+> in trouble.**
+
 ## What works
 
 A blank machine boots the Felhom disc, installs itself unattended, and is claimed by the customer, who