Generation Test Attempt 5: All Phases Complete, But Only 1 Module Generated + Deploy Fails

Session 138.3 | February 23, 2026 | Testing Director

Executive Summary

After the coding agent's fixes to ANALYZE, PLAN, and ENHANCE phases (maxTokens bump, normalizer functions, parseLlmJson), generation now completes all 7 phases without crashing. This is a major milestone.

However, two new issues prevent the feature from being usable:

1. Bug 4: EXECUTE phase generates only 1 module instead of the expected 5-6 (Fitness Studio template). Root cause: module name format mismatch between PLAN and DECOMPOSE phases.
2. Bug 5: "Deploy to Universe" button fails with "Deployment Issue". Console shows: Auto-sync skipped: No modules in manifest. Hub shows 0 modules, 0 pages, 0 galaxies.

Test Results Summary

Bug 4: Module Name Format Mismatch (CRITICAL)

Symptom

Only 1 module generated for "Fitness Studio" template which describes: membership management, class scheduling, trainer assignments, workout tracking, payment processing, and member check-in.

Root Cause

File: apis/backend-vitto-api/src/app/module-generation/phases/execute.phase.ts, line 72

const moduleSpec = decomposeResult.modules.find(m => m.name === plan.moduleName);
if (!moduleSpec) {
  this.logger.warn(`Module ${plan.moduleName} not found in decomposition — skipping`);
  continue;
}

The matching uses strict equality (===) between:

• plan.moduleName — comes from PLAN phase, normalized by normalizePlanResult() which maps p.moduleId → moduleName. The PLAN prompt template (system-plan.prompt.md) instructs the LLM to return moduleId in kebab-case (e.g., "user-management")
• decomposeResult.modules[].name — comes from DECOMPOSE phase, preserved as-is by normalizeDecomposeResult(). The DECOMPOSE LLM returns names in title case (e.g., "User Management")

Result: "user-management" === "User Management" → false → module SKIPPED.

Most modules are skipped, resulting in only ~1 module generated (whichever coincidentally matches).

Data Flow Trace

DECOMPOSE LLM → { modules: [{ name: "Member Management" }, { name: "Class Scheduling" }, ...] }
    ↓ normalizeDecomposeResult()
decomposeResult.modules[0].name = "Member Management"  (title case preserved)

PLAN LLM → { executionPlan: { phases: [{ moduleId: "member-management" }, ...] } }
    ↓ normalizePlanResult()
planResult.executionPlan[0].moduleName = "member-management"  (kebab-case from moduleId)

EXECUTE line 72:
  "Member Management" === "member-management" → FALSE → SKIPPED

Fix Options

Option A (Fastest — recommended): Case-insensitive + format-tolerant matching in execute.phase.ts line 72:

const normalize = (s: string) => s.toLowerCase().replace(/[\s-_]+/g, '');
const moduleSpec = decomposeResult.modules.find(
  m => normalize(m.name) === normalize(plan.moduleName)
);

Option B (More robust): Also update normalizePlanResult() to convert moduleId to title case to match DECOMPOSE convention. But this may break other code that expects kebab-case.

Option C (Best long-term): Add a moduleSlug field to both DECOMPOSE and PLAN outputs and match on that. Both normalizers would generate slugs from the module name.

Bug 5: "Deploy to Universe" Fails — No Modules in Manifest

Symptom

After clicking "Deploy to Universe", a modal appears: "Deployment Issue — Something went wrong during deployment". Console warning: Auto-sync skipped: No modules in manifest.

Root Cause Chain

1. Backend buildManifestJSON() (line 493-562 in module-gen-phase.executor.ts) correctly builds manifest with navigation.menuItems from executeOutput.modules

2. SSE event module-gen.completed sends manifestJSON to frontend

3. Frontend WorkflowStateService (line 263-275) correctly receives and parses manifestJSON into generatedManifest signal

4. autoSyncModulesToCanvas() (line 1056-1092 in vibe-universe-generator.component.ts) calls extractModulesFromNavigation(manifest.navigation?.menuItems, manifest)

5. extractModulesFromNavigation() (lines 563-636) has 5 fallback methods to extract module names:

   • Method 1: From navigation.menuItems[].route → filters out "dashboard"
   • Method 2: From manifest.routes[].path → filters out "dashboard"
   • Method 3: From manifest.metadata?.generatedModules
   • Method 4: From manifest.id
   • Method 5: From manifest.name

6. With only 1 module generated (due to Bug 4), if that module's route is "dashboard" or its extraction fails, result is empty → "No modules in manifest"

Additional Concern: DEPLOY Phase Persistence

The backend DEPLOY phase (line 228-318 in executor) calls backendAiClient.persistGeneratedModules(). This requires backendAiClient to be injected. If it's not available (optional dependency), DEPLOY is effectively a no-op — it reports "success" but persists nothing. The hub showing 0 modules suggests persistence may not be happening.

Fix

Fix Bug 4 first. Once EXECUTE generates all 5-6 modules:

• buildManifestJSON() will include all modules in navigation.menuItems
• extractModulesFromNavigation() will find non-dashboard modules
• Deploy should work

Additionally: Verify that backendAiClient is properly injected in the module generation module. Check the NestJS provider registration.

Files to Modify

Previously Fixed Issues (Verified Working)

Console Evidence

[1:19:40 PM] [ModuleSuggestions] Loaded global modules: 19
[1:19:40 PM] [ModuleSuggestions] Built industry templates: Array(5)
[1:20:05 PM] 🚀 [VibeGenerator] Starting generation now...
[1:21:28 PM] ⚠️ WARN » VibeUniverseGenerator
  🔄 Auto-sync skipped: No modules in manifest

Generation ran from 1:20:05 to 1:21:28 (~83 seconds). All phases completed. But auto-sync failed.

Network Evidence

• 4 SSE requests to localhost:3003/vitto-api/module-generation/start (all 200 OK)
• No deployment API call was observed (no POST to persist/deploy endpoint)
• Hub endpoint localhost:3000/api/spaces/.../universes returns universe with 0 modules

Hub Verification

Universe Hub at /space/chrome-space-1/universe/paks-uni-1/hub shows:

• MODULES: 0
• PAGES: 0
• GALAXIES: 0
• Last Updated: Jan 16, 2026, 03:28 PM (before today's tests)
• Empty Universe: Delete all modules (0)

Recommended Testing After Fix

1. Apply the case-insensitive matching fix to execute.phase.ts line 72
2. Re-run generation
3. Verify EXECUTE generates 5-6 modules (check backend logs for "EXECUTE completed: N visual modules")
4. Verify "Platform Generated Successfully" shows correct module count
5. Click "Deploy to Universe"
6. Navigate to Hub → verify modules > 0, pages > 0
7. If deploy still fails, check backendAiClient injection in DEPLOY phase