07 — Decorated Candidate Recheck

The pre-existing circular candidate v_rp_universal_node_ui_contract_decorated_generated_candidate was re-verified live.

v_rp_decorated_generated_full_column_parity (function-backed): verdict DECORATED_GENERATED_FULL_COLUMN_PARITY_PASS — 87/87 matched, gen_only 0, cur_only 0, count_value_diffs 0, decoration_found 87, decoration_missing 0, route 87, action 87, reliability 87, substrate 81 (by-design NULLs on empty-by-design WPC and synthetic nodes), warning 87, next_action 87; row_parity, count_parity, decoration_complete, route/action/reliability parity all true.

v_rp_generator_replacement_readiness_dashboard: parity PASS, guard PASS, db_side_ready true, oom_verdict OOM_SAFE, live_crash_landmines 0, repointed false, no_hardcode_ready false, verdict DECORATED_GENERATED_REPOINT_READY_OPERATOR. The note explains the circularity: the candidate sources decoration from the _current alias (equal to _current_v2), so a real repoint must rewire decoration to _current_v2.

No OOM risk in the parity check (it is function-backed, SAFE_FUNCTION_BACKED). Rollback for the candidate package exists (RUNBOOK_v2 section 4).