Add docs for database migration naming conventions and rollback process

[Chucks1093]

Summary
Database migrations lack a documented naming convention and the rollback process is not described anywhere. Contributors adding migrations need to know the naming rules and how to safely roll back a migration in development and production.

Scope

• document the naming convention for migration files including the timestamp and description format
• describe the rollback process for development and production environments
• note any migrations that are considered irreversible and why

Acceptance Criteria

• the migration naming convention is documented with an example
• the rollback process is described for both environments
• no code changes are required; this is a docs-only issue

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[wavyboy-build]

@wavyboy-build has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Pls assign me this issue

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

[drips-wave]

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

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

[Oyintarede]

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

Hi, I would like to work on this project.

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

[hally-Ayo]

@hally-Ayo has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, Maintainer can I work on this Issue?

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

[shadrach68]

I would like to work on this issue because I am a full-stack developer with 5+ years experience. I focus on identifying root causes and delivering clean, efficient, and maintainable solutions, with thorough testing to ensure reliable results.

[Osuochasam]

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

Dear maintainer, pls assign me to this issue

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

[Richardkingz2019]

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

Hi maintainer, I would love to work on this issue. I have studied the details of the issue description and I understood the requirements. I shall deliver with qualitative feedback and promptly

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

[Benedict315]

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

Hello please assign me to this issue

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