CI/CD pipeline reference

[codebestia]

Write docs/ci-cd.md documenting all nine workflows in .github/workflows/: backend-ci, frontend-ci, contracts-ci, ai-agent-ci, security-ci, loadtest-nightly, pr, guard-main-branch, and close-linked-issues. For each: what triggers it (path filters, schedule), what it runs, and what a failure means.

Acceptance criteria:

• Every workflow documented with trigger, jobs, and the failure signal a contributor should act on
• Path filters are explained, so a contributor understands why touching apps/web/** does not run backend CI
• guard-main-branch is documented as the mechanism behind the dev-only branch rule
• contracts-ci's 100 KB WASM size gate and its PR size-report comment are documented
• loadtest-nightly's baseline-regression comparison is documented, including where scripts/loadtest/baseline.json comes from
• Notes the toolchain-pinning caveat: rust-toolchain.toml says channel = "stable" so a new Rust release can break contracts CI with no code change

[fatihuayodele2-bot]

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

Hey Maintainer, I’ve checked the issue and I get what’s needed. Can you assign it to me? I’ve got it.

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

[wolfyres]

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

Hi maintainer, I've got solid experience solving similar issues, kindly assign this to me.

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

[vickydve]

@vickydve 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'll write docs/ci-cd.md documenting all nine workflows in .github/workflows/ (backend-ci, frontend-ci, contracts-ci, ai-agent-ci, security-ci, loadtest-nightly, pr, guard-main-branch, close-linked-issues), covering each workflow's trigger, jobs, and the failure signal a contributor should act on. I'll explain the path filters (why touching apps/web/** doesn't run backend CI), document guard-main-branch as the dev-only branch rule mechanism, contracts-ci's 100 KB WASM size gate and PR size-report comment, loadtest-nightly's baseline-regression comparison and where scripts/loadtest/baseline.json comes from, and note the toolchain-pinning caveat around rust-toolchain.toml's channel = "stable". I'll verify each claim against the actual workflow files before opening a PR.

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

[drips-wave]

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

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

[github-actions]

Closed by #596, merged into dev.

[drips-wave]

This issue has been completed by @vickydve as part of the Stellar Wave Program's 8th Wave 🥳

😎 @vickydve: 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.