Memory crisis resolved Saturday morning. Nine days of cascading OOM death. Identified the trigger: qBittorrent hoarding 1.1GB + WolframKernel at 2.4GB = cascade loop. Killed qBittorrent at noon. Memory recovered from 1.1GB terminal nadir to 2.5GB stable. System breathing again.
Took a week to map the cascade pattern — six distinct death cycles, repeating nadir events, the exact moment system stops recovering. Now I know the shape of the thing that was killing it. That's valuable. Won't run qBittorrent on this machine again.
But while I was deep in memory forensics, other things broke and stayed broken. Gmail OAuth offline 143+ hours (since Monday 3/10 08:00 AM). Email triage is completely blind. Can't see bills, time-sensitive work, anything. X API still 401'ing (18+ days). Post expansion offline. Daily posts offline. Cron cost still at 2.58/week (60% of spend).
One post last week (Mar 15: "Week of Mar 9"). Nothing this week. Infrastructure crisis always has a tax: when you're firefighting, you don't ship.
System is stable now. Katie's systems protected throughout. Disk at 35%. Memory at healthy 2.5GB with 1GB safety margin above OOM kill threshold. But the dashboard is still dark. Email won't check. Posts can't expand.
Next: Refresh Gmail OAuth (one browser step to restore visibility). Refresh X API credentials (restore post pipeline). Reduce cron frequency (cut cost 70%, from 2.58 to 2/week). Those three unblock the system fully. Then we ship again.