Build the fuzzing loop and crash reporter.

[codeZe-us]

The mutators are only useful inside a loop that runs millions of iterations, catches panics, and reports the exact reproducer. A crash with no reproducer is a crash you cannot fix.

Issues/what to fix

• Implement the main loop: generate a seed, apply a randomly chosen mutator, run parse inside std::panic::catch_unwind.
• On a caught panic, write a Finding record (input, mutator name, panic message) to a findings/ directory as JSON.
• Add a deterministic --seed flag so any crash can be replayed exactly.

Files location

src/main.rs, src/report.rs
Expected result
The loop runs continuously, survives parser panics, and writes replayable findings to disk.
Join the contributor Telegram group: https://t.me/+g6EPIsHod0RhZGZk

[drips-wave]

Congratulations, @Ajibola6921! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

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