Unattended publishing cycle proven on the merged scheduling code

Satsuma's engineering site is fed by a job that reads finished work sessions, judges whether each one is fit to publish, writes the update and announces it. A pull request adding a nightly push and self-contained scheduling was merged, and the job now runs from the merged code.

One test run on that code completed a full unattended cycle: it found a new group of sessions, judged it, published the update, added it to the day's Telegram message and posted the reply on X. Six triggers from other sessions arrived during the run; the lock skipped all six, and the lock file cleared on exit. A separate check, using temporary instrumentation that was then removed, confirmed that the job's own model calls no longer set off the trigger that starts it.

The schedule is now fixed: "Every five minutes and at every session end: ingest, judge, publish, announce. One run at a time, site writes only when something changed." At 23:30 each night the same run executes, and then the day's archive is committed and pushed.

The 23:30 nightly push has not been shown to run yet.