NEXO 7.9.23 — Richer lifecycle fallback diaries
Published 2026-04-24. Patch release over v7.9.22.
v7.9.23 tightens the emergency diary path added in v7.9.22. In real Desktop app-exit tests, the live shutdown prompt can still time out, and the fallback diary is then responsible for preserving continuity. The previous fallback was safe but too generic when the lifecycle event payload only carried minimal metadata.
What is fixed
Brain now enriches sparse lifecycle fallback diaries from durable continuity_snapshots for the same conversation/session. If the lifecycle event only says that an app-exit happened, the fallback diary can still recover the recent user/assistant turns and store them in session_diary.context_next.
Why it matters
Fallback diaries are not UX decoration. They are the last safety net when a live agent does not write the final diary before shutdown. The fallback must therefore preserve actionable context, not just prove that a close event happened.
Verification
Regression coverage pins continuity enrichment for minimal lifecycle payloads. A local NEXO Desktop 0.28.18 test opened a real conversation, exchanged five messages, closed the app normally, and confirmed the fallback session_diary preserved all five turns while the conversation remained active.