S201 Handoff Prompt — Validating & Hardening Platform Code Generation

Who You Are

You are continuing work on GoGrab Space's Generate → Edit → Deploy pipeline. Session 200 connected the frontend to the backend infrastructure and fixed critical generation bugs. Your job is to validate the fixes work end-to-end and harden the remaining rough edges.

What Was Built in S200 (5 Commits)

The Full Plan

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

Phases 1-4 are implemented. Phase 5 (Production Hardening) remains.

Your Priority: Validate & Fix

Priority 1: Verify Generation End-to-End

The S200 fixes need validation with a real generation run. Key things to verify:

1. Category assignment — Are modules getting meaningful categories (layout, analytics, etc.) or still defaulting to structural?
2. GitLab repo creation — Does the personal namespace fallback work? Check for any repo path issues.
3. Scaffold templates — Do generated form/list/detail components compile? Check for:
   • crud.onSubmit() not form.submit()
   • crud.isFieldInvalid('name') not isFieldInvalid('name')
   • crud.form() not form.formGroup()
4. Path aliases — Are they @module/{category}/{slug} format?
5. package.json — Does each module get one?
6. Parallel execution — Are modules batched? Check logs for "PARALLEL: Executing batch of N modules"
7. modules.map error — Should be gone. Verify tool handler gets actual module array.

Priority 2: Studio Visualization

Vitto Studio's file tree should show generated modules. If it doesn't:

• Check that VfsSyncService.setRepoContext() is being called
• Check that refreshAllModulesFromRepo() gets data from GitLab
• The StudioGenerationListenerService uses mode-aware refreshModule()/refreshAllModules()

Priority 3: Production Hardening (Phase 5)

From the plan:

• 5.1 MongoDB event persistence for SSE (replace in-memory ReplaySubject)
• 5.2 Local dev mode (SAVE_GENERATED_LOCALLY=true + file watcher)
• 5.3 NX module registration (yarn paths:merge after generation)
• 5.4 Post-generation chat summary
• 5.5 Pipeline visualization polish
• 5.6 Multi-tenant isolation verification
• 5.7 Rollback capability

Key Architecture Context

• GitLab is the source of truth for all generated code
• Module aliases: @module/{category}/{slug} (NEVER without category)
• Categories inferred from names: dashboard→layout, auth→auth, analytics→analytics, chat→communication
• Parallel generation: PARALLEL_MODULE_GEN_BATCH=3 env var (default)
• Scaffold fallback: After 2 failed LLM fix attempts, scaffold guarantees valid code
• Platform output: platforms/{spaceSlug}/{platformSlug}/ for app shells, modules/{category}/{slug}/ for modules

Critical Conventions (from S200)

1. session.result.executeResult.modules MUST be an array, never a count
2. Scaffold templates must use crud.* prefix (useCrudForm/useCrudList return objects)
3. GitLab initializeRepo falls back to personal namespace on 403
4. normalizeDecomposeResult → inferModuleCategory() maps names to categories
5. Every module needs package.json with name @module/{category}/{slug}
6. IntelligentMessageDoc.content is required: false (task messages have empty content)

Existing Infrastructure

What NOT to Do

• Do NOT manually edit generated module files. 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.
• Do NOT use @module/{slug} without category. Always @module/{category}/{slug}.

Commit Convention

[S201.N] type: description

Example: [S201.1] fix: verify generation produces compilable modules