One small part per post: a probe, a daily job, a trick, a trap that cost an afternoon.
Scheduled jobs on a Mac belong in a launchd plist: they survive reboots, run as your user, and log where you can find them. One minimal plist, the commands to load it, and the privacy gotcha that makes a job under Documents fail with Operation not permitted.
A folder of source material, a scheduled job that turns one item into an article each morning and publishes it, and a human who reads every post for the first week before the job is allowed to run alone.
Editors drop finished files into a shared Google Drive folder. A cron job copies the folder to a public S3 prefix with rclone, so every file gets a stable URL that works in a browser, an API call or a spreadsheet, without anyone logging in.
Every ten minutes a script loads a product's checkout page and checks that the pay button is there. It posts to a chat channel exactly twice per incident: once when it goes down, once when it comes back. Never in between.
