[Backend] ensure-core-tables migration CREATE TABLE loan_events collides with the loan_events compatibility view, breaking a clean migration apply

[grantfox-oss]

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

Why this matters

Migration order by timestamp: 1788000000018_unified-contract-events.js renames the loan_events table to contract_events and creates a VIEW named loan_events (lines 7,52-69). The next migration 1789000000000_ensure-core-tables.js:31-37 guards with IF NOT EXISTS (SELECT FROM pg_tables WHERE tablename='loan_events') THEN CREATE TABLE loan_events (...). pg_tables only lists ordinary tables (relkind r/p) and excludes views, so the guard evaluates TRUE and runs CREATE TABLE loan_events, which fails with relation loan_events already exists because the view occupies that name. On any from-scratch sequential migration the run aborts.

Acceptance criteria

• Detect the relation via pg_class / information_schema.tables (which include views) or use to_regclass('loan_events') instead of pg_tables
• Make the CREATE TABLE branch a no-op when loan_events already exists as a view
• Add a CI step that runs the full migration set against an empty database

Files to touch

• backend/migrations/1789000000000_ensure-core-tables.js
• backend/migrations/1788000000018_unified-contract-events.js

Out of scope

• Scores column rename runtime mismatch (already filed)
• Indexer inserting into the view (already filed)

[Turawa2]

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

I can work on the issue perfectly .

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

[raymondidahor-bot]

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

I would love to work on this project. I promise to deliver within a short time.

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

[leojay-net]

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

I would like to work on this issue.

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

[grantfox-oss]

🦊 GrantFox — @leojay-net has been assigned to this issue!

Next steps:

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

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @leojay-net: 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!

@leojay-net's PR #1124 was approved and merged by @ogazboiz.

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

👏 Great work, @leojay-net! Keep contributing to LabsCrypt.