A 04:00 scheduled task that builds and pushes the Command Center snapshot, then commits the spend history nothing else can recompute.
The nightly is plain code only: no Claude session runs anywhere in it. It does two things. It runs the same builder the half-hourly task runs, so the phone page gets a fresh snapshot at 04:00, and it commits the day's spend rollups to the repo. Those rollups are the one thing here that cannot be recomputed later, because Claude Code deletes its session transcripts after about thirty days.
Nothing in it is fatal except the push. A data commit the estate's commit gate refuses, or a push that fails, leaves the numbers on disk and says so in the log, and the 05:00 backup check reports uncommitted data as a fault. The run's exit code is the push's, so a failed night is a failed task.
Its health shows where I already look. Until 25 Sep 2026 it wrote a health record for the desktop console's status bar, and it borrowed that console to sync spend from the servers. Both went with the console. Now the phone page is the check: its PC half carries the time it was built, and the age line turns red past two hours, so a nightly that stops, or a half-hourly push that stops, is seen the next morning without anything else to open.