feat(cron): make skip_memory configurable via config.yaml

[YeuSheng]

Summary

Currently skip_memory is hardcoded to True for all cron jobs in cron/scheduler.py:2077:

skip_memory=True,  # Cron system prompts would corrupt user representations

This prevents users who want scheduled tasks to benefit from conversation memory (e.g., context-aware daily briefings, memory-informed status reports) from opting in.

Change

Replace the hardcoded value with a config.yaml lookup:

skip_memory=bool(_cfg.get("cron", {}).get("skip_memory", True)),

Default remains True — zero breaking change for existing setups. Users who want memory context in their cron jobs can set:

cron:
  skip_memory: false

Motivation

Some scheduled tasks (e.g., daily self-review, weekly retrospectives) benefit from knowing the user's accumulated preferences and context. The hardcoded True forces all cron sessions into a memory-agnostic mode regardless of user intent.

Test Plan

• Verified locally: cron jobs run with skip_memory=true (default) and skip_memory=false without errors
• Existing cron behavior unchanged when config key is absent

[alt-glitch]

This was generated by AI during triage.

Duplicate of #9825 — same one-line change in cron/scheduler.py making skip_memory configurable via config.yaml (cron.skip_memory, default True). #9825 is the earlier open PR and also includes regression tests. Tracking feature request: #9763.

[tonydwb]

Code Review Summary

Verdict: Approved

13-line change making skip_memory configurable via config.yaml. Default remains True (cron system prompts would corrupt user representations). Clean and backwards-compatible.

---

Reviewed by Hermes Agent

[teknium1]

Thanks for addressing a real cron-memory limitation. The current implementation needs a safer scope before it can be considered.

Problems

• cron/scheduler.py:3073 is an intentional isolation boundary: commit 005e0ec4 added skip_memory=True to prevent cron system prompts from corrupting user representations (bug(honcho): cron sessions write system instructions to Honcho as user messages, corrupting user representation #4052). A global cron.skip_memory: false would remove that protection for every cron job.
• This is broader than enabling a memory query path. With skip_memory=False, agent/agent_init.py:1363-1444 initializes both local memory and external providers; run_agent.py:3403-3424 then synchronizes each completed cron turn and queues provider prefetch.
• The one-line diff adds no regression coverage, DEFAULT_CONFIG entry, or documentation for the new setting.

Suggested changes

• Keep cron memory isolated by default and use an explicit per-job opt-in that separates provider tools from automatic prompt injection and turn synchronization.
• Add tests proving default cron jobs remain isolated and that any opted-in mode follows its intended read/write lifecycle.

Automated hermes-sweeper review.

[teknium1]

Closing as superseded by PR #91447 (merged as ef04d84) — cron memory is now enabled unconditionally rather than config-gated. @nightq's #9825 was the earliest PR in this cluster. Thanks for the contribution @YeuSheng.