RFC - Add session management tools for debugging and external tooling

[wesen]

In the branch idea/inspect-session, I sketch out a toolkit for exporting and importing conversation sessions to enable:

1. Debugging workflows - Export sessions to analyze conversation patterns, token usage, and costs
2. External tooling development - Enable developers to build analysis tools, visualizations, or integrations that could later be incorporated into Crush
3. Data portability - Share conversations between team members or environments for troubleshooting

New Commands

• crush sessions export/export-conversation - Export session data to JSON/YAML files
• crush sessions import/import-conversation - Import session data from JSON/YAML files
• crush sessions search - Find sessions by title or message content
• crush sessions stats - Analyze usage patterns and costs over time

Status

This is a prototype implementation. The code is functional and safe to merge as it operates independently from the core application logic.

Use Cases

• Export problematic conversations for debugging
• Build external analytics dashboards using session data
• Create conversation analysis tools for cost optimization
• Develop conversation sharing/archiving workflows
• Prototype new features using real conversation data

[BradKML]

Other than export/import, we also need a kind of context chunking/summarization/condensation so that it can be more easily used, without MCPs and without needing manual session starts #810

Session management is good for going between feature building and solving multiple issues. Chunking and condensation are good when it is one hard feature or bug, needing multiple layers of investigation and bug-hunting.

[maliayas]

Related issue where I discuss storing chats directly as plantext in the first place rather than exporting later (both can coexist though).

[Peng-YM]

plus one on this, we need this on CI tasks