openclaw - 💡(How to fix) Fix [Bug]: Compaction does not write summary to daily memory — regression of #79022

Bug Description

Compaction fires and shows the compaction message in chat, but the memory-flush summary is NOT written to memory/YYYY-MM-DD.md.

This is a regression of #79022 (closed May 7 2026 as fixed).

Environment

• OpenClaw version: 2026.5.18+
• Channel: Telegram
• Model: minimax-portal/MiniMax-M2.7

Configuration

"compaction": {
  "mode": "safeguard",
  "keepRecentTokens": 30000,
  "reserveTokensFloor": 30000,
  "identifierPolicy": "strict",
  "recentTurnsPreserve": 10,
  "memoryFlush": {
    "enabled": true,
    "softThresholdTokens": 8000,
    "prompt": "We are nearing a context limit. Summarize our progress today into memory/YYYY-MM-DD.md. If the file already exists, APPEND new content only."
  },
  "maxHistoryShare": 0.8,
  "notifyUser": true
}

Steps to Reproduce

1. Continue a Telegram conversation until compaction fires (~170k tokens)
2. Observe compaction message appears: 🧹 Compacting context (433 messages) so I can continue without losing history…
3. After compaction completes, check memory/YYYY-MM-DD.md
4. Expected: A summary of the compacted conversation has been appended
5. Actual: No summary written — file is unchanged from before compaction

Expected Behavior

When compaction fires, the memory-flush turn should write a summary of the conversation to memory/YYYY-MM-DD.md before the transcript is compacted.

Additional Context

• Manual daily memory writes work correctly (via heartbeat, edit tool, etc.)
• The issue is specific to the automatic flush on compaction
• No error visible in chat or logs — the flush silently fails
• Connected issues:
  • #79022 (closed fix — may have regressed)
  • #45608 (feature: /new and daily reset should also get memory flush — still open)
  • #63664 (session flush blocks write tool completely during compaction — P1, open)
  • #66612 (memory flush write sandbox blocks SESSION_HANDOFF.md — open)