The hall keeps the night on the shared host: one job runs every game's rollup and backup and checks in with Sentry once for each

Eight cron monitors, two per game, watched eight scripts that run on the
same box at the same two minutes. hall-nightly.sh now runs the hall's own
rollup and every game's rollup at 00:12, and every game's backup at 07:23,
finding the games by their scripts in /usr/local/bin, and checks in once
for each job to the gamehall project's hall-rollup and hall-backup
monitors. The template's rollup and backup say by their exit status
whether they managed, the skipped backup included, and its deploy leaves
the game's own cron file off a host the hall schedules.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

CONVENTIONS.md

@@ -198,8 +198,9 @@ Every game gets the same tools, installed by `deploy.sh` on every deploy:
   the rollup's last week, the backup's last word, the box's vitals.
 - `<slug>-rollup.sh` nightly at 00:12 UTC: one JSON line a day of counts,
   no addresses. `<slug>-backup.sh` nightly at 07:23 UTC: rclone to the
-  shared Space, mirror plus dated snapshots pruned after 90 days. Both check
-  in with Sentry Crons so a missed night is noticed.
+  shared Space, mirror plus dated snapshots pruned after 90 days. On the
+  shared host the hall's `hall-nightly.sh` runs both for every game and
+  checks in with Sentry Crons once for all, so a missed night is noticed.
 - The reports desk (skill `<slug>-reports`): `pull-reports.sh` mirrors the
   desk to the Desktop with a digest; `report-reply.sh <ip> <id> <status>
   "text"` answers with `resolved`, `by-design` or `open`. A fix goes live