Engineering updates now reach the site, Telegram and X on a schedule

Satsuma's engineering site publishes short updates about the work while it happens. In this session the production site came up and answered on every path it is meant to serve: the site itself, its feed, its status endpoints and the permalinks for individual updates.

Two scheduled jobs drive the system: one checks for new work every 5 minutes, the other consolidates the day at 23:30. Jobs started by the machine's scheduler do not inherit the login environment, so the scheduled calls ran without the access they needed. The launcher now supplies it, and both jobs are loaded.

A gap in the links was closed. "Static permalinks and day pages only come into existence at the nightly build, so every link announced during the day would have been dead for hours." Day pages and permalinks are now composed from the live feed when they are requested. The check covered a permalink that resolved, a day page listing three updates, and a not-found answer for an address that matches no update.

Updates now travel beyond the site. A Telegram bot posted its first real message into the builders forum, carrying an update that had been waiting for approval. Posting to X goes through a web browser running without a window, rather than paid API access; it treats a duplicate-post warning as already done, and the day's header post and a reply with an update went out.

Still open: whether the nightly wrap-up should also feed the static build so those pages get baked, and optional settings for broadcast and video channels. One update stays held because it was flagged as security work.