nx_recall_or_red_gate.nx

nx_recall_or_red_gate.nx -- THE LOCK for the "recall-or-RED" guarantee (the no-unseen-repeat law). Structural twin of the no-hang error-emit keystone: just as nx_netscope T2 proves every error PATH emits a verdict within a deadline (never hangs), THIS proves every SEEN issue is RECALLED + ROUTED to its remedy (never a silent "can't identify/fix this if we've seen it before"). A regression that lets a catalogued signature go unrecognized turns this gate RED within one heartbeat. HERMETIC: the gate seeds its OWN test store (knowledge/store/kigate-) with controlled fixtures (clearly T-* ids -- NOT production claims), so recall is exercised over MULTIPLE signatured rows (proving a real DATA-driven table walk, not one hardcoded branch). Assertions: T1 recall completeness : a diagnostic embedding row T-RKW's signature -> HIT, id=T-RKW T2 route correctness : that hit routes to remedy nx_doctor_fix:doc_heal_token + status AUTO T3 second-row recall : a diagnostic embedding row T-SEGV's signature -> HIT, id=T-SEGV T4 neg-control : a genuinely novel diagnostic -> UNKNOWN (no rubber-stamp; UNFIXABLE stays legal ONLY for truly-unseen issues -- twin of T5 no-false-positive) T5 tamper : corrupt the matched signature in the diagnostic -> recall MISSES (UNKNOWN) -- proves the match is a real substring, not a constant TRUE (twin of BL-011 tamper discipline) GREEN only if T1 .. T5 all hold. Evidence -> knowledge/status/recall_or_red.log. license_tier: ORIGINAL