NEXO 7.9.26 — automation language contract
Published 2026-04-25. Patch release over v7.9.25.
v7.9.26 makes the operator-language contract part of the central headless automation runner. Reports, diaries, syntheses, followups, escalations, and other user-facing automation output now inherit the calibrated language even when the underlying product prompt is written in English.
What changed
run_automation_prompt now appends the operator-language contract for operator-facing callers before launching Claude Code or Codex automation. Pure machine-only calls such as backend probes, context checks, and learning validation remain unchanged so exact machine contracts keep working.
Deep Sleep is deterministic
Deep Sleep extraction and synthesis prompts no longer ask the model to find calibration.json opportunistically. They now rely on the automation runner to inject the language contract, while JSON keys remain stable in English for parsers.
Why it matters
Overnight memory, morning agendas, daily synthesis, postmortems, and autonomous maintenance reports often start from English templates. The user should still receive natural output in their configured language without each script remembering to pass language context manually.
Verification
Regression tests cover operator-facing language-contract injection, machine-only caller exclusions, Deep Sleep caller coverage, and Claude/Codex prompt construction after the central injection point.