🏗️ Architecture: How should the 4 critical pipeline wiring gaps (C1-C4) be im...

Date: 2026-02-06
Time: 04:06:12 UTC
Session: editor2-95.11
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should the 4 critical pipeline wiring gaps (C1-C4) be implemented?

Task: Implement C1-C4 critical pipeline wiring fixes

🎯 Decision Made

Chosen:

C1: Added orchestration_complete to PhaseProgressEvent type + event listener + lastOrchestrationResult signal in WorkflowSSEClientService. C2: AIModuleReceiverService watches SSE client signal via effect() and auto-calls receiveFromOrchestration(). C3: ModuleWorkbenchComponent watches receiver's lastReceivedModuleId signal and auto-loads via loadExistingModule(). C4: Deploy step filters out .ts/.scss (not browser-ready), generates rich self-contained index.html with XSS-safe escaping, removes broken runtime.js reference.

Options Considered:

• No alternatives documented

💭 Reasoning

Chose signal-based reactive wiring over manual subscription because: (1) signals are Angular's preferred reactive primitive in 17+, (2) no subscription cleanup needed, (3) the receiver is a root singleton so the effect() lives for the app lifetime. Dependency direction is libs-structural → libs-ai (already established, no circular dep). Deploy fix uses pragmatic static HTML approach rather than in-browser TS compilation - Cloudflare Pages serves static files, so the generated HTML must be self-contained.

📁 Files Involved

• libs/libs-ai/gograb-ai-lib/src/lib/services/workflow-sse-client.service.ts
• libs/libs-structural/modularity-lib/src/lib/services/ai-module-receiver.service.ts
• libs/libs-structural/modularity-lib/src/lib/components/module-workbench/module-workbench.component.ts
• libs/libs-structural/modularity-lib/src/lib/components/steps/deploy-step/deploy-step.component.ts

🔗 Related

• Decision ID: dev_1770350772549_00p4u5z
• Session: 95
• Workspace: editor2

Auto-generated by MCP Smart Consolidation