🏗️ Architecture: How should the widget generation pipeline be fixed to route ...

Date: 2026-01-22
Time: 15:12:14 UTC
Session: editor2-58.7
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should the widget generation pipeline be fixed to route requests to the backend instead of using broken frontend stubs?

Task: Session 57.1: Fix widget generation pipeline

🎯 Decision Made

Chosen:

Create new GenerationRouterService that routes directly to backend-api while also fixing processCompletion() for backward compatibility

Options Considered:

1. Fix IntelligenceCoordinatorService.processCompletion() only
2. Create new GenerationRouterService that routes directly to backend-api
3. Bypass all frontend services and call backend directly from components

💭 Reasoning

The existing IntelligenceCoordinatorService.processCompletion() was returning placeholder code instead of parsing AI responses. Creating GenerationRouterService provides a clean, unified entry point for all generation requests (widget, module, image, video) that routes directly to the correct backend-api endpoints. Also fixed processCompletion() to actually parse markdown code blocks from AI responses for backward compatibility with services still using IntelligenceCoordinatorService.

📁 Files Involved

• libs/libs-ai/gograb-ai/src/lib/services/generation-router.service.ts
• libs/libs-ai/gograb-ai/src/lib/services/intelligence-coordinator.service.ts
• libs/libs-ai/vitto-hub/src/lib/components/ai-panel-widget/ai-panel-widget.component.ts

🔗 Related

• Decision ID: dev_1769094734367_bbol8r0
• Session: 58
• Workspace: editor2

Auto-generated by MCP Smart Consolidation