Deferred physical DROP of dead columns on the rutap.vehiculo_historial_normalizado view graph (carroceria_modelo first)

Follow-up from MOVILBA-468: carroceria_modelo is confirmed dead (zero live consumers, writer stopped 2026-10-09, coder03 70f0b96a/c949595c) but physically dropping it from rutap.vehiculo_historial_normalizado requires DROP+CREATE on its ENTIRE transitive view graph - 33 relations measured on DEV 2026-10-09 (32 dependent views), not just the 4 that reference the column directly, because DROP VIEW cascades on the whole view regardless of which column a downstream reader touches and CREATE OR REPLACE VIEW cannot drop a column at any position. Chain reaches public.v_vehiculos_api_public (published external API) and public.v_api_status, plus agents.v_vehiculo_lookup. Elazar/coder03 decision 2026-10-09: not worth the regen risk for one dead column alone - defer and BUNDLE with any other dead-column cleanup on the same graph so the 32-view regen pays for itself once. Do not attempt as a single-column change. Scope before touching anything: full pg_get_viewdef capture of all 33 relations + verified topological drop/create order (recursive pg_depend on rutap.vehiculo_historial_normalizado, not a column-level query - that undercounts).