Recent sessions: token-expiry investigation, fantasy-football cron web-access fix, inflation/oil catchup, and two operator-news cron runs.
Targeted searches for token expiry, fantasy-football/web-access cron issues, [SILENT][LOCAL_PATH] patterns, and morning-briefing cron guidance.
Durable Learnings Saved
None. The major durable lessons were already encoded in skills/memory: live-source crons need web + terminal + file; cron ok does not prove visible/source-backed output; explicit Telegram topic targets are safer than origin; Google Workspace skill already documents Testing-mode OAuth refresh-token expiry and Gmail empty-body parsing.
Patterns Noticed
Recurring cron friction is now mostly verification/routing/tooling, not prompt quality: outputs can be ok while silent, misrouted, or generic due to missing tools.
The fantasy football job was fixed after its first generic run by adding web, terminal, and file; the relevant skills were already patched during that session.
Gmail-backed newsletter automation has two active weak points: OAuth refresh-token expiry and occasional empty newsletter body extraction.
Google/Gmail OAuth reauthorization for the Morning newsletter digest appears unresolved in the reviewed transcript until Moz completes the copied redirect URL/code exchange.
The recent operator-news crons are running with the right broad toolset and wiki-oriented pattern.
Automation / Cron Hygiene
Recommendation: complete Google OAuth reauth for ~[LOCAL_PATH] then verify with setup.py --check`; consider moving the Google Cloud OAuth app out of Testing mode to avoid ~7-day refresh-token expiry.
Recommendation: after the fantasy-football job’s next run, inspect the latest $HERMES_HOME/cron/output/710e0be4a36f/*.md to confirm it now cites live sources rather than saying it lacks web access.
No cron jobs modified tonight; no destructive actions taken.
Candidate Next Actions for Moz
Finish the Gmail OAuth redirect-code exchange so the Morning newsletter digest can read newsletters again.
If Stratechery/paid-newsletter empty bodies recur, patch/test google_api.py gmail get MIME recursion against the affected message.
Run a one-off fantasy football cron test after toolset correction if waiting for the next scheduled run is annoying.
Confidence / Guardrails
High confidence on cron/toolset and OAuth patterns from recent sessions and existing skills.
I intentionally did not save new memory or patch skills because the durable lessons were already present, and the remaining items are operational follow-ups rather than stable preferences.