chore: add workflow_dispatch inputs to ci-post-deploy-verify.yml for manual re-runs against a specific network

[misrasamuelisiguzor-oss]

Description

If ci-post-deploy-verify.yml only triggers automatically, an operator wanting to manually re-verify testnet or mainnet after an incident has no easy way to trigger it against a specific network without pushing a commit.

This is part of the CI/CD configuration under .github/workflows/, the automated gate that enforces every other guarantee this project claims to have, from ABI/contract consistency to documentation linting to coverage reporting. CONTRIBUTING.md lists specific required status checks that every PR must pass before merging, which means a gap in CI configuration doesn't just fail to catch a class of bug, it actively lets that class of bug merge to main with a green checkmark that reviewers reasonably trust.

Because CI is the one piece of the project every single contributor interacts with on every single PR, inefficiencies or blind spots here have an outsized multiplier effect: a slow or overly broad workflow wastes a small amount of time on every PR forever, and a missing check is a permanently open door for exactly the class of regression it should have caught.

Requirements and context

• Add a workflow_dispatch trigger with a network choice input (testnet/mainnet)

Suggested execution

1. Fork the repo and create a branch

   git checkout -b chore/post-deploy-verify-manual-dispatch
   

2. Implement changes

• Update .github/workflows/ci-post-deploy-verify.yml

3. Test and commit

• Manually trigger the workflow via the Actions tab for both network options

Example commit message

chore: add manual dispatch trigger to post-deploy verify workflow

Guidelines

• Assignment required before starting
• PR description must include: Closes #[issue_id]
• Keep PR description professional and detailed

[vicistar-star]

@vicistar-star has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.

I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.

My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.

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

[Good-terminal]

@Good-terminal has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer I will like to work on this issue please

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

[john2ydep2-gt]

@john2ydep2-gt has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

please i will love to work on this

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

[drips-wave]

Congratulations, @john2ydep2-gt! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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