# REPORT — morning check, and hub 0.179.1 (2026-11-08, attended)

**Plain words first.** Last night's fixes worked. The N100 installed its Proxmox updates (no refusal) and a new kernel,
and restarted itself. demo-hp made its first local whole-box copy in 10 days. The hub still said the N100 „needs a
restart" after it had restarted; hub 0.179.1 fixes that. demo-hp does need a restart; the operator chose to wait for its
kernel step.

**Box facts (SSH).** demo-felhom: pve step `DONE upgraded=33` (05:32), kernel 7.0.14-28 one-shot boot 05:35, `KERNEL GOOD`
(default now 7.0.14-28), 0 host processes on replaced libraries, guest 9201 running. demo-hp: local backup `completed`
02:43 (`local:backup/vzdump-lxc-9201-2026_11_08-02_30_38`), pve step `upgraded=35`, no kernel step yet (7.0.14-28 pending),
systemd/sshd/kvm/zed/rrdcached on replaced libraries.

**Hub 0.179.1** (`osupdates.layerLine`): the host's last boot (crash guard `last_boot_at`) cuts the host layer's
reboot-needed run, less one minute of clock skew; a claim after the boot starts a new run. Feeds the System page and
the 14-day alarm. Test `TestRebootNeeded_ClearedByAHostBootAfterTheClaim`, red on two mutants; `go test ./...` green.
Deployed: image built from `ddbcabeb`, manifest `6b91a215`, ArgoCD sync of `Deployment/hub` only, rollout ok, pod
logs `felhom-hub 0.179.1 starting`. **Live (endpoint method — `GET /system` with CC's token, the page the operator
opens):** only demo-hp is listed. Evidence: `documentation/audits/hub-reboot-flag-2026-11-08/`.

**Remote restart buttons (the operator's question).** The host page has „Restart controller" and „Reboot the guest"
per guest (agent actions, D65). There is no button that reboots the Proxmox host; the host reboots only by the kernel
step. Not a defect — the agent's action list is closed by design.

**Registers.** No row opened or closed (the hub fault fixed in the session, size rule). System poster: no fact changed.