Bug Description

When the Dreaming System runs, it writes Dream Diary narrative content to memory/YYYY-MM-DD.md files instead of only to DREAMS.md as documented.

This makes daily memory files unusable for their intended purpose. When an agent tries to answer "what did I do yesterday?", it reads hundreds of lines of Dream Diary narrative instead of actual event records.

Expected Behavior (per docs)

From the Dreaming docs:

Dreaming 会将人类可读的叙事输出写入 DREAMS.md（或现有的 dreams.md）。

Dream Diary is human-readable narrative output meant for the Dreams UI. Daily memory files (memory/YYYY-MM-DD.md) should contain only event records and promoted long-term memory entries.

What actually happens

Example from memory/2026-04-13.md:

• ## Light Sleep section: 340 lines of Dream Diary narrative content
• ## REM Sleep section: 14 lines of REM narrative content
• No actual event records visible — entirely dominated by dream output

Evidence from memory/.dreams/events.jsonl:

"phase":"light", "lineCount":340, "storageMode":"inline"
"phase":"rem", "lineCount":14, "storageMode":"inline"

Both Light and REM phases write their full narrative output inline to the daily memory file, not just to DREAMS.md.

Expected Fix

Dream Diary narrative content should only be written to DREAMS.md. The ## Light Sleep and ## REM Sleep sections in daily memory files should contain only structural phase markers/metadata — not the full dream narrative output.

Environment

• OpenClaw 2026.4.12