NEXO 7.22.0 — MCP latency hardening and Entity Dossier

Published 2026-05-17. Release over v7.21.0.

Why this release exists

Desktop conversations must not wait on heavy Brain work before the first useful reply. v7.22.0 keeps routine MCP calls fast, moves critical writes into an honest queued/committed path, and exposes the compliance state Desktop needs to block only at the right boundaries.

What changed

• Fast Desktop heartbeat. Desktop-managed heartbeat no longer loads Local Context, drive analysis or semantic correction classifiers unless explicitly forced.
• Durable write queue. Critical writes can be accepted as queued, drained by one runtime writer, and resolved as committed, retrying or dead_letter.
• Compliance state for Desktop. Brain exposes heartbeat, diary, learning and close obligations so Desktop can enforce them before the next visible turn or clean close.
• Entity Dossier. Local Context can aggregate all evidence linked to an entity, canonicalize aliases, extract open-domain facts and return quantified summaries without changing the existing semantic top-K search route.
• Load-safe Local Memory. Desired index speed persists under sidecar DB contention and Desktop foreground state can throttle indexing while a conversation is active.

Validation

python3 -m pytest tests/test_local_context_entity_dossier.py tests/test_runtime_write_queue.py tests/test_session_compliance_state.py -q
# focused MCP, durable queue, compliance, privacy and dossier coverage passed

Full changelog entry → · Previous Local Memory semantic model note