NEXO 7.9.22 — Desktop lifecycle fallback diary
Published 2026-04-24. Patch release over v7.9.21.
v7.9.22 closes a real shutdown safety gap in the coordinated NEXO Desktop lifecycle flow. When Desktop closes, archives, or exits the app, Brain already owns the canonical plan: resume the linked session, inject the final diary prompt, confirm diary evidence, then stop the session. In the field, an app-exit path can still lose the live prompt response if the agent process does not answer before shutdown.
What is fixed
Brain now exposes an explicit fallback diary command for lifecycle events. If the live agent cannot answer the injected diary prompt, Desktop can ask Brain to write a desktop-lifecycle-fallback session_diary directly from the lifecycle payload snapshot. That fallback preserves the conversation title, current goal, Desktop/Claude/NEXO session ids, and transcript tail so the shutdown context is not silently dropped.
Why it matters
Close/archive/app-exit are data-preservation paths, not cosmetic UI transitions. A shutdown failure should remain visible and retryable, and if a live prompt cannot complete in time, the system should still capture enough context for continuity instead of pretending the diary happened.
Verification
Regression coverage pins fallback diary writing, diary evidence confirmation, canonical completion after fallback, and the coordinated Desktop behaviour that keeps app-exit failures retryable rather than abandoned.