Implement contract hot-reload development workflow with Soroban CLI

[Smartdevs17]

Context

Developing Soroban contracts requires a manual compile -> deploy -> test loop that takes 30+ seconds per iteration, severely hampering productivity.

Current Limitation/Problem

No hot-reload for contract development. Each code change requires cargo build, deploy WASM to testnet, and invoke contract tests.

Expected Outcome

Watch mode: filesystem watcher automatically re-compiles contracts on source change, deploys to local Soroban standalone, and runs contract integration tests. Iteration time <3s.

Acceptance Criteria

• File watcher: chokidar or fswatch monitoring contracts/**/*.rs for changes
• Incremental rebuild: on change, run cargo build --target wasm32-unknown-unknown for changed crate only
• Redeploy: deploy new WASM blob to local Soroban standalone node
• Test runner: run affected contract integration tests after deploy
• Error reporting: compilation errors displayed with file:line:col and error message
• Skip unchanged: contracts not modified are not rebuilt (incremental compilation)
• Performance: full loop (save -> rebuild -> redeploy -> test result) <3s for single contract change
• Edge case: multiple changes in rapid succession (debounce 500ms)

Technical Scope

• scripts/contract-watch.sh - watch mode orchestrator
• scripts/contract-build.sh - incremental build with dependency graph
• contracts/Makefile - make watch target with hot-reload flag
• .github/workflows/contracts.yml - CI uses same build script
• docs/CONTRACT_DEV.md - hot-reload workflow documentation

[Oluwasuyi-Timilehin]

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

Hello maintainers I'm a full stack developer experience in building scalable systems I can handle this perfectly if assigned

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

[Dev-Ben-Theo]

@Dev-Ben-Theo 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

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Dev-Ben-Theo to this issue.

[drips-wave]

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

🧑‍💻 @Dev-Ben-Theo: 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 🌊