[CI] Add contract documentation generation to CI

[AbelOsaretin]

Description

Documentation should be generated and published as part of CI. This ensures docs are always up to date.

Recommendation

• Add cargo doc to CI
• Publish documentation to GitHub Pages
• Include documentation in release artifacts
• Add documentation link to README

Severity

Low — Documentation automation.

[HademiData]

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

Dear Maintainers,

I would like to work on this issue.

I have experience building CI/CD pipelines with GitHub Actions for Go and Rust projects, including automated builds, testing, linting, and deployment validation. For this task, I’ll create a deployment workflow that performs build verification before deployment, automates deployment using the existing Makefile commands, runs post-deployment verification checks, and includes a rollback strategy for failed deployments. I’ll ensure the workflow follows the repository’s existing conventions, is well documented, and provides a reliable, reproducible deployment process while minimizing manual intervention.

Thank you for your consideration. I look forward to contributing to the project.

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

[drips-wave]

Congratulations, @rikkk-j! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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

[DevAyomi]

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

Hi Maintainer, Please I would love to worrk on this issue

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

[Ryjen1]

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

I would like to work on this issue.I have experience with open-source contributions in TypeScript, Rust, Stellar ecosystem, frontend/backend, and I'm familiar with the project's architecture. I can start working on it immediately and aim to deliver a clean, well-tested solution with proper documentation.

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

[drips-wave]

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

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