wazionapps/nexo

Coordinated with NEXO Desktop v0.18.0.

Plan Consolidado wave 2 closes the remaining Guardian roadmap items that do not require an invasive structure migration:

• Extended cognitive_sentiment shape (is_correction / valence / intent enum).
• Entities schema extension (aliases / metadata / source / confidence / access_mode) via idempotent migration m44.
• 21 labelled rule fixtures + R13 spike gates (FP < 5%, P95 < 3s).
• Fase F telemetry loops (aggregate_per_rule, FP grouping, FN candidate promotion) + Deep Sleep phase_guardian_analysis report.
• Local zero-shot classifier skeleton pinned to MoritzLaurer/mDeBERTa-v3-base-xnli-multilingual-nli-2mil7 @ b5113eb (previous pin failed model_type load under transformers 5.x). Consumer wired into src/hooks/auto_capture.py with threshold 0.65 + 40-char minimum + regex fast-path short-circuit.
• hook_guardrails respects NEXO_MIGRATING=1 (F0.0.4).
• personal_scripts gains origin column (F0.1) via idempotent migration m45.
• T4 LLM classifier gate wraps R15 / R23e / R23f / R23h with byte-parity between src/enforcement_engine.py and nexo-desktop/enforcement-engine.js.

Pre-release audit (2 parallel reviewers + re-audit pass):

• CRITICAL F-01 — Desktop JS T4 wire was dead code (method-name casing + async/await mismatch); fixed with regression test at nexo-desktop/tests/t4-wire-enforcement-engine.test.js.
• HIGH H1 — enforcement_classifier.classify conflated an explicit no with an unparseable conservative fallback, silently suppressing destructive rules on flaky backends; fixed with new tristate flag returning yes/no/unknown; unknown falls through to regex.
• HIGH H2 — otra vez removed from CORRECTION_SIGNALS to stop false-positive on benign repeats.
• F-02 — T4 gate degradations now log WARNING once per (rule_id, reason) so infra flakiness surfaces.
• F-04 — is_correction fallback tightened (requires 2+ all-caps OR second-person + 2 neg signals).

Deferred to a future release (not missing): F0.3–F0.6 physical structure migration and v7.0.0 breaking symlink removal. Infrastructure is in place (migrations_applied table, origin column, core/personal/runtime layout with symlinks), but the physical move requires coordinated validation on Francisco + Nora live runtimes per learning #450.