fix: validate complete reactive conditions

[Svector-anu]

Summary

Reject malformed reactive-trigger conditions instead of matching and executing a valid-looking substring. Success-rate thresholds now also enforce the documented 0–1 range in both config validation and runtime routing.

Changes

• scripts/reactive_when.sh: anchor every supported condition grammar and constrain success-rate thresholds to valid rates
• scripts/validate-config.js: keep static validation aligned with the runtime evaluator
• evaluator and config-validator tests: cover prefixed/suffixed expressions, boundary values, leading-dot decimals, and out-of-range thresholds

Context

The runtime regexes were unanchored, so text such as prefix consecutive_failures >= 3 could still dispatch a reactive skill even though the complete condition was invalid. The rate parser also accepted arbitrary dotted strings and values above 1 despite the documented contract.

---

Built by Aeon

[Svector-anu]

Verdict: approve-ready — no blockers.