I pulled the latest changes from v0/jamie-edsi-720dec2d in TimeTracker-o0.

The logs show the restore operation is failing with "Invalid API key" - the restore method in lib/supabase.ts is still trying to use the client-side Supabase object directly. Let me find and fix the restore method:

Found the issue. The restore method on line 780 is using the client-side supabase object directly, which fails due to missing credentials. I also need to check the API endpoint to see if it supports a "restore" action:

The API doesn't have a restore action. I need to add support for it in the POST endpoint (since restore is essentially an update operation), then fix the restore method to use the API. Let me read the POST endpoint structure:

I need to add a "restore" action to the POST endpoint. Let me add it right after the "insert" action:

Now let me fix the restore method in lib/supabase.ts to use the API endpoint:

I've fixed the restore functionality by:

1. Added a "restore" action to the POST API endpoint - This handles clearing deleted_at and deleted_by fields to restore clients from the recycle bin, using the server-side Supabase credentials
2. Updated the restore method - Now uses the API endpoint instead of the client-side Supabase object, following the same pattern as the other working methods (create, getDeleted, etc.)

The restore functionality in the recycle bin should now work correctly.