W2-B-046 - Migration order is inconsistent (file timestamps vs content)

[likableai]

Severity: Medium | Area: backend/migrations | Evidence: prisma/migrations/ mixes 20260129..., 20260418..., 20260423... names and two _init migrations (20260129225314_init, 20260423111042_init)
Impact: Confusing history; risk of double-applied init on fresh clones. Fix: Rebaseline the migration history to a single coherent sequence. Acceptance: Fresh DB migrate succeeds with only required migrations.

[drips-wave]

Congratulations, @Gunshots-debug! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Gunshots-debug: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊