Fix v0.7.8 release-status risk classification

[kforris]

Summary

• treat release candidate, readiness, notes, checklist, gate, status, policy, plan, and version references as nominal read-only context
• preserve high-risk routing when those nouns are attached to explicit actions such as prepare or ship
• cover the exact live roadmap/remaining-lifecycle query that exposed the post-deploy false positive

Verification

• npm run check: 82 passed, 13 environment-skipped
• six-case held-out evaluation unchanged at 1.00 with release-policy routing preserved
• 18-case production-shaped evaluation unchanged
• format, plugin cache digest, and production dependency audit passed

Boundary

Narrow post-deploy correctness follow-up for the same v0.7.8 milestone. No database, Swift, plugin payload, or lifecycle behavior changes.