Add non-interactive CI smoke-test artifact validation for every release candidate

[usmanimamu17-create]

Problem Statement
The testnet deploy workflow is manual and produces artifacts, but there is no non-interactive validation gate that proves the release candidate is safe to promote.

Why it matters
Deploying a contract from a release branch without a formal validation gate creates unnecessary human error risk.

Technical Context
The deploy workflow lives in .github/workflows/testnet-deploy.yml, while the build and hash workflow is in .github/workflows/release-hash.yml.

Expected Outcome
A deterministic release-candidate validation gate that verifies build success, artifact integrity, and smoke-test expectations.

Acceptance Criteria

• A release validation checklist exists.
• The validation can be executed in CI without manual intervention.
• The artifact hash and smoke test results are recorded in a reviewable form.

Implementation Notes
Prefer failures on clear validation criteria rather than broad manual review.

Files or modules likely to be affected

• .github/workflows/testnet-deploy.yml
• .github/workflows/release-hash.yml
• SECURITY.md

Dependencies (if any)
Release maintainer approval policy.

Difficulty level
Medium

Estimated effort
M

[shaarknado]

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

I would love to work on this task

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

[onakijames-droid]

@onakijames-droid has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer I can work on this issue and submit a PR for it ASAP

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

[Richardkingz2019]

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

i would love to work on this

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

[drips-wave]

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

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