Refactor: Which libs-ai libraries should be removed, consolidated, or ...

Documentation for Sessions

♻️ Refactor: Which libs-ai libraries should be removed, consolidated, or ...

Date: 2026-03-12
Time: 16:38:04 UTC
Session: gspace1-208.4
Agent: architecture
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Which libs-ai libraries should be removed, consolidated, or kept during the cleanup audit?

Task: S208: libs-ai cleanup audit

🎯 Decision Made

Chosen:

Remove 7 dead libraries (~20K lines): ai-generation-hub (deprecated S204), ai-task-router (0 imports), ai-training-models (0 imports), multi-agent-dashboard (0 imports), panel-intelligence (deprecated S171), ai-agent-experience (0 imports), ai-agent-registry (0 imports). Also remove 3 orphaned shell directories (ai-module-patterns, ai-outcome-tracker, cursor-agents) whose code was already consolidated into parent libs. Remove 8 stale tsconfig aliases.

Options Considered:

  1. A: Keep all libraries, just mark deprecated
  2. B: Remove only explicitly @deprecated libraries
  3. C: Remove all zero-import libraries + orphaned shells + stale aliases

💭 Reasoning

Full audit of all 29 libs-ai libraries showed 7 with zero TypeScript imports (only doc/comment references). Several had been logically consolidated in S113 but the old directories remained as shells. The tsconfig paths for consolidated libs already pointed to parent libs (e.g., @libs-ai/ai-agent-experience → agent-mind/src/index.ts), so the directories were dead weight. multi-agent-dashboard had 1 import in gograb-dev that was replaced by the Command Center migration to /command/mission. Key active aliases preserved: @libs-ai/module-patterns and @libs-ai/outcome-tracker (5+ active code imports each, pointing to ai-module-intelligence).

📁 Files Involved

🔗 Related

Auto-generated by MCP Smart Consolidation