🧪 Universe Persistence Bug - Diagnostic Testing

Date: November 3, 2025
Status: DIAGNOSTIC LOGGING ADDED
Goal: Find why universes disappear after refresh

🔬 What Was Added

Enhanced logging in SpaceService to trace every step:

1. Universe Loading - Shows what universeIds the space has
2. Storage Checks - Verifies each universe exists in storage
3. Validation - Shows spaceId comparison for each universe
4. Merge Logic - Shows what IDs are merged from backend/local
5. Backend Sync - Shows what backend returns after sync

🧪 Test Procedure

Step 1: Clear Browser State

IMPORTANT: Start fresh to avoid old data interfering

1. Open DevTools Console (F12)
2. Run: clearCachedSpaceData()
3. Or manually: Clear IndexedDB → Delete "gograb-space" database
4. Refresh page

NEW: You can also run debugUniverseStorage() at any time to see:

• All universes in storage
• Their spaceIds
• Validation status

Step 2: Create Universe

1. Navigate to: http://localhost:5200/chrome-space-1/dashboard
2. Click "Create Universe"
3. Fill form:
   • Name: "Test Universe Persist"
   • Description: "Testing persistence"
4. Click "Create Universe"
5. WATCH CONSOLE: Look for these logs:

   [SpaceService] 💾 Universe saved to local storage
   [SpaceService] 🌐 Syncing space to backend with new universe...
   [SpaceService] ✅ Space synced to backend with universeIds
   

Step 3: Navigate to Space Map

1. Should see universe in the overview
2. WATCH CONSOLE: Look for:

   [SpaceService] 🔍 Loading universes for space:
   [SpaceService] 🔍 Checking universe from storage:
   [SpaceService] 🔍 Validating universe:
   [SpaceService] ✅ Universe INCLUDED: Test Universe Persist
   

Step 4: Refresh Page (THE CRITICAL TEST)

1. Press F5 to refresh
2. WATCH CONSOLE CAREFULLY: Look for:

   [SpaceService] 🔍 Merging validated universeIds from local storage:
   [SpaceService] 🔍 Backend returned after sync:
   [SpaceService] 🔍 Loading universes for space:
   [SpaceService] 🔍 Checking universe from storage:
   [SpaceService] 🔍 Validating universe:
   

Step 5: Navigate to Dashboard

1. Click "Dashboard" in sidebar
2. WATCH CONSOLE: Look for universe validation logs
3. Check dashboard: Does it show 0 or 1 universe?

🔍 What To Look For

✅ GOOD SIGNS (Universe Persists)

[SpaceService] 🔍 Validating universe:
  universeId: "universe_xxxxx"
  universeName: "Test Universe Persist"
  universeSpaceId: "69067c087ebb621cd9ff8c3f"  ✅ Has spaceId
  currentSpaceId: "69067c087ebb621cd9ff8c3f"   ✅ Matches
  hasSpaceId: true                              ✅
  idsMatch: true                                ✅
  willBeIncluded: true                          ✅

[SpaceService] ✅ Universe INCLUDED: Test Universe Persist

❌ BAD SIGNS (Universe Lost)

Missing spaceId:

[SpaceService] ❌ Universe missing spaceId property, filtering out
  universeSpaceId: undefined                    ❌ No spaceId!
  currentSpaceId: "69067c087ebb621cd9ff8c3f"

Space ID Mismatch:

[SpaceService] ❌ Universe does not belong to current space
  universeSpaceId: "some-other-space-id"       ❌ Wrong spaceId!
  currentSpaceId: "69067c087ebb621cd9ff8c3f"

Not Found in Storage:

[SpaceService] ❌ Universe not found in storage
  universeId: "universe_xxxxx"                  ❌ Not in storage!
  storageKey: "universe_universe_xxxxx"

Backend Returned Empty:

[SpaceService] 🔍 Backend returned after sync:
  returnedUniverseIds: []                       ❌ Backend lost data!
  returnedCount: 0
  sentCount: 1

📊 Copy ALL Console Logs

When you see the issue, copy the ENTIRE console output from:

1. Universe creation
2. Navigation to space-map
3. Page refresh
4. Navigation to dashboard

Send the logs so we can pinpoint the exact failure point.

💡 Expected Diagnosis

The enhanced logging will reveal ONE of these issues:

1. Universe not saved with spaceId → Fix createUniverse()
2. Space ID changed between creation and reload → Fix initializeSpace()
3. Backend not returning universeIds → Fix backend API
4. Storage key mismatch → Fix storage.get() key
5. Merge logic filtering out valid universes → Fix merge validation

Ready to test! 🚀
Run the test procedure and share the console logs.