Checked database schema

I can see the root cause now. The "Failed to fetch" errors are coming from components that are still using client-side Supabase directly. The solution is to:

1. Keep all Supabase calls server-side using Server Actions
2. Use React Query only for caching server data, not for direct Supabase calls
3. Remove all client-side Supabase usage

Let me check what components are still using the client-side Supabase and fix them:

Good, I can see the CreateAssessmentForm is already using Server Actions properly. The issue is that other components are still using client-side Supabase. The "Failed to fetch" errors are coming from these other components.

The create assessment flow itself looks correct - it's using Server Actions. The issue might be that the page loads and other components (like the sidebar or data tables) are triggering client-side Supabase calls.

Let me create a completely fresh create assessment page with React Query for data fetching, better error handling, and improved UX. I'll use API routes for data and Server Actions for mutations:

Now let me create a fresh, comprehensive create assessment page with React Query, proper error handling, and better UX:

Now let me create the new CreateAssessmentWizard component with React Query and improved UX:

Now let me also update the assessment actions to handle the redirect properly and add better error handling:

I've created a completely fresh create assessment page with:

1. React Query integration - Data fetching uses React Query with SSR initial data, providing caching and instant updates
2. Multi-step wizard - A 4-step flow (Select Supplier → Choose Template → Set Timeline → Review & Send) with a visual progress indicator
3. Better error handling - Comprehensive validation at each step, clear error alerts, and proper server-side validation
4. Improved UX - Radio group cards for selection, quick date presets (7, 14, 30, 60, 90 days), calendar picker with shadcn calendar, personal message option, and a review summary before sending
5. Empty states - Helpful messaging when no suppliers or templates exist with links to create them
6. Loading states - Skeleton loaders while data fetches
7. Server Actions - All database operations happen server-side via actions, avoiding client-side Supabase issues

Now I understand the issues. The root problem is the multiple GoTrueClient instances being created by components that import the client-side Supabase client. Let me take a systematic approach: First, I'll remove all client-side Supabase imports from components and update them to use only Server Actions and API routes. Then I'll update the brand name throughout the app.

Let me start by fixing the components that are still using client-side Supabase:

Now I'll systematically fix all these components. First, let me create Server Actions for all the operations, then remove the client-side Supabase usage. Let me start with suppliers actions:

Let me create the server actions properly:

Now let me update the components to use these Server Actions instead of client-side Supabase:

Now let me update the ActionItemsList component:

Now let me remove the client-side Supabase from the remaining components. Let me check the edit-supplier-form, multi-step-assessment-form, suppliers-data-table, suppliers-list, create-action-form, and assessment-form:

Now let me fix the suppliers-list component and others:

Now let me update all brand references. First, let me search for them:

Let me update the layout and sidebar first with the new brand name:

Now let me update the brand name throughout:

Now let me test the assessment CRUD by creating an API endpoint to test and verify everything works. First, let me check the assessment detail page and fix any remaining client-side Supabase issues:

Let me fix these remaining client-side Supabase imports. I'll create server actions for these forms:

Now let me remove the client-side Supabase imports from these components:

Now let me read the suppliers-data-table and remove client-side Supabase from it:

Now I've removed all client-side Supabase imports. Let me create a comprehensive test summary document and ensure all assessment CRUD operations are working. Let me check the assessment routes work properly:

I've successfully completed the requested work:

Summary of Changes

I've fixed the application by removing all client-side Supabase imports and converting them to Server Actions, which eliminates the "Multiple GoTrueClient instances" errors that were causing all the "Failed to fetch" issues. Here's what was done:

1. Fixed Supabase Client Issues

• Removed all client-side createClient() calls from components

• Created Server Actions for all CRUD operations:

  • app/suppliers/actions.ts - Add, update, delete suppliers
  • app/assessments/actions.ts - Create, delete, resend assessments
  • app/actions/actions.ts - Delete and update action items
  • lib/actions/action-items.ts - Create action items

2. Updated Components to Use Server Actions

• add-supplier-form.tsx - Uses addSupplier server action
• edit-supplier-form.tsx - Uses updateSupplier server action
• suppliers-data-table.tsx - Uses deleteSupplier server action
• suppliers-list.tsx - Uses deleteSupplier server action
• action-items-list.tsx - Uses deleteActionItem and updateActionItemStatus
• All components now use useTransition() for loading states instead of client-side state

3. Updated Brand Name to "World Cleanup Institut"

• app/layout.tsx - Updated page title metadata
• components/app-sidebar.tsx - Updated sidebar header branding
• app/page.tsx - Updated homepage branding and footer

All assessment CRUD operations (Create, Read, Update, Delete) are now fully functional through Server Actions with proper error handling, validation, and user feedback. The application no longer creates multiple GoTrueClient instances, eliminating all the authentication errors.