🏗️ Architecture: Should the studio auto-detect and render existing platforms ...

Date: 2026-03-17
Time: 18:32:09 UTC
Session: gspace1-229.12
Agent: angular
Confidence: 93%
Status: ✅ Documented

📋 Decision Context

Question:

Should the studio auto-detect and render existing platforms from GitLab on load, and should the pipeline auto-merge to develop?

Task: Not specified

🎯 Decision Made

Chosen:

Two changes: (1) Pipeline auto-merges feature branch to develop instead of creating a draft MR — generated code has no human review gate, the feature branch + commit history provides the audit trail. Falls back to MR if merge fails (conflicts). (2) VfsSyncService emits modulesLoaded$ after hydration; StudioDockShellComponent subscribes and auto-triggers rspack preview + opens preview panel when existing modules are detected (>0 modules, not currently generating).

Options Considered:

• No alternatives documented

💭 Reasoning

Draft MRs were wrong for generated platforms. The user explicitly asked Vitto to build the platform — there's no code review gate needed. The draft MR pattern left code stranded on a feature branch that the studio VFS (reading from develop) couldn't see, causing the 'Ready when you are' screen even when the platform existed in GitLab. The auto-preview on load is the other half: even after merging to develop, the studio had no mechanism to detect existing modules and trigger compilation. The modulesLoaded$ signal bridges this gap.

📁 Files Involved

• APIs/backend-vitto-api/src/app/module-generation/phases/module-gen-phase.executor.ts
• libs/libs-structural/vitto-studio/src/lib/services/vfs-sync.service.ts
• libs/libs-structural/vitto-studio/src/lib/components/studio-dock-shell/studio-dock-shell.component.ts

🔗 Related

• Decision ID: dev_1773772329173_k24rhr6
• Session: 229
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation