Add smoke test for the live testnet deployment on every push to main

[Levi-Ojukwu]

Description
After each merge to main, a lightweight smoke test should verify that the testnet deployment is still functional. This catches breakages caused by testnet network upgrades or contract expiry without waiting for the nightly E2E run.

Requirements and context

• .github/workflows/testnet-smoke.yml triggered on push to main
• Smoke test: call get_version() and get_contract_stats() on all three deployed contracts, assert non-error responses
• Call the indexer's /health endpoint and assert status: 'ok'
• On failure: create a GitHub issue automatically with the error details using actions/github-script
• Timeout: fail if any check exceeds 30 seconds

Suggested execution

git checkout -b ci/testnet-smoke-test

• Create scripts/smoke-test.ts (or reuse from existing)
• Create testnet-smoke.yml workflow
• Test the auto-issue-creation on a deliberate failure

Example commit message
ci: add testnet smoke test on main push with auto-issue on failure

---

[adepoju2006]

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

I have experience writing GitHub Actions smoke test workflows for live testnet deployments. I'll create .github/workflows/testnet-smoke.yml triggered on push to main, calling get_version() and get_contract_stats() on all three contracts, hitting the indexer /health endpoint, and failing the workflow on any non-successful response.

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

[Bellamzy]

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

I'd really like the chance to work on this issue — I've been actively looking to contribute and gain real experience, and I have hands-on skills in debugging and GitHub workflows to back it up.
My plan: reproduce the problem, implement and test a clean fix, then open a focused PR for review.
This opportunity means a lot to me right now, and I'd put in the time to get it done right and quickly.

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

[QwinDivy]

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

Hi Maintainer, I'd love to take this one on. I've gone through the codebase and I'm comfortable with the approach needed here. I'll keep the change focused, add tests, and make sure CI stays green. Happy to open a draft early so we can align on direction.

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

[oscar24357]

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

Hello maintainer I'd love to work on this issue, please assign me to it.

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

[Ultra-Tech-code]

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

hello, I'd like to work on this issue.

I'll add a GitHub Actions smoke test workflow at .github/workflows/testnet-smoke.yml that runs on every push to main and validates the live testnet deployment. I'll implement checks for get_version() and get_contract_stats() across the deployed contracts, verify the indexer's /health endpoint returns an ok status, enforce a 30-second timeout per check, and configure automatic GitHub issue creation with failure details using actions/github-script.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ultra-Tech-code to this issue.

[drips-wave]

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

🧑‍💻 @Ultra-Tech-code: 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 🌊

[grantfox-oss]

🦊 GrantFox — @Ultra-Tech-code has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #366)
2. Your PR will be reviewed by the Invoice-Liquidity-Network maintainers

Good luck! Track your progress on GrantFox.