Feature: contract upgrade + migration runbook with on-chain version surfacing

[Psalmuel01]

Contracts support upgrade, but there is no clear operational runbook or a way for clients to see the deployed contract version.

Scope

• Add a version view to each contract returning a semantic version/build id, and surface it in the app footer and /api/ready.
• Write a migration runbook: how to upgrade, verify the new WASM hash, and roll back, including data migration steps for record shape changes.
• Emit an event on upgrade.

Value

Safe, transparent upgrades with client-visible versioning.

Acceptance

• Each contract exposes its version; clients display it; a documented upgrade/rollback runbook exists.

[badmusdare4]

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

Hello maintainer can I work on this.

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

[franklin251861-killer]

@franklin251861-killer has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like to work on this issue, assign it to me.

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

[Anadudev]

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

Hi Maintainer, I would like to work on this issue

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

[Risktaker001]

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

Hi, I'd like to work on this issue!

I will implement a version view query in the contracts that returns semantic versioning metadata and emits an upgrade event on contract updates. I'll also expose the deployed version in /api/ready and the frontend footer, and author a detailed migration runbook covering WASM hash verification, state migration, and rollback steps.

Please assign this to me!

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

[drips-wave]

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

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