Applied Pluto migrations missing from registry can be skipped by registry-driven rebuild

Separate from PLUTO-774's current-effects census. Measured instance: migration 131-pluto-437-pacientes-identity-anchor.sql has no supabase_migrations.schema_migrations row (db-pluto-cc's postgres-role read recorded on PLUTO-774: latest registry entry 130), while db-pluto-ca's 2026-10-06 read-only production catalog check found its pacientes/pacientesArchive tables, columns, constraints, indexes, function bodies and archive trigger present. A registry-driven rebuild would skip a migration whose effects already exist. The catalog cannot witness a missing ledger row: current objects establish current schema, not registry completeness. Determine the full applied-but-unregistered set with an authorized registry reader, then decide the remedy; no ledger backfill or other write is pre-authorized. PLUTO-774's zero-absent-effects result does not resolve this replay risk.