Dream project rebuild fails when some L2 projects are missing explanation

[yl11023]

Describe the Bug

The Dream consolidation step fails with:

Dream project rebuild did not explain current projects: openclaw-cli-auth-fix, wu-jijun-billing-info-query, openclaw-gateway-auth-config, persona-improvement, system-command-output-fix, clawxmemory-ui-bug-tracking, browser-login-setup, voice-response-implementation, clawx-memory-optimization, browser-automation-skill, legal-advice-scenario, voice-audio-issues

6 out of 12 L2 projects were not explained during Dream rebuild.

Environment

• ClawXMemory version: 0.1.5 (latest at time of report)
• OpenClaw version: 2026.4.2
• Runtime: agent=main | model=qwen/qwen3.6-plus:free (default: Qwen3.5 local)
• OS: Windows 11

Reproduction Steps

1. Accumulate multiple project sessions across several days
2. Let ClawXMemory index them automatically (indexing succeeds)
3. Dream consolidation triggers (either scheduled or manual memory_flush)
4. Dream fails because some project keys exist in the index but the Dream L2 rebuild cannot generate explanations for them

Observed Behavior

• memory_search returns all 12 projects successfully (search uses L1/L2 directly)
• memory_overview shows lastDreamStatus: failed
• lastDreamL1EndedAt points to an older session (2026-04-03), suggesting Dream only processed a subset
• All 6 "missing" projects are legitimate L2 projects from prior sessions (browser-login-setup, voice-response-implementation, clawx-memory-optimization, browser-automation-skill, legal-advice-scenario, voice-audio-issues)

Expected Behavior

Dream rebuild should either:

1. Explain all current L2 projects, or
2. Gracefully handle projects it cannot explain (e.g., mark them as "insufficient context" rather than failing the entire operation)

Impact

• Retrieval/search continues to work fine (enoughAt=l1 still succeeds)
• However, persistent Dream failures prevent L2 consolidation, which could degrade memory quality over time
• The failed Dream timestamp keeps showing in memory_overview

Additional Context

• Total L2 projects: 29
• Total L0 sessions: 252
• Total L1 windows: 29
• pendingL0: 0 (no new sessions waiting to be indexed)
• The 6 unexplained projects were created from sessions around 2026-04-03 to 2026-04-04

[yl11023]

Second Dream Failure (Update)

Dream failed again at 2026-04-05T11:51:49Z with a different set of unexplained projects:

• clawxmemory-setup
• system-command-output-fix
• browser-login-setup
• voice-response-implementation
• clawx-memory-optimization
• clawxmemory-ui-fix

The first failure at 11:47 had 12 projects; this second one has 6, and the overlap is partial. This suggests the Dream engine sees a different project snapshot each run, which points to a determinism/stability issue rather than simply missing data.

Pattern

Run	Time	Failed Projects
1st	11:47 UTC	12 projects (incl. cli-auth-fix, billing-info, gateway-auth, persona-improvement, etc.)
2nd	11:51 UTC	6 projects (incl. clawxmemory-setup, clawxmemory-ui-fix)

Both runs have lastDreamL1EndedAt: 2026-04-03T15:25:26Z, suggesting the Dream L1 base is anchored to an old session. Total L2 projects = 29 remains unchanged.

[yl11023]

Root Cause Analysis & Fix Applied

Root Cause

Two cascading issues:

1. LLM planning can miss projects — planDreamProjectRebuild may not include every current project in its output (neither kept nor deleted)
2. Fallback clustering misses orphan projects — buildFallbackProjectPlan only clusters projects that have L1 window details. Projects with no associated L1 windows get silently dropped into deletedProjectKeys, and buildProjectPlan counted them as "explained" (handled) even though they were lost.

Fix Applied (dream-review.js)

1. Added try-catch to buildProjectPlan — LLM failures fall back to buildFallbackProjectPlan
2. Added try-catch to buildProfileRewrite — Profile rewrite failures fall back to buildFallbackProfileRewrite
3. Added orphan preservation in run() — after plan is obtained, any existing project NOT in plan.projects is appended to the final output with its original data, regardless of whether it appears in plan.deletedProjectKeys
4. Fixed plannedKeys check — only checks plan.projects, not plan.deletedProjectKeys, so fallback-deleted projects are correctly treated as orphans and preserved

Result

All 29+ existing projects should now survive Dream reconstruction. Projects without L1 source data will be preserved as-is rather than dropped.

---

Note: This was fixed inline by patching the installed dist file. An upstream PR would be appropriate for the next release.