Bug Description

Regression on v2026.4.29 (a448042): #64068 was closed as "resolved" on 4/12, but the dreaming promotion pipeline is still completely broken — 7 agents, 11 consecutive days of Promoted 0.

Environment

• OpenClaw 2026.4.29 (a448042), installed via Homebrew May 1
• macOS 15.4 arm64, Node.js v22.22.2
• 7 agents: general, coding, finance, health, network, study, truth
• Dreaming cron: daily 3AM Asia/Taipei (0 3 * * *)

Evidence

1. All 920+ entries have recallCount = 0

$ openclaw memory promote --agent general --min-recall-count 0 --json
→ 10 candidates, ALL with recallCount: 0, uniqueQueries: 1

2. Deep phase output — 11 days of zero promotions

Every day since 4/22:

# Deep Sleep
- Repaired recall artifacts: rewrote recall store.
- Ranked 10 candidate(s) for durable promotion.
- Promoted 0 candidate(s) into MEMORY.md.

Only 4/21 had Promoted 1 — the last successful promotion.

3. All 7 agents' MEMORY.md frozen

coding   last modified 2026-04-27
finance  last modified 2026-04-27
general  last modified 2026-04-25
health   last modified 2026-04-27
network  last modified 2026-04-30
study    last modified 2026-04-24
truth    last modified 2026-04-23

4. Cron job runtime collapsed

Before 4/25 update: ~420-580s per run (full candidate processing)
After  4/25 update:  ~25-52s  per run (summary = "NO_REPLY")

The agent is no longer processing dreaming data — 15x runtime reduction.

5. CLI workaround proves data is there

$ openclaw memory promote --agent general --min-recall-count 0 --min-unique-queries 1 --limit 10
→ Returns 10 candidates with scores 0.807-0.888

Candidates exist with high scores, but recallCount stuck at 0 prevents promotion.

Root Cause (from #64068)

The normalized recall artifacts before dreaming (rewrote recall store) step resets recallCount to 0 on every dreaming cycle, making promotion permanently impossible. The fix committed for #64068 (which closed it 4/12) appears to have been regressed or was incomplete.

Expected Behavior

• recallCount persists and accumulates across dreaming cycles
• High-signal entries eventually promoted to MEMORY.md
• Agents build long-term memory over time

Related

• [Bug]: memory-core dreaming promotion always finds 0 candidates - recallCount never accumulates (normalized recall artifacts resets scores) #64068 (closed as "resolved" 4/12, but still broken on 4.29)
• Dreaming: dayBucket uses file date instead of ingestion date, preventing dailyCount from growing and blocking short-term promotion #67061 (closed, no comments)
• Expose dreaming promotion thresholds (minScore, minRecallCount, minUniqueQueries) as user config #65402 (closed, feature request for configurable thresholds)