feat(supabase): add notifications and push_tokens tables with RLS

[youngkidwarrior]

Summary

Create database schema for the notifications system with notifications and push_tokens tables, RLS policies, and PgTAP tests.

Changes

• Add notification_type enum: transfer_sent, transfer_received, tag_confirmed, account_activity, system
• Add push_token_platform enum: expo, web
• Create notifications table for storing user notifications
• Create push_tokens table for storing push notification tokens (Expo and Web Push)
• Add RLS policies allowing users to manage only their own rows
• Add update_push_token_updated_at trigger for automatic timestamp updates
• Add indexes for efficient querying by user_id and read status
• Add unique constraints to prevent duplicate tokens
• Add 15 PgTAP tests for table operations and RLS enforcement

Tables

notifications

Column	Type	Description
id	bigint	Auto-increment primary key
user_id	uuid	Foreign key to auth.users (CASCADE delete)
type	notification_type	Type of notification
title	text	Notification title
body	text	Notification body
data	jsonb	Optional JSON data
read	boolean	Read status (default false)
created_at	timestamptz	Creation timestamp

push_tokens

Column	Type	Description
id	bigint	Auto-increment primary key
user_id	uuid	Foreign key to auth.users (CASCADE delete)
platform	push_token_platform	expo or web
token	text	Expo push token
endpoint	text	Web Push endpoint URL
p256dh	text	Web Push public key
auth	text	Web Push auth secret
created_at	timestamptz	Creation timestamp
updated_at	timestamptz	Auto-updated on changes

Testing

• All 674 tests pass including 15 new notifications tests
• Tests cover CRUD operations and RLS enforcement for both tables

This PR was generated with Warp.

[github-actions]

Vercel Unique URL: https://sendapp-4393ewxof-0xsend.vercel.app
Vercel Preview URL: sendapp-database-schema-notifications--worker-1-0xsend.vercel.app
Last Commit: 4693362