BE-110: Unify Database Migration Strategy Across Modules

[Cedarich]

Labels: Backend, Stellar Wave, database, architecture, devops
Complexity: Hard (200)

Description
Migrations are scattered per-module (branch-preview/migrations/, crash-reporting/migrations/) with no single ordered history or shared runner. There is no reliable way to know whether a database is fully migrated, which is exactly the class of problem behind CI database failures. Consolidate on one migration mechanism with a deterministic order.

Acceptance Criteria

• All existing module migrations are consolidated into a single ordered migration history.
• One documented command applies all pending migrations from a clean database.
• Migration state is queryable so an environment can be verified as up to date.
• Applying migrations twice is a no-op.
• The consolidation is verified by provisioning a clean database in CI and running the full suite.

[drips-wave]

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

🧑‍💻 @oluwapelumiakinola74-dotcom: 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 🌊