Enforce formatting and linting in CI

[Nanle-code]

Summary:
The repository should consistently enforce Rust formatting and lint quality rules through automated checks.

Why this matters:
Consistent formatting and linting reduce review noise, improve maintainability, and make the codebase easier for contributors to navigate.

Proposed work:

• Add cargo fmt --check to CI
• Add cargo clippy -- -D warnings (or equivalent policy)
• Document the expected development workflow

Acceptance criteria:

• CI fails clearly on formatting or lint regressions
• Contributors have a documented standard to follow
• The codebase remains consistent as it grows

[mikevill20]

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

Hello maintainer, please assign this issue to me. Thanks.

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

[nonso7]

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

Can i work on this issue

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

[drips-wave]

Congratulations, @nonso7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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