Scheduled tasks always start a new session — option to resume an existing one?

Scheduled tasks (via SKILL.md under ~/.claude/scheduled-tasks/) always spawn a brand-new session/transcript on each run, even for the same recurring task. Over a month of daily runs (repo maintenance, backups, monitoring, etc.), this produces 100+ separate session files for what is conceptually one long-running routine.

This makes it hard to build tooling on top of session transcripts (e.g. indexing conversation history into a memory store) — each scheduled task run becomes a new, disconnected session ID rather than a continuation of a persistent thread.

Would it be possible to add an option for a scheduled task to resume/append to a designated existing session, instead of always starting fresh? Even an opt-in flag per task would help.