Consolidate /login and /(auth)/signin into one user journey

[Abidoyesimze]

Summary

The app currently exposes more than one sign-in surface with different copy and behavior.

• Pick a canonical route and redirect the other.
• Avoid duplicate SEO and split analytics.
• Align messaging (wallet vs email) with product intent.

Acceptance criteria

• Clear owner and scope agreed in the issue thread if ambiguous.
• Change is verifiable: tests, screenshots, or written QA steps in the PR.
• No new duplicate abstractions without a one-line note explaining why.

Suggested labels

ux, routing, auth, priority-medium

Notes

Filing: use these files as the issue body, or gh issue create with a trimmed file. This queue complements the feature backlog (001–050).

[chisomvictorcv-sketch]

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

Good day I am a full stack developer with over 6 years of experience and I have good practical knowledge on this kindly assign this to me.

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

[karanjadavi]

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

can i work on this issue

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

[dubemoyibe-star]

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

This looks like a useful cleanup, and I'd love to help with it.

I'll review both sign-in flows and work toward a single, consistent authentication experience. The goal is to choose one primary route, redirect the other, and make sure the messaging and behavior stay the same no matter how users arrive at the login page.

I'll also include clear testing or QA steps in the PR so the updated flow is easy to verify. If no one is currently working on this, I'd be happy to pick it up.

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

[grantfox-oss]

🦊 GrantFox — @karanjadavi has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #381)
2. Your PR will be reviewed by the Neurowealth maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @karanjadavi: 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!

@karanjadavi's PR #508 was approved and merged by @Abidoyesimze.

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

👏 Great work, @karanjadavi! Keep contributing to Neurowealth.