🔄 [MEDIUM] Cargo Workspace Members vs Actual Contract Directories Alignment

[ayomideadeniran]

Description

The root Cargo.toml workspace members list includes some contracts that follow a different naming convention or may not exist as workspace-eligible packages.

Location

/Cargo.toml lines 22-43:

[workspace]
members = [
    "contracts/debugging-utils",
    "contracts/cross-contract-utils",
    ...
]

Current State

All 21 workspace member contracts have their Cargo.toml files. However, the root Cargo.toml workspace does NOT include many of the ~90 contracts in the contracts/ directory. There is no clear documentation on:

• Which contracts are part of the workspace vs standalone
• Criteria for adding a contract to the workspace
• Why some contracts are excluded

Impact

• Running cargo build from root only builds 21 out of ~90 contracts
• Contributors may add contracts to the wrong location
• No clear distinction between "workspace" and "non-workspace" contracts

Required Fix

1. Document the selection criteria for workspace members
2. Either add all contracts to the workspace or organize them into sub-workspaces
3. Consider adding a cargo check --workspace CI step to validate all members build

Reference

Identified during full codebase audit of soroban-playground.

[devpassionOX]

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

Hello, I reviewed the issue requirements and identified the likely areas that need modification. I'd appreciate the opportunity to contribute and submit a well-tested solution.

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

[ShantelPeters]

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

Please can i be assigned to this issue , i am ready to work

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

[drips-wave]

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

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