test: add a CI job that runs make update-abi-snapshots and fails if regenerated files differ from committed abis/

[misrasamuelisiguzor-oss]

Description

This may overlap with ci-abi-metadata.yml/ci-abi-snapshots.yml, but if those workflows check ABI metadata format rather than actually regenerating and diffing, adding an explicit regenerate-and-diff job would give a stronger correctness guarantee that abis/*.json truly reflects current contract source.

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

• Confirm existing ABI CI jobs regenerate-and-diff rather than schema-check only; add the stronger check if missing

Suggested execution

1. Fork the repo and create a branch

   git checkout -b test/ci-abi-regenerate-diff-check
   

2. Implement changes

• Update .github/workflows/ci-abi-snapshots.yml or add a new job

3. Test and commit

• Deliberately edit a contract without updating abis/ on a test branch and confirm CI fails

Example commit message

test: add regenerate-and-diff enforcement to ABI snapshot CI

Guidelines

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

[samuelelijah585]

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

Hello, I've reviewed the issue and its acceptance criteria, and I'm confident I can deliver a solution that meets the requirements. I'd appreciate it if you could assign this issue to me. Thank you!

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

[JClark011]

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

Hi maintainer Let me work on this issue
I'll definitely give you quick response

ℹ️ Repo Maintainers: To accept this application, review their application or assign @JClark011 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.

[Engr-Able]

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

Hello Maintainer, I’ve read through the issue description and have a clear understanding of the expected outcome. I’d be pleased to take on this task and contribute a quality solution to the project.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Engr-Able 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 🌊