Monorepo structure and tooling guide

[codebestia]

Write docs/monorepo.md explaining the workspace layout: pnpm-workspace.yaml (apps/* plus contracts), turbo.json's task graph (build with dependsOn: ^build, dev persistent/uncached, lint), which scripts live at the root vs. per app, and why contracts is a pnpm workspace member despite being a Cargo project.

Acceptance criteria:

• The directory tree is documented one level deep with a purpose line per entry
• Explains when to run a root script vs. pnpm --filter <app>
• Documents the Turbo task graph and what is cached
• Explains the shared root tooling (Prettier config, .prettierignore, root ESLint setup) and that Prettier is pinned to one exact version across the workspace

[TS-mfon]

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

GM

I'm a Blockchain developer

Please can I work on this issue

I'll cook hard for ya

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

[Deb-Auth]

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

I'm interested in working on this issue. I'll carefully follow the project's guidelines and submit a tested, maintainable solution.

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

[promisszn]

@promisszn 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/monorepo.md explaining the workspace layout (pnpm-workspace.yaml, apps/* plus contracts), documenting the directory tree one level deep with a purpose line per entry, when to run a root script vs. pnpm --filter, the Turbo task graph and what's cached, and the shared root tooling (Prettier config, .prettierignore, root ESLint setup, pinned Prettier version). I'll verify each claim against the actual config files before opening a PR.

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

[drips-wave]

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

🧑‍💻 @promisszn: 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 #595, merged into dev.

[drips-wave]

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

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