chore: add a make doctor target that validates local toolchain versions

[misrasamuelisiguzor-oss]

Description

The Makefile and justfile both provide dev targets, and rust-toolchain.toml pins the Rust version (#32), but there's no single command a new contributor can run to check whether their local Rust, Node, and Soroban CLI versions all match what the project expects before they start debugging confusing build failures.

This is repository-level tooling, configuration, or process rather than application code, but that doesn't make it lower stakes: onboarding friction, unclear ownership, and process gaps are consistently what determines whether a project with this much surface area (two contract trees, two backend trees, two frontend apps, a static dashboard, and an active external contributor program) stays maintainable as it grows or slowly accumulates inconsistency that nobody has the full context to untangle.

Given that this repository is actively recruiting outside contributors through the Stellar Wave bounty program (this issue included), the quality of its repository-level scaffolding, from CONTRIBUTING.md to CODEOWNERS to its issue and PR templates, has a direct and measurable effect on how many contributors are able to land a change successfully on their first attempt versus giving up in the setup phase.

Requirements and context

• Add a make doctor (and just doctor) target checking rustc --version, node --version, and soroban --version against expected ranges

Suggested execution

1. Fork the repo and create a branch

   git checkout -b chore/makefile-doctor-target
   

2. Implement changes

• Add the target to Makefile and mirror it in justfile (chore: add Makefile targets for common dev tasks #29)

3. Test and commit

• Run make doctor locally and confirm it reports mismatches clearly

Example commit message

chore: add doctor target for toolchain version validation

Guidelines

• Assignment required before starting
• PR description must include: Closes #[issue_id]
• Keep PR description professional and detailed

[stevengrams]

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

I would like to apply for this issue, i am confident i can solve it

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

[john2ydep2-gt]

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

please i will love to work on this

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

[drips-wave]

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

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