openclaw - 💡(How to fix) Fix feat: Add session:disconnect event for automatic memory archival on TUI close

Problem

Currently, the session-memory hook only triggers on /new or /reset commands. When a user closes the TUI through any other means, the session context is not automatically archived to memory files. This means if the agent didn't manually write to memory/YYYY-MM-DD.md during the conversation, that day's context is lost from the agent's working memory after a daily reset.

When to Trigger Archival

Trigger memory archival when a session is permanently ending and cannot be resumed:

Proposed Solution

Add a new event type: session:end that fires when a session is permanently ending.

Hook integration

Extend the existing session-memory hook:

Events: command:new, command:reset, session:end

Benefits

1. Zero lost memories: Every session's context is preserved when it truly ends
2. Zero user friction: Works automatically, no habit change needed