R-1300 CLOSED: controller 0.345.1 (cloudflared 2026.10.3) on every box; R-1301 filed (N100 host clock, chrony fails at boot); 01: cloudflared follows Cloudflare's security notices

documentation/lived-in/n100.md

@@ -46,3 +46,9 @@ what happened, who noticed, and the register row it became. Prose here is not a
   route by name) reached the N100 by the normal update path at 12:04:45; `files.demo-felhom.eu` 200, the default login
   refused (401). No data touched. Register: fixed within the release, recorded in R-1126's close. Evidence:
   `audits/filebrowser-memory-ci-2026-10-17/release/box-walk.txt`. (CC)
+- **2026-10-26 — cloudflared 2026.10.3 (Cloudflare's eMudhra notice), and the host clock found 14 s slow.** Controller
+  0.345.1 arrived by the normal update path (per-box floor 20:06:04 UTC); the controller recreated cloudflared on
+  2026.10.3 by itself, the tunnel was down for about 4 s (a no-app name answered 530, then 404 again). While measuring
+  the gap the Proxmox host's clock read 14 s behind DooPlex and demo-hp: `chrony` has failed at every boot since at least
+  2026-10-16 („Could not send notification to $NOTIFY_SOCKET"); demo-hp, same package and options, runs it. Register:
+  R-1300 (the release), R-1301 (the clock). Evidence: `audits/cloudflared-2026.10.3-2026-10-26/` (`obs-n100-clock.txt`). (CC)