Duplicate routing sources (App and AppRoutes) create regression risk

[Mkalbani]

Problem

Routes are defined in two places with different path sets, but only one is mounted, making updates error-prone.

Evidence

• src/App.tsx
• src/routes/AppRoutes.tsx
• src/main.tsx

Scope

Frontend-only. No API needed.

Contributor Task

• Consolidate routing into one source of truth.
• Remove or deprecate the unused route map.

Done When

• Only one route definition source is used in runtime.
• Navbar and page routes are derived from the same route set.

[DeveloperEmmy]

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

I’d like to work on this because consistent routing reduces regressions; I have experience structuring React apps with single source-of-truth navigation.

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

[wokedi]

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

Hello maintainer, can you assign me this please? ETA: 8hours

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

[drips-wave]

Congratulations, @DeveloperEmmy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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