Write contract upgrade guide covering schema migration and governance workflow

[Emeka000]

Summary

Upgrading a live Soroban contract requires multi-sig approval, schema compatibility checks, and coordination. There is no documentation walking operators through this process.

Guide Sections

1. Pre-upgrade checklist: schema compatibility, test coverage, staging deployment
2. Governance proposal submission: how to create and submit a WASM upgrade proposal
3. Multi-sig approval collection: minimum signers, timeout handling
4. Schema migration entry point: how to write and invoke migrate_schema
5. Rollback procedure: what to do if post-upgrade verification fails
6. Testnet dry run: how to simulate the upgrade before mainnet

Acceptance Criteria

• Guide written at docs/upgrade-guide.md
• Each section has a concrete example command or code snippet
• README links to the guide

[Emoji-dot]

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

I would like to work on this issue please

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

[temitope-007]

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

Hi maintainer

I'd like to take up this issue

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

[rahimatonize]

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

Hi maintainer, I would love to work on this issue

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

[rasputin2525]

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

hi team kindly assign me i can work on this issue

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

[drips-wave]

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

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