chore: add generate_abi_metadata to CI on contract change

[misrasamuelisiguzor-oss]

Description

Add a CI workflow step that automatically runs scripts/generate_abi_metadata.sh whenever files under contracts/ are changed. This ensures that ABI snapshots in abis/ are always regenerated and committed as part of any PR that modifies contract source, preventing stale metadata from reaching the main branch.

Requirements and context

• Trigger the CI step on pull requests where any file under contracts/ is modified
• Run scripts/generate_abi_metadata.sh as part of the workflow
• Fail the CI job if the resulting abis/ diff is non-empty (snapshots not committed)
• Optionally auto-commit regenerated snapshots back to the PR branch
• Follow existing project conventions

Suggested execution

1. Fork the repo and create a branch

   git checkout -b chore/abi-metadata-ci-automation
   

2. Implement changes
3. Test and commit

Example commit message

chore: auto-run generate_abi_metadata.sh in CI on contracts/ change

Guidelines

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

[Fayyo]

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

Hi! I'd like to work on this issue.

I have experience with GitHub Actions, Rust contract workflows, and CI automation. I'll update the workflow to run scripts/generate_abi_metadata.sh whenever files under contracts/ change, fail CI if abis/ contains uncommitted changes, and ensure the workflow follows the project's existing conventions.

I'll include Closes #117 in the PR description and submit a PR with the workflow updates and documentation if needed.

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

[Good-Coded]

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

Hi, I’d like to take on this issue.
I have experience working with smart contracts, backend systems, and frontend integrations, and I’m comfortable implementing solutions that are deterministic, secure, and aligned with existing architecture. I focus on writing clean, maintainable code with proper validation, error handling, and test coverage to ensure stability and reliability.
For this task, I will follow the existing code patterns in the repository, avoid breaking changes, and ensure the implementation passes all integrity checks. I will include comprehensive tests covering edge cases and expected behavior, and make sure everything integrates smoothly without introducing regressions or performance issues.
I’ll also provide clear documentation where needed so the changes are easy to understand and maintain going forward.
Let me know if you’d like me to proceed or if there are any specific considerations I should be aware of.

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

[drips-wave]

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

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