diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 9855d0c5b..afd0cf79b 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "9577d6609b697578287596456bed776a988d7b74",
-  "syncedAt": "2026-04-14T23:59:00.374Z"
+  "sha": "0c4e0d703023c93bed101fcf62a92dbfd3537bcc",
+  "syncedAt": "2026-04-15T00:29:51.591Z"
 }
diff --git a/docs/concepts/dreaming.md b/docs/concepts/dreaming.md
index 0a3795f4b..49f548e6a 100644
--- a/docs/concepts/dreaming.md
+++ b/docs/concepts/dreaming.md
@@ -80,6 +80,9 @@ After each phase has enough material, `memory-core` runs a best-effort backgroun
 subagent turn (using the default runtime model) and appends a short diary entry.
 
 This diary is for human reading in the Dreams UI, not a promotion source.
+Dreaming-generated diary/report artifacts are excluded from short-term
+promotion. Only grounded memory snippets are eligible to promote into
+`MEMORY.md`.
 
 There is also a grounded historical backfill lane for review and recovery work: