fix(validation): honor zero-aligned probe overrides

[luisleo526]

Summary

• apply declared expected_tier and expect_tv_match=false overrides to non-empty zero-alignment results
• keep the explicit zero-match branch so fully unaligned rows cannot fall through the small-N coverage waiver
• share normal and zero-aligned override precedence without changing existing matched-path behavior
• print -> <label> for zero-aligned results so probe builders receive a verdict
• pin valid, malformed, both-empty, single-sided, precedence, printer, and CLI exit behavior

Why

The zero-alignment early return ran before both documented-divergence overrides. A probe explicitly declared anomaly or engine_only was reported as Minimal, printed no verdict label, and exited 1. This is live for the special-validation limitation-probe class, although it has no current public corpus or scraper score impact.

Validation

• two independent final reviews: GO
• focused metric suite: 16/16
• adversarial normal-path truth table: 250/250 exact
• base-vs-candidate differential matrix: 27 cases, 0 unexpected differences
• CTest: 112/112
• validation-report fixtures: 3/3
• doctest and C ABI source check
• public corpus: 252/252, unchanged at 247 Excellent / 4 Strong / 1 anomaly / 0 engine_only
• full verbose base-vs-candidate corpus output: byte-identical
• py_compile and git diff --check

The only intended behavior change is for a non-empty zero-alignment result carrying a valid documented-divergence declaration. Both-empty Excellent, malformed metadata, every normal matched label/metric, and override precedence remain base-identical.