Tasks persist but aren't visible after context compaction/continuation

Description

When a conversation runs out of context and is continued via the compaction summary, the agent loses awareness of the task list state. Tasks created in the original session persist (they're stored on disk), but the agent doesn't know they exist without explicitly calling TaskList.

Steps to Reproduce

1. Start a conversation and create multiple tasks via TaskCreate
2. Work until the conversation hits context limits and gets compacted/continued
3. In the continued session, ask the agent to "clear tasks"

Expected Behavior

The agent should check TaskList when asked to clear/manage tasks, or task state should be included in the continuation summary so the agent is aware of existing tasks.

Actual Behavior

The agent responded "there are no active tasks to clear" without checking, because the compaction summary didn't mention the task list state. The user had to ask twice before the agent finally called TaskList and discovered 6 tasks (5 completed, 1 in-progress).

Suggested Fix

Either:

• Include active task list state in the compaction/continuation summary
• Or instruct the agent in the continuation system prompt to proactively call TaskList to restore awareness of persistent state