Add Decision Severity String Formatting and Stats

[codeZe-us]

Add a String() method on Decision and a Stats function that takes a slice of decisions and returns counts per decision type.

Contribution Guide

• PRs go to the dev branch, not main
• Application must explain your specific approach to this task ; generic applications will not be assigned
• PR description must clearly describe what you built and changed
• Link your PR to the correct issue number (e.g. Closes #12)

Implementation Guidelines
Key files: examples/go-exchange/contract-deposit-firewall/firewall/stats.go

• Decision.String() returns "auto-credit", "manual-review", or "quarantine".
• Stats(decisions []Decision) map[Decision]int returns count per type.
• Update main.go to print a summary line after all scenarios: "Results: X auto-credit, Y manual-review, Z quarantine".

Expectations
What done looks like: Summary line at the end of the runner output shows correct counts matching the scenario results.

Discord for questions: codeze_us

[adedamolamiposi]

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

Good day dev. Allow me to jump on this issue.

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

[Jidetireni]

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

HI! I'D LIKE TO TAKE ON ISSUE #223.

MY APPROACH: I'LL ADD A String() METHOD ON Decision RETURNING "auto-credit", "manual-review", OR "quarantine", AND A Stats(decisions []Decision) map[Decision]int FUNCTION IN firewall/stats.go THAT COUNTS EACH DECISION TYPE. I'LL THEN UPDATE main.go TO COLLECT ALL SCENARIO DECISIONS AND PRINT A FINAL SUMMARY LINE WITH THE CORRECT COUNTS.

THANKS FOR CONSIDERING!

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

[drips-wave]

Congratulations, @Jidetireni! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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