Fuzz seed corpus plus Makefile `make fuzz` actually executing tests

[miss-yusrah]

Complexity: High (200 points)

Why this matters
Make fuzz is the contributor entry point and currently a no-op. Seeds make failures reproducible.

Problem
Makefile fuzz target does not run tests. No FUZZ_SEEDS. REGISTRY_INVARIANTS.md is fiction until this lands (compose with the property-fuzz issue; this one is the corpus + make target plumbing).

What "done" looks like

• make fuzz runs non-zero tests.
• Seed files or env FUZZ_SEEDS.
• README accurate.
• If property tests already exist, this issue is wiring + seeds only — don't duplicate.

Scope

• In: Makefile + seeds + README/invariants truth.
• Out: AFL on WASM (probably overkill).

Guidelines

• Key files: Makefile, README.md, docs/REGISTRY_INVARIANTS.md
• Watch for: Empty target, timeout, duplicate test names.
• Constraints: Must execute in CI or documented nightly. Not echo skipped.
• Validate: make fuzz

PR must include

• Working make fuzz
• Seeds
• Docs match

[VikkyFame01]

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

Hi Maintainer, I’ve carefully gone through the issue and I’m capable of getting it fixed , please assign me.

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

[harmondconsultant-png]

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

I’d like to take this issue and drive it through to completion. I’ve reviewed the requirements and understand the scope, and I’m ready to start immediately.

I’ll keep the implementation focused and consistent with the existing codebase, cover the relevant tests, and submit a clean PR that’s easy to review. I’ll also handle any review feedback through to completion.

If no one is currently working on it, I’m happy to take it.

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

[abdoolbasit374-web]

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

Hi dear maintainer , I am a smart contract developer please allow me to work on this issue , I can fix this

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

[drips-wave]

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

🧑‍💻 @abdoolbasit374-web: 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 🌊