Add `versioning.rs` coverage for the newly-completed handlers

[fejilaup-cloud]

Labels: enhancement, api-server
Priority: Low
Estimated Time: 1 hour

Description:
versioning.rs exists for API versioning. Confirm the 13 now-to-be-wired handlers are correctly attached to a version (e.g. /v1/...) and that breaking changes to the RPC-mapping layer won't silently affect v1 clients.

Tasks:

• Audit route registration for explicit versioning
• Add a test that an unversioned or unknown-version request is rejected clearly
• Document the current API version and deprecation policy

[Olo2u]

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

Hi maintainer,

I’d like to pick up issue #859 (versioning.rs coverage for the newly-wired handlers).

My Approach:

• Audit versioning.rs and route registration to confirm all 13 newly-wired handlers are explicitly attached under a version prefix (e.g. /v1/...), rather than accidentally falling through to an unversioned or default route.
• Trace the RPC-mapping layer to check that future breaking changes there would be caught/isolated per-version rather than silently leaking into v1 client behavior.
• Add a test asserting that a request with no version or an unknown version is rejected with a clear, explicit error (not a silent fallback or generic 404).
• Add brief documentation covering:
• The current API version (v1).
• The deprecation policy for future version transitions (e.g. how/when v1 would be sunset if v2 is introduced).

Given the 1-hour estimate, I’ll keep this scoped to auditing + the one rejection test + doc note, and flag in the PR if I spot anything during the audit that looks like it needs a separate follow-up ticket.

Looking forward to contributing.

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

[Omoboi-dev]

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

Hello maintainer, i would like to work on this issue as i have read through the requirement and can deliver a good pr

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

[deborahamoni0-prog]

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

hi i would love to work on this issue

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@deborahamoni0-prog's PR #951 was approved and merged by @fejilaup-cloud.

🏆 @deborahamoni0-prog: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (853 total points). Track your full progress on GrantFox.

👏 Great work, @deborahamoni0-prog! Keep contributing to AtomicIP.

[drips-wave]

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

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