Expose or retire wallet API routes with tests

[pragmaticAweds]

Context

wallet.controller.ts has a listWallets handler and wallet.services.ts creates a wallet repository, but wallet.routes.ts does not register any route. This leaves the wallet module in a half-implemented state: it is present in the codebase but not reachable through the API.

Scope

• Decide whether wallet listing should be a supported API endpoint or the unused module should be removed from routing docs
• If supported, register the wallet route under the appropriate v1 router
• Add authentication/admin requirements appropriate for listing wallets
• Add controller/route tests for success, auth failure, and database-not-ready behavior
• Ensure response shape matches shared API conventions
• Update README or API docs if a public route is added

Out of Scope

• Wallet creation or balance mutation endpoints
• Chain balance synchronization
• Large platform permission redesign

Acceptance Criteria

• Wallet module is no longer dormant or misleading
• Any exposed wallet route has access control and tests
• Tests cover expected failure responses
• bun run type-check passes
• bun run test passes
• bun run lint passes

Suggested Files or Packages

• src/components/v1/wallet/
• src/components/v1/routes.v1.ts
• src/__tests__/
• README.md

[Silver36-ship-it]

@Silver36-ship-it has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this professionally, please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Silver36-ship-it to this issue.

[habnark]

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

Hello can I work on this issue

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

[drips-wave]

Congratulations, @Silver36-ship-it! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Silver36-ship-it: 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 🌊