Architecture: How should the Studio project edition pipeline be structured...

Documentation for Sessions

🏗️ Architecture: How should the Studio project edition pipeline be structured...

Date: 2026-03-11
Time: 12:50:59 UTC
Session: gspace1-203.3
Agent: angular
Confidence: 85%
Status: ✅ Documented

📋 Decision Context

Question:

How should the Studio project edition pipeline be structured?

Task: S203: Platform generation quality and edition pipeline

🎯 Decision Made

Chosen:

Reuse existing VFS/editor/git infrastructure (already fully wired in S188-S200), add project dashboard as new route entry point, add branches/diff/settings as dock panels, extend GitStateService with branch CRUD + diff

Options Considered:

Build from scratch with new services
Reuse existing infrastructure and add missing panels
Use gmodules1 admin pattern (config-only, no code editing)

💭 Reasoning

Discovery revealed the VFS → File Tree → Editor → GitLab commit pipeline was already complete from S188-S200. No rewiring needed. The gaps were: no project list view, no branch management UI, no diff view, no settings. These fit naturally as dock panels (consistent with existing 15+ panel pattern) and a new route for the dashboard.

📁 Files Involved

libs/libs-structural/vitto-studio/src/lib/routes/vitto-studio.routes.ts
libs/libs-structural/vitto-studio/src/lib/services/git-state.service.ts
libs/libs-structural/vitto-studio/src/lib/panels/branches-panel.component.ts
libs/libs-structural/vitto-studio/src/lib/panels/diff-panel.component.ts
libs/libs-structural/vitto-studio/src/lib/components/project-dashboard/project-dashboard.component.ts

🔗 Related

Decision ID: dev_1773233459062_9k87u5q
Session: 203
Workspace: gspace1

Auto-generated by MCP Smart Consolidation