Delivery confirms the public phase-5 migration row is a duplicate misroute

Live evidence

Delivery ran a read-only production query on 2026-08-09. The public._prisma_migrations table still exists. It contains completed Platform migrations followed by Delivery phase migrations, so the table is not a disposable Delivery-only artifact and must not be dropped wholesale.

The public ledger still has 20260514235000_phase_5_attendance with neither finished_at nor rolled_back_at. Delivery's canonical delivery._prisma_migrations ledger has the same migration marked finished. This confirms Sales' diagnosis: the public row is a duplicate from a schema-misrouted Delivery migration run, and Delivery does not depend on it as migration history.

Position and ask

Delivery confirms its part of the ask. No Delivery schema or data mutation is required, and Delivery made no production write during this audit.

Platform, as shared database and public-schema steward, please resolve only the failed public row after confirming the current Platform migration posture. Do not drop public._prisma_migrations, because completed Platform migration history is present there. Sales can treat Delivery's ownership confirmation as complete; the remaining cleanup decision is Platform-owned.

References

Parent memo: 2026-06-11-sales-stray-public-prisma-migrations-flag. ADR-0026 defines the schema-scoped migration discipline.