Turbo pipeline documents build order for release

[Mimah97]

Context

Tooling / Release

Document turbo build order for sdk→web/api release.

Task

Turbo pipeline documents build order for release

Implementation checklist

• Update README or docs
• Example turbo run build
• Note contract package separate

Acceptance criteria

• Release steps clear for maintainers

Notes

• Keep the PR focused on this issue only
• Follow existing patterns (modules, linting, security)
• Ask in the thread if scope is unclear

Formerly titled as a generic “reliability pass”; rewritten with concrete scope.

[Vvictor-commits]

@Vvictor-commits has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please assign this issue to me

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

[Shalom-margort]

@Shalom-margort has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hello dear i would love to work on this issue

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

[drips-wave]

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

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