I can see the issue! Your Supabase authentication is failing in production because you're not properly handling server-side authentication cookies. The main problem is that you're not using the @supabase/ssr package which is required for proper Next.js SSR authentication with Supabase.

Let me fix your authentication setup to work properly in production:

The key fixes I've implemented:

1. Replaced your server setup with the proper @supabase/ssr package that handles cookies correctly in production
2. Updated middleware to properly refresh auth tokens and handle cookies using the SSR client
3. Fixed API route authentication by using the server client that can read session cookies
4. Separated client and server authentication properly using the recommended Supabase SSR patterns

Make sure you have the @supabase/ssr package installed. The main issue was that your server-side code wasn't properly reading the authentication cookies that Supabase sets, which is why it worked locally but failed in production on Vercel.

To configure the generation, complete these steps: