Database And Backend Supabase

User says 'add a notes feature: each note has a title, body, and belongs to a user.' Project is linked to a Supabase project.

Generate a notes table with id (uuid pk), user_id (fk to auth.users), title (text not null), body (text), created_at (timestamptz default now()). Generate the SQL migration file, show it in chat, and apply via the documented Supabase migration path. Do not write directly to the live DB without surf…

Notes table was created in the prior turn. Without RLS, any logged-in user could read any other user's notes via the Supabase anon key.

Enable RLS on the notes table and add the documented policy: 'auth.uid() = user_id' for select/insert/update/delete. Verify by attempting cross-user read from a generated client and show the rejection in chat.

Schema changes in Supabase; client code uses typed supabase.from('notes').

Regenerate the typed types (supabase gen types typescript) after every schema change and include the regenerated file in the same commit. Build will catch drift; client gets type-safe access to new columns.