S200 Handoff Prompt — Perfecting Platform Code Generation

Who You Are

You are continuing work on GoGrab Space's Generate → Edit → Deploy pipeline. Session 200 built the backend infrastructure. Your job is to perfect the platform code generation process and close the remaining gaps so the full pipeline works end-to-end.

What Was Built in S199 (6 Commits)

The Full Plan

Read: docs/english/Plans/perfecting-platform-code-gen.plan.md

This has the complete gap analysis with 17 tasks across 5 phases. Phase 1 is your priority.

Your Priority: Phase 1 — Frontend Wiring

These 4 tasks connect the S199 backend infrastructure to the frontend. Without them, the backend work is invisible to users.

Task 1.1: VfsSyncService — Load from GitLab Instead of Disk

File: libs/libs-structural/vitto-studio/src/lib/services/vfs-sync.service.ts

What to do:

• The method refreshAllModulesFromDisk() currently calls api.listModulesOnDisk() which reads local filesystem
• Add a parallel method refreshAllModulesFromRepo(spaceSlug, universeSlug) that calls the new GitLab-backed API:
  • api.listModulesFromRepo(spaceSlug, universeSlug) → get module slugs
  • api.getModuleStructureFromRepo(spaceSlug, universeSlug, slug) → get file tree
  • api.getFileFromRepo(spaceSlug, universeSlug, filePath) → get content
• Modify hydrateModuleFiles() to detect whether to use GitLab or disk mode
• The API methods already exist on StudioApiService (added in S199.3)

How to detect mode: If the project has a spaceSlug and universeSlug in its context, use GitLab. Otherwise fall back to disk.

Task 1.2: Edit → GitLab Auto-Commit

File: libs/libs-structural/vitto-studio/src/lib/services/vfs-sync.service.ts

What to do:

• When a user edits a file in Studio, the existing debounce logic syncs to backend
• Extend it to call api.commitFileToRepo(spaceSlug, universeSlug, filePath, content, 'edit: filename') after the 1s debounce
• Show commit status (saved/saving/error) in the editor — update the VFS node's metadata

Task 1.3: Chat SSE Reconnection

File: libs/libs-ai/vitto-chat/src/lib/services/vitto-chat-engine.service.ts

What to do:

• On service initialization, call GET {VITTO_API_URL}/module-generation/active/{spaceId}
• If response has active: true, resubscribe to the SSE stream using the returned sessionId
• Show a "Reconnected to generation in progress" message in chat
• The endpoint already exists (S199.6) and the ReplaySubject(50) already buffers events

Task 1.4: MR URL Display in Chat

File: libs/libs-ai/vitto-chat/src/lib/services/vitto-chat-engine.service.ts

What to do:

• Add a handler for module-gen.mr-created SSE event type (alongside existing tool.starting, tool.progress handlers from S197)
• Display: "Draft merge request created: View in GitLab" as a chat message
• The event data has: { mrUrl, mrId, branch, target, draft }

Key Architecture Context

• GitLab is the source of truth for all generated code. Not local disk, not R2.
• Studio reads from GitLab, edits commit to GitLab, deploys from GitLab.
• Vitto chat has the edit_module_file tool that commits to GitLab directly.
• UniverseGitService on backend-vitto-api wraps GitLab REST API v4 (no git binary).
• StudioRepoController on backend-ai-api proxies to backend-api's GitLabProviderService.

Existing Infrastructure You Can Use

What NOT to Do

• Do NOT manually edit generated module files (modules/structural/*). Fix the generator instead.
• Do NOT edit tsconfig.base.json for @module/* paths. Use config/tsconfig-paths/modules/generated.paths.json + yarn paths:merge.
• Do NOT hardcode ports. Use env vars from .env.local.
• Do NOT pass --port to backend serve commands (causes WebSocket 400 errors).
• Do NOT use Promises or async/await in Angular code. Use RxJS Observables exclusively.

Testing

• Backend-vitto-api auto-restarts on file changes (NestJS watch mode)
• Backend-ai-api auto-restarts on file changes
• Frontend: yarn serve:space (port 6200) — but rebuilding large NX apps is slow. Prefer building only the specific library you changed: npx nx build vitto-studio --skip-nx-cache
• To test generation: use the Vitto chat in gograb-space on port 6200, ask to generate a platform

Environment

• Branch: session-200 (create from session-199)
• GitLab credentials: in .env.local (GITLAB_URL, GITLAB_API_TOKEN)
• Cloudflare credentials: in .env.local (CLOUDFLARE_ACCOUNT_ID, CLOUDFLARE_API_TOKEN)
• R2 credentials: in .env.local (R2_ACCOUNT_ID, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY)

Commit Convention

[S200.N] type: description

Example: [S200.1] feat: VfsSyncService loads modules from GitLab repo