project
macOS service and job scheduler used to fire the pipeline at 07:00 and 14:00 daily, with the second slot acting as catch-up.
No evidence-backed relationships are recorded.
An operator running 160-plus launchd jobs lost four days of publishing when macOS "Optimize Storage" turned 69 article files into dataless stubs. Nothing crashed. Nothing alerted.
Reality
A one-week, two-repo field report from a solo developer: implementation capacity sat idle because nobody was re-judging stale tasks. Two of seven hand-dispatched tasks had already rotted.
Reality
An operator mapped every cron-style job on his Mac after noticing a metrics pipeline had been dead for two days. The count was never the problem. The missing inventory was.
Reality
A launchd job logged "no changes" and exited clean every Sunday while TCC blocked every write to ~/Documents. The success path and the total-failure path looked identical.
Reality
A scheduled Claude Code job skipped three runs in a row and reported success every time. The cheap fixes: check whether the PID in the lock file is alive, and alert on output rather than status.
Reality
A developer's nightly content pipeline kept reporting success while shipping 186-byte error messages. The fix was to stop reading logs and start checking whether a dated done-marker exists.
Reality
A developer lost a day of automated output to a daemon holding 46GB of compressed memory behind a 264MB resident set. Sorting top by RSS will never surface it.
Reality
One developer found seven dead MCP connections and could not say when they broke. His answer was measurement: a weekly snapshot that turns "feels slow lately" into a dated diff.
Reality
A dev.to writeup documents a six-day silent crash loop across 26 scheduled macOS jobs, and a single-command health check built around one useful contract: exit 1 if anything is red.
Reality
Every auto-generated Claude Code skill is injected into context on every conversation. One developer's weekly curator treats that like log rotation: stale at 30 days, archived at 90, nothing deleted.
Reality
An unattended video pipeline on macOS launchd stopped dying overnight after a startup wait went from 180s to 600s and a download timeout from 90s to 240s. The logic never changed.
Reality