Clerk and NextAuth.js Conflicting Auth Headers

1. Clerk and NextAuth middleware both running and interfering with each other
2. Conflicting session cookie names causing overwrite behavior
3. Both libraries attempting to validate auth on the same routes
4. Incorrect middleware execution order in next.config.js or middleware.ts
5. Session context providers not properly isolated in layout hierarchy

Choose one auth solution: For new projects, prefer Clerk for modern features or NextAuth for OAuth flexibility. Don't mix both.

If must coexist: Use separate cookies and route prefixes. Configure NextAuth on /api/auth/* and Clerk on /clerk/* paths.

Middleware isolation: In middleware.ts, route Clerk-protected paths separately from NextAuth routes.

Provider wrapping: Wrap Clerk provider at root level, NextAuth session provider inside it, avoiding double-wrapping.