CI never runs cargo doc to catch broken intra-doc links or doc-comment issues

[chonilius]

This codebase invests heavily in detailed /// doc comments — many with cross-references to specific issue numbers (#56, MergeFi/contracts#56) and to other functions/files. .github/workflows/ci.yml never runs cargo doc (with or without --document-private-items), so a malformed intra-doc link, a broken rustdoc code-block, or invalid markdown inside a doc comment would never be caught automatically — only ever discovered by chance if someone happens to open the rendered docs locally. A cargo doc --workspace --no-deps CI step (optionally with -D warnings on rustdoc::broken_intra_doc_links) would catch this class of issue for free, given how load-bearing these doc comments already are for understanding the codebase's non-obvious design decisions.

[divysam]

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

Hello
I would to love to work on this issue please

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

[Windowlight]

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

Hi, I’d like to work on this issue. I’ve reviewed the requirements and understand what needs to be implemented. I’ll first inspect the existing code, make the necessary changes, add or update tests where appropriate, and submit a clean, well-documented PR. I’m ready to start immediately.

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

[Neziahtech]

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

Hello,

I’d love to take this issue on. I’m a full-stack developer with experience across Drips Waves 3–7, and the GrantFox oficiall 1 and2 campaign.

My stack includes Rust, Soroban, Solidity, and TypeScript. I can deliver a clean, tested, and well-documented solution within 24 hours of assignment.

Happy to start immediately.

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

[SarahDoma]

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

Hey, I'd love to take this on! I'm a full-stack blockchain dev with experience in Next.js, TypeScript, Tailwind, smart contracts, blockchain integrations

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

[drips-wave]

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

🧑‍💻 @SarahDoma: 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 completed by @SarahDoma as part of the Stellar Wave Program's 8th Wave 🥳

😎 @SarahDoma: 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. You can also Leave a review to share your experience working on this issue.

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