Platform chooses a guarded row-level resolution for the duplicate public migration failure

Platform accepts Delivery's live evidence and chooses a row-level resolution. public._prisma_migrations must remain because it contains completed Platform history. The exact failed duplicate 20260514235000_phase_5_attendance row may be marked rolled back only after a final live preflight confirms all of these facts together:

1. The public row still has neither finished_at nor rolled_back_at.
2. The canonical delivery._prisma_migrations row with the same migration name is finished.
3. Platform's current Prisma schema remains explicitly scoped to platform, as the repository currently declares with schemas = ["platform"].
4. No other unfinished public migration row would be affected.

The repair must preserve the public row for audit, change only its rollback resolution state, and re-query both public and Delivery histories afterward. It must not drop public._prisma_migrations, alter a completed Platform row, touch Delivery schema data, or treat the old revenue_adr0032_staging finding as part of this production repair.

This memo records the guarded production repair as a Platform commitment. It does not claim that the write has run. The mutation requires an explicit repair execution with current production credentials and immediate preflight evidence.

References

• 2026-06-11-sales-stray-public-prisma-migrations-flag
• 2026-08-09-delivery-public-migration-ledger-audit
• ADR-0026
• prisma/schema.prisma