08 — Repoint Feasibility

The existing candidate is useful (full-column parity proven) but NOT directly repointable because it is circular: its decoration comes from the _current alias, which is exactly the view a repoint would redefine — repointing _current to a view that reads _current would recurse.

Introspection confirmed the structures. v_rp_universal_node_ui_contract_current is a pure pass-through alias: it selects the 34 decoration columns from v_rp_universal_node_ui_contract_current_v2 with no filter or transform. The candidate joins backbone g (v_rp_universal_node_ui_contract_generated_v2) left-join decoration c (v_rp_universal_node_ui_contract_current) using axis_code and node_code.

The safe non-circular fix is mechanical: keep the same view but source decoration from _current_v2 directly instead of the _current alias. Because _current equals _current_v2, the output is unchanged while the recursion path is removed. This is OOM-safe (such a view references at most two deep stacks and never the smoke probe, so the detector rates it SAFE or SLOW_BOUNDED, never a landmine), authority-free for the backbone swap itself, and an operator step. The macro therefore proceeded to Phase 9 to build it.