[CI] No migration-from-scratch job - the 32 backend migrations are never applied against a fresh Postgres in CI, so collision/ordering bugs only surface on the staging server

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

ci.yml backend job has no services: Postgres and never runs npm run migrate:up; it sets DATABASE_URL but no DB is provisioned. The first place migrate:up runs end-to-end is deploy-staging.yml line 182 (on the live server). With known duplicate timestamp prefixes (e.g. 1777000000007, 1778000000008, 1786000000016, 1788000000018 each appear twice) and the ensure-core-tables vs loan_events collision, a broken from-scratch apply ships to staging undetected.

Acceptance criteria

• A CI job spins up a Postgres service and runs npm run migrate:up from an empty schema, failing on any error
• It also exercises a migrate:down (or up/down/up) cycle to catch irreversible/ordering issues
• Job runs on PRs that touch backend/migrations/

Files to touch

• .github/workflows/ci.yml
• backend/migrations
• backend/package.json

Out of scope

• Fixing the individual migration ordering bugs (already filed)
• Seeding production data

[mordabdul1]

Hi Maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately.

[Killerjunior]

@Killerjunior has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, I have read and understood the issue requirements and checked the necessary documentation. I’m confident I can work on this task effectively and deliver a proper solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Killerjunior to this issue.

[MethelyDev]

@MethelyDev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, i would like to work on this issue, kindly assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MethelyDev to this issue.

[grantfox-oss]

🦊 GrantFox — @MethelyDev has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1252)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @MethelyDev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@MethelyDev's PR #1259 was approved and merged by @ogazboiz.

🏆 @MethelyDev: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (156 total points). Track your full progress on GrantFox.

👏 Great work, @MethelyDev! Keep contributing to LabsCrypt.

[drips-wave]

This issue has been completed by @MethelyDev as part of the Stellar Wave Program's 6th Wave 🥳

😎 @MethelyDev: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.