Issue 31: CI/CD - Automated Testnet Deployments and Tagging

[soomtochukwu]

Description:
Connecting code theory into practical deployment mechanisms validates the true capability of the framework. This final CI/CD issue governs constructing a GitHub workflow triggering solely upon merging into the development or main branches. It instructs the server environment to meticulously build the finalized .wasm smart contract architectures, authenticate securely with the core Stellar CLI accessing heavily guarded GitHub secrets, and autonomously deploy the generated contracts directly against the Stellar Futurenet or Testnet structures. It must automatically dump output generated contract IDs back into the repository environment variables confirming synchronization so the frontend seamlessly connects reflecting exact cutting-edge logic updates rapidly.
Requirements:

• Script out ./.github/scripts/deploy-contracts.sh executing deterministic deployments leveraging heavily protected CI secrets configuration securely.
• Update global repository environmental mapping (.env.local simulation points) reflecting dynamic contract IDs produced post-deployment.
• Build trigger dynamics orchestrating backend and frontend deployments pushing architectures onto cloud providers (Fly.io / Vercel automatically) using CLI actions simultaneously.
• Integrate comprehensive deployment tag notifications echoing inside internal developer workflows signaling testnet environment refreshed mechanics clearly.
  Acceptance Criteria:
• Merging to explicitly protected staging branches triggers automated testnet ledger injection flawlessly without manual dev intervention implicitly.
• Subsequent updates strictly update relative environment links dictating perfect harmony spanning blockchain parameters to localized UI rendering contexts fully.
• Extensive logs document precisely which contract version configurations generated which IDs tracking architectural evolution smoothly.

[ayomideadeniran]

@ayomideadeniran has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I'm a full-stack developer and I'd like to take this issue.
I understand the requirements and will follow the existing project structure, keep the implementation clean, and include proper tests where applicable.

ETA: 1–3 days (depending on scope)
Portfolio: https://knightsdev-portfolio.vercel.app/

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

[drips-wave]

Congratulations, @ayomideadeniran! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

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

[drips-wave]

This issue has been completed by @ayomideadeniran as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @ayomideadeniran: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.