🏗️ Architecture: How should we organize session data to avoid duplication and...

📋 Decision Context

Question:

How should we organize session data to avoid duplication and maintain a single source of truth?

Task: Session folder consolidation - single source of truth

🎯 Decision Made

Chosen:

Use only sessions/sessions-history/{workspace}/ as the single source of truth, removing the duplicate workspaces/ folder

Options Considered:

1. Keep both sessions/workspaces/ and sessions/sessions-history/
2. Use only sessions/workspaces/ (new)
3. Use only sessions/sessions-history/ (original)
4. Use database only, no local files

💭 Reasoning

Having two folders (workspaces/ and sessions-history/) violated the single source of truth principle and caused confusion. The sessions-history/ folder was the original location with complete history, so we consolidated there. Updated MCP constants to alias SESSIONS_WORKSPACES_DIR to SESSIONS_HISTORY_DIR, ensuring all code paths use the same location. Test sessions (1000+) moved to _test_sessions/ subfolder to keep production sessions clean.

📁 Files Involved

• MCP/mcp-development-ai/src/config/constants.ts
• MCP/mcp-development-ai/src/storage/docs-data-integration.ts
• sessions/sessions-history/editor2/
• sessions/active.json
• sessions/sessionID.json

🔗 Related

• Decision ID: dev_1767648653480_ss0g67a
• Session: 22
• Workspace: editor2

Auto-generated by MCP Smart Consolidation