♻️ Refactor: How to consolidate duplicate generation UIs (ai-generation-h...

Date: 2026-03-11
Time: 16:35:29 UTC
Session: gspace1-204.7
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How to consolidate duplicate generation UIs (ai-generation-hub vs vibe-universe)?

Task: Not specified

🎯 Decision Made

Chosen:

Deprecate ai-generation-hub route with redirect to vibe-universe. Remove from dashboard, nav, and tool orchestration. Keep library files for now (transitive imports may exist).

Options Considered:

1. Delete ai-generation-hub entirely
2. Merge ai-generation-hub features into vibe-universe
3. Deprecate with redirect (chosen)
4. Keep both and sync them

💭 Reasoning

ai-generation-hub had its own parallel SSE implementation (GenerationHubService) duplicating WorkflowStateService logic, and originally hit the broken backend-ai-api/workflow endpoint that never decomposed requirements (0 modules). vibe-universe already correctly routes through Vitto's 7-phase pipeline via WorkflowStateService. Two competing generation UIs = confusion and maintenance burden. Redirect preserves any bookmarks/links while funneling all generation through the correct path.

📁 Files Involved

• apps/gograb-space/src/app/app.routes.ts
• libs/libs-structural/vibe-universe/src/lib/services/tool-orchestration.service.ts
• apps/gograb-space/src/app/components/space-components/g-space-dashboard/g-space-dashboard.component.ts
• apps/gograb-space/src/app/components/layout/main-layout/main-layout.component.ts
• libs/libs-ai/gograb-ai-lib/src/lib/services/workflow-state.service.ts

🔗 Related

• Decision ID: dev_1773246929443_hbe3oya
• Session: 204
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation