Testing: enforce storage/event snapshot drift in CI

[josephchimebuka]

Summary

CI currently prints snapshot advice if snaps exist but does not hard-fail. Add real snapshot fixtures or remove the dead step.

Acceptance criteria

• Either: snapshots committed + CI fails on drift
• Or: remove misleading CI step
• Document regenerate script

Where

• .github/workflows/ci.yml
• contracts/test_snapshots/

[Peolite001]

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

i would love to work on this issue

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

[Nife-tanny]

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

Hi Maintainer. Please I'll like to work on this issue.

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

[drips-wave]

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

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Nife-tanny as part of the Stellar Wave Program's 8th Wave 🥳

Moderator's reason: [Auto-assessed] The PR correctly addresses the issue by removing the non-enforcing, dead snapshot drift CI step, associated script, and documentation as requested by Path B of the issue. The diff is clean, fully reviewable, and has no maintainer objections across any channels.

😎 @Nife-tanny: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.