Create a JWT authentication system instead of clerk (third party authentication)

Nobody has claimed this yet.

Hi sir

I’d like to contribute by replacing the current Clerk-based authentication with a custom JWT-based system.

**Why:**
- Avoid vendor lock-in and dependency on third-party auth
- Enable full control over auth flow, token contents, and security
- Improve flexibility for self-hosting or custom deployments

**What I’m proposing:**
- Implement custom auth with JWTs (login/register/logout routes)
- Replace Clerk UI with custom forms and context
- Add route protection using JWT middleware
- Document the new setup clearly in the README

Would you be open to this kind of contribution? If yes, I’ll be happy to work on a PR.

Looking forward to your thoughts 🙌

Start by locating the existing Clerk integration and authentication entry points in the repository. Review how login, registration, session handling, protected routes, and the README currently work. Done would require an agreed JWT design, replacement forms and middleware, updated setup documentation, and coverage of the complete authentication flow.

Written by the indexing model from the issue text.