[FEATURE] Carry-forward context/checklist template for recurring scheduled Routine runs

Summary

Each firing of a recurring scheduled Routine (e.g. a daily "check this repo" cron) starts from a completely blank session — it has no memory of what the previous run found or flagged. Please add an optional carry-forward context/checklist that persists a small structured summary from one run into the next, scoped per-Routine.

Current behavior

Recurring Routines like Electure daily check, Driveway daily check, Mamme mart daily check, and Daily repo review deploy fire on a schedule (daily / every few days), each tied only to the Routine's static prompt. Every run is a fresh session with no structured link to the prior run's output. There is no built-in place for "what did the last run flag, and is it still open" to carry forward automatically — the only way to check is to manually open the previous session and compare by hand.

Motivation

This is the day-to-day pattern for anyone using Routines for ongoing repo monitoring/maintenance over weeks or months (the same routine names recur in my session history going back to early May, run repeatedly against the same repos). Without carry-forward, following up on "did the thing flagged last Tuesday actually get fixed?" requires manually digging through old sessions — which defeats a large part of the value of having a recurring agent versus just running an ad hoc check whenever you remember to.

Proposed behavior

1. Optional per-Routine carry-forward doc. A Routine can persist a small structured summary (e.g. "last run's findings" + "still-open items") that gets automatically injected into the next run's context.
2. User-editable, not a black box. Surface the carry-forward doc so the user can adjust it between runs — e.g. manually mark an item resolved, or add a note — rather than it being an opaque internal cache.
3. Scoped per-Routine. Carry-forward context should never bleed across unrelated Routines (e.g. the electure routine's history shouldn't leak into the driveway routine's context).
4. Opt-in. Default off, so Routines meant to be fully stateless "fresh check every time" keep today's behavior; carry-forward is something you enable per Routine.

Why it matters

• Recurring monitoring/maintenance is a core use case for Routines. Without carry-forward, every run degrades into "run the same generic check with no institutional memory," which loses the main advantage of a recurring agent — tracking whether something flagged previously actually got resolved over time.
• Reduces manual cross-session comparison work, which currently falls entirely on the user.
• Makes long-running Routines (months of daily firings against the same repo) actually accumulate value instead of restarting from zero every time.

Related issues (adjacent, not duplicates)

• #34556 Feature Request: Persistent Memory Across Context Compactions — adjacent (persistent memory), but scoped to within-session compaction, not cross-run Routine carry-forward
• #22616 [FEATURE] Native automations with scheduled tasks and review queue (closed, stale) — closest prior ask in spirit; closed without this being addressed

Notes

• Should default off/opt-in per Routine to avoid surprising context bleed for Routines that are intentionally meant to be stateless one-off checks.
• The carry-forward doc should be small and structured (summary + open items), not a raw transcript dump, to avoid bloating every subsequent run's context window.