♻️ Refactor: How should the AI Panel component (3083 lines) be separated ...

Date: 2026-02-17
Time: 21:31:57 UTC
Session: gspace1-112.3
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should the AI Panel component (3083 lines) be separated from Vitto's command hub?

Task: Session 112: Extract AI Panel from vitto-hub into ai-panel-core

🎯 Decision Made

Chosen:

Extract AiPanelComponent + 5 sub-components + 4 services + 2 model files from @libs-ai/vitto-hub into @libs-ai/ai-panel-core. The ai-panel-core library already existed as a lightweight shell (trigger directive + core state + types). Expanded it to hold the full AI Panel.

Options Considered:

• No alternatives documented

💭 Reasoning

The AiPanelComponent talks to 3 backends (backend-ai-api, backend-api, backend-vitto-api) and has 26 inject() calls. It's the universal interface for ALL AI interactions — not specific to Vitto. Keeping it in vitto-hub conflated the interface with the orchestrator. ai-panel-core already existed with an intentional design: lightweight types/triggers that any library can import without pulling heavy deps. We expanded it to also hold the heavy component, since the trigger/types remain importable separately via their existing export paths. No circular dependencies introduced because ai-panel-core doesn't import from vitto-hub.

📁 Files Involved

• libs/libs-ai/ai-panel-core/src/index.ts
• libs/libs-ai/ai-panel-core/src/lib/components/ai-panel/ai-panel.component.ts
• libs/libs-ai/ai-panel-core/src/lib/services/ai-panel-state.service.ts
• libs/libs-ai/vitto-hub/src/index.ts

🔗 Related

• Decision ID: dev_1771363917582_n7qu8md
• Session: 112
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation