[FEATURE] Bridge ConversationManager and SessionManager

[dbschmigelski]

Priority: Low

Problem Statement

ConversationManager and SessionManager operate in isolation. Content removed from the active context window is stored in session storage for audit-ability, but there is no standard way to retrieve it. If something relevant was said early in a conversation, it is effectively lost once removed from the window. Intelligent context management requires these components to work together.

Proposed Solution

Connect ConversationManager and SessionManager so that:

• Persistent storage becomes a retrievable context source, not just an audit log
• The context manager knows what content is available for retrieval in session storage
• The context manager can retrieve and re-insert relevant content when needed

This is the foundational plumbing that enables context navigation meta-tools and tiered memory (MemGPT-inspired).

Use Case

• Long-running conversations where early context becomes relevant again
• Recovering from lossy context reduction (sliding window, summarization)
• Enabling the agent to search its own conversation history

Additional Context

Part of the Context Management epic, Track 1: Conversation Context. Unlocks context navigation meta-tools and tiered memory.