Refactor: How to eliminate all duplicate generation code paths so Vitt...
Documentation for Sessions
♻️ Refactor: How to eliminate all duplicate generation code paths so Vitt...
Date: 2026-03-11
Time: 17:42:07 UTC
Session: gspace1-204.9
Agent: angular
Confidence: 97%
Status: ✅ Documented
📋 Decision Context
Question:
How to eliminate all duplicate generation code paths so Vitto is the sole orchestrator?
Task: Not specified
🎯 Decision Made
Chosen:
Gutted GenerationHubService (1334→70 lines), rewired ChatModulePanelComponent to WorkflowStateService, deprecated WorkflowSSEClientService and GenerationRouterService. Net: -1247 lines of dead SSE code.
Options Considered:
- No alternatives documented
💭 Reasoning
GenerationHubService had zero external consumers — only used by ai-generation-hub internal components which are never loaded (route redirects to /vibe). The 1300 lines included a full parallel SSE implementation, entity pattern matching, field generation — all duplicating what Vitto does better. ChatModulePanelComponent was the only active consumer of the old GenerationRouterService→WorkflowSSEClientService→backend-ai-api chain. Rewiring it to WorkflowStateService makes it go through Vitto.
📁 Files Involved
libs/libs-ai/ai-generation-hub/src/lib/services/generation-hub.service.tslibs/libs-ai/vitto-chat/src/lib/components/generation/chat-module-panel/chat-module-panel.component.tslibs/libs-ai/gograb-ai-lib/src/lib/services/workflow-sse-client.service.tslibs/libs-ai/gograb-ai-lib/src/lib/services/generation-router.service.ts
🔗 Related
- Decision ID:
dev_1773250926989_72rnvrk - Session: 204
- Workspace: gspace1
Auto-generated by MCP Smart Consolidation