Session log — Auto-publishing session logs after midnight

7 May 2026 · Hasmukh with Claude · Hasmukh asked what is needed so every session log is published to documentation.mobilearn.africa just after midnight SAST, including sessions that span across the midnight boundary. Planning conversation only, no schedule set up yet. Two options on the table: same-night publishing with no editing window, or one-day-delayed publishing that gives a morning to edit before the log goes public.

Brief

Summary

Hasmukh asked what is needed so that every session log is published to documentation.mobilearn.africa just after midnight SAST, including sessions that span across the midnight boundary. The last published log on /overview/ is currently 3 May, and 13 logs from 1 to 6 May are sitting unpublished in the queue.

Decisions

None taken yet. Hasmukh has been given a recommendation and asked to choose between two options before anything is set up.

Changes

Changes made

No code, content, or schedules were changed in this session. This was a planning conversation only.

Follow-ups

Hasmukh to decide whether to (a) clear the 13-log backlog first, then (b) set up a nightly publishing schedule, or some other order.
Hasmukh to choose between same-night publishing (00:10 SAST, no editing window) and one-day-delayed publishing (gives a morning to edit before the log goes public).
Once decided, set up a scheduled remote agent that runs each night, finds any session log without a .published marker, publishes it as a permanent page under /overview/, surfaces it on the /overview/ index page in the same run, and writes the .published marker so the same log is never published twice.
Confirm the rule for sessions that cross midnight: one log file per calendar date the work touched, so a 23:00 to 02:00 session produces two files.