A 06:30 scheduled task that checks the build, syncs remote token numbers, commits the data, and writes a health record LAST — with an exit code that finally measures something.
The nightly is plain code only since the 2026-08-21 overhaul — the headless Claude briefing session retired with the briefing module, because the console IS the briefing now: every screen derives its own picture. What remains are the chores that preserve numbers nothing can recompute once transcripts age out.
The run's shape is defensive from top to bottom. The rebuild check runs in observation mode for its first week (-WhatIf: report what a rebuild WOULD do, touch nothing) before it earns the right to rebuild unattended. The console has to be running for the token sync, and nothing autostarts at login any more — so the run starts it itself (fire-and-forget, because a launcher that can raise a modal dialog at 06:30 hangs the task forever), uses it, and puts the machine back the way it found it. The data commit can be refused by the estate gate and the push can fail — neither is fatal, because by then the data is already on disk; both land in the health record instead.
The health record is the run's whole epistemology: it is written LAST, so its very existence means the run reached the end, and the process exit code is derived from it. Before this existed, the exit code read 0 every night while three briefings were lost, one run died outright, and nine remote syncs failed invisibly. The status bar renders the record as NIGHTLY · OK / MISSED / FAILED — a morning-glance answer to "did last night actually work?"