Sentry: errors from the duel server, and cron check-ins for the rollup and backup

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0141G6xqLeNRYEtviLWSB5Up

deploy/waving-hands-rollup.sh

@@ -5,13 +5,25 @@
 # started and finished, and the box's vitals. Counts only: no addresses are
 # kept. The pulse reads it for trends the self-rotating access log loses.
 #   waving-hands-rollup.sh [YYYY-MM-DD]   (default: yesterday, UTC)
-#   Cron: /etc/cron.d/waving-hands, installed by deploy.sh.
+#   Cron: /etc/cron.d/waving-hands, installed by deploy.sh; SCHEDULE below
+#   must match it, because the Sentry monitor is told the same shape.
+#   Sentry Crons check-in: /root/.waving-hands-sentry-cron-rollup holds the
+#   check-in URL (absent = no check-ins).
 set -u
 OUT="/var/lib/waving-hands/rollup.jsonl"
 LOG="/var/log/waving-hands/rollup.log"
 DAY="${1:-$(date -u -d 'yesterday' +%Y-%m-%d)}"
+SCHEDULE="12 0 * * *"
+CRON_URL=$(cat /root/.waving-hands-sentry-cron-rollup 2>/dev/null || true)
+# The check-in carries the schedule: Sentry keeps a monitor only once told its shape.
+checkin() {
+  [ -n "$CRON_URL" ] && curl -sf -o /dev/null -X POST -H "Content-Type: application/json" \
+    -d "{\"status\":\"$1\",\"monitor_config\":{\"schedule\":{\"type\":\"crontab\",\"value\":\"$SCHEDULE\"},\"checkin_margin\":30,\"max_runtime\":10,\"timezone\":\"UTC\"}}" \
+    "$CRON_URL" || true
+}
 mkdir -p "$(dirname "$LOG")"
-python3 - "$DAY" "$OUT" <<'PY' >> "$LOG" 2>&1
+checkin in_progress
+if python3 - "$DAY" "$OUT" <<'PY' >> "$LOG" 2>&1
 import collections, datetime, glob, gzip, json, os, re, shutil, sys
 day, out = sys.argv[1], sys.argv[2]
 d0 = datetime.datetime.fromisoformat(day).replace(tzinfo=datetime.timezone.utc)
@@ -94,3 +106,4 @@ with open(out + ".tmp", "w") as fh:
 os.replace(out + ".tmp", out)
 print("%s rolled: %d people, %d requests, %d rooms" % (day, len(hips), human, created))
 PY
+then checkin ok; else checkin error; fi