🏗️ Architecture: How to consolidate session storage to eliminate duplication?

📋 Decision Context

Question:

How to consolidate session storage to eliminate duplication?

Task: Not specified

🎯 Decision Made

Chosen:

Store decisions IN session manifests instead of separate .cursor/ai-memory/sessions/ folder

Options Considered:

• No alternatives documented

💭 Reasoning

v8.0 consolidation: (1) Decisions were duplicated in .cursor/ai-memory/sessions/session-X.json AND sessions/sessions-history/{workspace}/session-X.json, (2) Session manifests had empty decisions arrays while cache had data, (3) By storing decisions IN the manifest: single file per session, no sync issues, easier backup/restore, Git-tracked decisions

📁 Files Involved

• MCP/mcp-development-ai/src/storage/file-storage.ts
• MCP/mcp-development-ai/src/storage/docs-data-integration.ts
• MCP/mcp-development-ai/src/tools/log-decision.ts
• sessions/sessions-history/editor2/session-35.json

🔗 Related

• Decision ID: dev_1768066508736_2h76qtn
• Session: 35
• Workspace: editor2

Auto-generated by MCP Smart Consolidation