NEXO 7.15.0 — shared continuity, multilingual recall, and automation hardening

Published 2026-05-07. Minor release over v7.14.0 — closes the generic product gaps from the shared Brain/Desktop audit without adding operator-specific behavior.

Sent email continuity now has one sink

Successful sends from the monitored reply path and the direct SMTP CLI now write the same durable event shape: message id, sender, recipients, subject, source, metadata, and body text. Cognitive memory ingests the same evidence so parallel clients can recall what was already sent instead of repeating or denying it.

Recall is multilingual and context-aware

The local embedding manifest now points to a pinned multilingual model and existing cognitive databases are backed up and re-embedded when the model marker changes. Learning recall also gains a tag/category/source floor, so declared operating context can load matching learnings with strength at least 1.0 even when the current wording drifts.

Automation has harder guards

The email monitor now maintains a durable thread-key cooldown for self-sent or repeated internal threads. Headless runners check the shared guard before mutable automation starts. The protocol enforcer suppresses passive reinjection loops after a clean task close while still re-arming when genuinely new work begins.

Operators get better evidence

nexo_learning_list exposes creation timestamps and date filters. Daily self-audit writes an idempotent postmortem when AUTO-N session bursts exceed the threshold. Doctor now includes a bootstrap coverage check for recent Codex sessions that did not reach startup.

Validation

PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 pytest -q -x
python3 -m compileall -q src scripts tests
scripts/pre-release-verify.sh --release v7.15.0

Full changelog entry → · sent-email sink · learning context floor · post-close cooldown