monero: check every five minutes again

The probes, the unit check and the public checks ran once a day with 26h
windows, justified as "a multi-week initial sync on a rotating disk". That
stopped being true: the node is synced, and a cold explorer page now renders
in 29s and a warm one in 0.2s - polling every 5 minutes is what keeps it warm.
A dead monerod could go unnoticed for a day.

Back to the standard 5m cadence and 11m heartbeat; the per-host
service_health override on monerod-box is gone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

ansible/infra/403_service_probe_registration.yml

@@ -45,15 +45,12 @@
       - {name: mempool-mariadb,  host: mempool_box_local}
       - {name: mempool-backend,  host: mempool_box_local}
       - {name: mempool-frontend, host: mempool_box_local}
-      # The two Monero probes push ONCE A DAY, not every 5 minutes, so they
-      # need a window wider than a day. 26h, not 24h: the window must exceed
-      # the push interval or a check that reports exactly on time races its own
-      # deadline and alerts on jitter. The timers are OnCalendar 05:00 and
-      # 05:30 with RandomizedDelaySec=900, so the true worst case is ~24h15m.
-      # Cadence lives in roles/{monero,xmrblocks}/defaults/main.yml; the two
-      # are one decision and must move together.
-      - {name: monerod,          host: monerod_box_local, heartbeat: '26h'}
-      - {name: xmrblocks,        host: monerod_box_local, heartbeat: '26h'}
+      # Every 5 minutes like the rest since 2026-10-17 (they were daily while
+      # the node synced on a rotating disk). Cadence lives in
+      # roles/{monero,xmrblocks}/defaults/main.yml; it and this window are one
+      # decision and must move together.
+      - {name: monerod,          host: monerod_box_local}
+      - {name: xmrblocks,        host: monerod_box_local}
       - {name: navidrome,        host: music_box_local}
       - {name: jar-lid-archive-staging, host: jar_lid_staging_local}