Fix Authentication API Routes to Resolve 404 Errors

[vikasverma101]

Description

Fixes #8995

Fixed the production Sign In and Sign Up API 404 issue in CommitPulse.

The frontend was calling:

• /api/auth/login
• /api/auth/signup

while the API route directory used an uppercase Auth, causing the routes to fail in the case-sensitive production environment.

This PR aligns the authentication API route paths with the lowercase /api/auth/... endpoints expected by the frontend and adds regression coverage for the affected routes.

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

Not applicable — this is an API routing/authentication bug fix with no visual or SVG changes.

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested the authentication changes locally.
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have updated README.md if I added a new theme or URL parameter.
• I have started the repo.
• I have made sure that i have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[vercel]

@vikasverma101 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[retenta-bot]

This pull request addresses a critical issue with the authentication API routes that were causing 404 errors in production. It aligns the route paths with the expected lowercase format, ensuring proper functionality. This change is important for maintaining a secure and reliable authentication process. Additionally, it adds regression coverage for the affected routes, which is a great practice. Please note that similar past decisions have focused on improving API error handling to prevent sensitive information leakage, which highlights the importance of robust API design. Thank you for your contribution, and I look forward to your updates!

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

Asset	PR Size	Base Size	Difference	Status
static/chunks/app/api/Auth/Nextauthgithub/route-[hash].js	-	0.28 KB	-0.28 KB (-100.00%)	🗑️ Deleted
static/chunks/app/api/Auth/login/route-[hash].js	-	0.28 KB	-0.28 KB (-100.00%)	🗑️ Deleted
static/chunks/app/api/Auth/signup/route-[hash].js	-	0.28 KB	-0.28 KB (-100.00%)	🗑️ Deleted
static/chunks/app/api/auth/Nextauthgithub/route-[hash].js	0.28 KB	-	+0.28 KB (++100%)	🆕 New
static/chunks/app/api/auth/login/route-[hash].js	0.28 KB	-	+0.28 KB (++100%)	🆕 New
static/chunks/app/api/auth/signup/route-[hash].js	0.28 KB	-	+0.28 KB (++100%)	🆕 New

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	4998.89 KB	4998.89 KB	0 B
Total CSS	354.18 KB	354.18 KB	0 B