nx_gate_verdict_lib.nx

nx_gate_verdict_lib.nx -- the SHARED reader for "what does this gate log say?". NO main() ON PURPOSE. WHY A MODULE AND NOT A NOTE: nx_gate_rollup.nx owns a main(), so its gr_slurp/gr_last_line cannot be imported by a second entry point -- the same structural trap nx_gatelib's own header documents for egb_walk/tr_walk ("that is why it kept being copied rather than shared -- a structural reason, not an oversight, and the fix is a module with no main() rather than a note promising to do it later"). This is that module. New readers import it instead of copying; nx_gate_rollup folds into it next. THE VERDICT CONTRACT, in one place so it cannot drift again: a gate log's NEWEST non-empty line carries the anchor. The ecosystem emits BOTH cases -- knowledge/status/deploy_ready.log, fin_spine_gate.log, coordination_gate.log and pm_dashboard_gate.log use uppercase VERDICT=, while rv64_runproof_gate.log and friends use lowercase verdict=. nx_gate_rollup matched lowercase ONLY, which made every uppercase gate read RED the instant it was registered. Case is a spelling detail, not a verdict; both are accepted here so no future reader has to rediscover that. FAIL-CLOSED: missing / empty / no-anchor is GV_NONE, never GREEN. "I could not tell" must never read as "fine" -- that is the failure mode the gate plane exists to remove. license_tier: ORIGINAL No hw writes (Rule 26).