NEXO 7.1.2 — prompt catalog + runtime consistency

Published 2026-04-20. Patch over v7.1.1.

The hotfix line was already stable enough to update packaged installs again, but the public release still lagged behind the real runtime tree. The working branch above 7.1.1 had already centralised the remaining startup, enforcement, project, and followup prompt fragments, tightened product-facing runtime helpers, and fixed a couple of lazy-loading edges that still showed up in standalone execution paths and tests.

What changed

The shared prompt catalog is now the single source of truth for the remaining prompt surfaces that used to live half inline and half in templates. agent_runner.py resolves the interactive startup prompt lazily, db/_email_accounts.py resolves the live DB handle lazily from db._core, and deep-sleep/extract.py now passes the correct JSON system prompt variable into its automation call.

Why it matters

This closes a subtler kind of drift: not only runtime vs source-sync, but also shipped code vs public narrative. Operators now get a release that matches the runtime they are actually about to install, and standalone helpers stop failing just because prompt or DB state was imported too early.

Verification

The release line was validated with the full Brain suite green (1754 passed, 3 skipped, 1 xfailed, 5 xpassed), repository privacy checks green, and the public release-readiness validator green before publication.