npm - @realtimex/email-automator - Versions diffs - 2.26.0 → 2.28.0 - Mend

@realtimex/email-automator 2.26.0 → 2.28.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (16) hide show

package/dist/index.html CHANGED Viewed

@@ -5,7 +5,7 @@
     <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
     <title>Email Automator</title>
-    <script type="module" crossorigin src="/assets/index-BiE9QzV0.js"></script>
+    <script type="module" crossorigin src="/assets/index-DpVG-8N2.js"></script>
     <link rel="stylesheet" crossorigin href="/assets/index-fVuZ4_5V.css">
   </head>
   <body>

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@realtimex/email-automator",
-  "version": "2.26.0",
+  "version": "2.28.0",
   "type": "module",
   "main": "dist/api/server.js",
   "bin": {

package/supabase/migrations/20260117000003_add_action_constraint.sql ADDED Viewed

@@ -0,0 +1,4 @@
+-- Update rules action check constraint to support new actions
+ALTER TABLE rules DROP CONSTRAINT IF EXISTS rules_action_check;
+ALTER TABLE rules ADD CONSTRAINT rules_action_check
+    CHECK (action IN ('delete', 'archive', 'draft', 'star', 'read', 'label', 'forward'));

package/supabase/migrations/20260131170000_add_rule_categories.sql ADDED Viewed

@@ -0,0 +1,65 @@
+-- Migration: Add rule categories
+-- Adds category column and backfills existing rules
+-- Step 1: Add category column to rules table if it doesn't exist
+ALTER TABLE public.rules
+ADD COLUMN IF NOT EXISTS category VARCHAR(50);
+-- Step 2: Update existing user rules to get categories from their templates
+UPDATE public.rules r
+SET category = rt.category
+FROM public.rule_templates rt
+WHERE r.rule_template_id = rt.rule_id
+  AND r.is_system_managed = true
+  AND (r.category IS NULL OR r.category != rt.category);
+-- Step 3: Create backfill function to install rules for existing users
+CREATE OR REPLACE FUNCTION public.install_all_rules_for_user(target_user_id UUID)
+RETURNS void AS $$
+DECLARE
+  existing_rules_count INTEGER;
+BEGIN
+  -- Check if user already has rules installed
+  SELECT COUNT(*) INTO existing_rules_count
+  FROM public.rules
+  WHERE user_id = target_user_id AND is_system_managed = true;
+  IF existing_rules_count > 0 THEN
+    RAISE NOTICE 'User % already has % system-managed rules installed', target_user_id, existing_rules_count;
+    RETURN;
+  END IF;
+  -- Copy ALL rules from templates with category
+  INSERT INTO public.rules (
+    user_id,
+    name,
+    intent,
+    condition,
+    action,
+    actions,
+    is_enabled,
+    category,
+    rule_template_id,
+    is_system_managed,
+    created_at
+  )
+  SELECT
+    target_user_id,
+    rt.name,
+    rt.intent,
+    rt.condition,
+    rt.actions[1],
+    rt.actions,
+    rt.is_enabled_by_default,
+    rt.category,
+    rt.rule_id,
+    true,
+    NOW()
+  FROM public.rule_templates rt
+  ORDER BY rt.category, rt.sort_order;
+  RAISE NOTICE '✓ Installed % rules for user %', (SELECT COUNT(*) FROM rule_templates), target_user_id;
+END;
+$$ LANGUAGE plpgsql SECURITY DEFINER;
+COMMENT ON FUNCTION public.install_all_rules_for_user(UUID) IS 'Backfill function to install all rules from templates for an existing user';

package/supabase/migrations/20260206000010_fix_trigger_naming_conflict.sql CHANGED Viewed

@@ -17,7 +17,7 @@ CREATE OR REPLACE FUNCTION public.handle_new_auth_user()
 RETURNS TRIGGER
 LANGUAGE plpgsql
 SECURITY DEFINER
-SET search_path = public
+SET search_path TO 'pg_catalog', 'public'
 AS $$
 DECLARE
   profile_count INT;
@@ -46,10 +46,11 @@ CREATE OR REPLACE FUNCTION public.handle_new_profile()
 RETURNS TRIGGER
 LANGUAGE plpgsql
 SECURITY DEFINER
-SET search_path = public
+SET search_path TO 'pg_catalog', 'public'
 AS $$
 DECLARE
   v_encryption_key TEXT;
+  v_new_encryption_key TEXT;
   v_rules_created INTEGER := 0;
 BEGIN
   -- Wrap in exception handler to prevent profile creation failure
@@ -60,7 +61,17 @@ BEGIN
     WHERE encryption_key IS NOT NULL
     LIMIT 1;
-    -- 1. Create user_settings
+    -- Generate new encryption key if none exists (first user case)
+    IF v_encryption_key IS NULL THEN
+      -- Use built-in gen_random_uuid() (no extension required) - convert to 64-char hex
+      v_new_encryption_key := md5(random()::text || clock_timestamp()::text) || md5(random()::text || clock_timestamp()::text);
+      RAISE NOTICE '[handle_new_profile] Generated new encryption key for first user %', NEW.id;
+    ELSE
+      v_new_encryption_key := v_encryption_key;
+      RAISE NOTICE '[handle_new_profile] Using existing encryption key for user %', NEW.id;
+    END IF;
+    -- 1. Create user_settings with encryption key
     INSERT INTO public.user_settings (
       user_id,
       llm_provider,
@@ -72,7 +83,7 @@ BEGIN
       NEW.id,
       'realtimexai',
       'gpt-4o-mini',
-      v_encryption_key,
+      v_new_encryption_key,
       NOW(),
       NOW()
     )
@@ -154,6 +165,40 @@ GRANT EXECUTE ON FUNCTION public.handle_new_auth_user() TO service_role;
 GRANT EXECUTE ON FUNCTION public.handle_new_profile() TO authenticated;
 GRANT EXECUTE ON FUNCTION public.handle_new_profile() TO service_role;
+-- ============================================================================
+-- FIX RLS POLICIES TO ALLOW TRIGGER INSERTS
+-- ============================================================================
+-- Drop the overly restrictive "FOR ALL" policy
+DROP POLICY IF EXISTS "Users can only access their own settings" ON user_settings;
+-- Create granular policies that allow trigger inserts (when auth.uid() IS NULL)
+CREATE POLICY "Users can view their own settings" ON user_settings
+    FOR SELECT USING (auth.uid() = user_id);
+CREATE POLICY "Users can update their own settings" ON user_settings
+    FOR UPDATE USING (auth.uid() = user_id);
+CREATE POLICY "Users can delete their own settings" ON user_settings
+    FOR DELETE USING (auth.uid() = user_id);
+CREATE POLICY "Users and triggers can insert settings" ON user_settings
+    FOR INSERT WITH CHECK (auth.uid() = user_id OR auth.uid() IS NULL);
+-- Fix RLS for rules table (same issue - triggers need to insert)
+DROP POLICY IF EXISTS "Users can only access their own rules" ON rules;
+CREATE POLICY "Users can view their own rules" ON rules
+    FOR SELECT USING (auth.uid() = user_id);
+CREATE POLICY "Users can update their own rules" ON rules
+    FOR UPDATE USING (auth.uid() = user_id);
+CREATE POLICY "Users can delete their own rules" ON rules
+    FOR DELETE USING (auth.uid() = user_id);
+CREATE POLICY "Users and triggers can insert rules" ON rules
+    FOR INSERT WITH CHECK (auth.uid() = user_id OR auth.uid() IS NULL);
 -- ============================================================================
 -- COMMENTS
 -- ============================================================================

package/supabase/migrations/20260206000016_update_init_function_negative_conditions.sql CHANGED Viewed

@@ -1,104 +1,121 @@
--- Migration: Update handle_new_user() to copy negative_condition from templates
+-- Migration: Update handle_new_profile() to copy negative_condition from templates
 -- Purpose: Ensure new users get negative conditions when rules are initialized
 --
 -- This completes the zero-config UX by ensuring negative_condition flows from
 -- rule_templates → user rules during signup
 -- Update the function to include negative_condition
-CREATE OR REPLACE FUNCTION public.handle_new_user()
-RETURNS TRIGGER AS $$
+CREATE OR REPLACE FUNCTION public.handle_new_profile()
+RETURNS TRIGGER
+LANGUAGE plpgsql
+SECURITY DEFINER
+SET search_path TO 'pg_catalog', 'public'
+AS $$
 DECLARE
-  pack_install_id UUID;
-  user_exists BOOLEAN;
+  v_encryption_key TEXT;
+  v_new_encryption_key TEXT;
+  v_rules_created INTEGER := 0;
 BEGIN
-  -- Check if user exists in auth.users to avoid foreign key violation
-  SELECT EXISTS (
-    SELECT 1 FROM auth.users WHERE id = NEW.id
-  ) INTO user_exists;
+  -- Wrap in exception handler to prevent profile creation failure
+  BEGIN
+    -- Get shared encryption key (sandbox mode)
+    SELECT encryption_key INTO v_encryption_key
+    FROM public.user_settings
+    WHERE encryption_key IS NOT NULL
+    LIMIT 1;
-  IF NOT user_exists THEN
-    RAISE NOTICE 'User % does not exist in auth.users yet, skipping initialization', NEW.id;
-    RETURN NEW;
-  END IF;
+    -- Generate new encryption key if none exists (first user case)
+    IF v_encryption_key IS NULL THEN
+      -- Use built-in functions (no extension required) - generates 64-char hex string
+      v_new_encryption_key := md5(random()::text || clock_timestamp()::text) || md5(random()::text || clock_timestamp()::text);
+      RAISE NOTICE '[handle_new_profile] Generated new encryption key for first user %', NEW.id;
+    ELSE
+      v_new_encryption_key := v_encryption_key;
+      RAISE NOTICE '[handle_new_profile] Using existing encryption key for user %', NEW.id;
+    END IF;
-  -- 1. Create user_settings record with defaults (with conflict handling)
-  INSERT INTO public.user_settings (
-    user_id,
-    llm_provider,
-    llm_model,
-    user_role,
-    onboarding_completed,
-    created_at,
-    updated_at
-  ) VALUES (
-    NEW.id,
-    'realtimexai',
-    'gpt-4o-mini',
-    NULL,
-    FALSE,
-    NOW(),
-    NOW()
-  )
-  ON CONFLICT (user_id) DO NOTHING;
-  -- 2. Install ALL rules from templates
-  -- First, check if rule_templates table exists (for backwards compatibility)
-  IF EXISTS (SELECT FROM information_schema.tables WHERE table_name = 'rule_templates') THEN
-    -- Copy ALL rules from templates (some enabled by default, others disabled)
-    -- Now includes negative_condition, min_confidence, description, instructions, and priority
-    INSERT INTO public.rules (
+    -- 1. Create user_settings with encryption key
+    INSERT INTO public.user_settings (
       user_id,
-      name,
-      description,
-      intent,
-      priority,
-      condition,
-      negative_condition,
-      min_confidence,
-      action,
-      actions,
-      instructions,
-      is_enabled,
-      pack,
-      rule_template_id,
-      is_system_managed,
-      created_at
-    )
-    SELECT
+      llm_provider,
+      llm_model,
+      encryption_key,
+      created_at,
+      updated_at
+    ) VALUES (
       NEW.id,
-      rt.name,
-      rt.description,
-      rt.intent,
-      rt.priority,
-      rt.condition,
-      rt.negative_condition,  -- ✅ NEW: Copy negative conditions
-      0.7,                     -- Default min_confidence (can be overridden by template if column added)
-      rt.actions[1],           -- First action as primary (for backwards compat)
-      rt.actions,              -- All actions array
-      rt.instructions,         -- Draft generation instructions
-      rt.is_enabled_by_default, -- Some enabled, others disabled
-      rt.pack_id,              -- Keep for backwards compat
-      rt.rule_id,
-      true,                    -- is_system_managed
+      'realtimexai',
+      'gpt-4o-mini',
+      v_new_encryption_key,
+      NOW(),
       NOW()
-    FROM public.rule_templates rt
-    ORDER BY rt.pack_id, rt.sort_order;
+    )
+    ON CONFLICT (user_id) DO NOTHING;
+    -- 2. Install rules from templates (including negative_condition)
+    IF EXISTS (SELECT FROM information_schema.tables WHERE table_name = 'rule_templates') THEN
+      INSERT INTO public.rules (
+        user_id,
+        name,
+        description,
+        intent,
+        priority,
+        condition,
+        negative_condition,
+        min_confidence,
+        action,
+        actions,
+        instructions,
+        is_enabled,
+        category,
+        rule_template_id,
+        is_system_managed,
+        created_at
+      )
+      SELECT
+        NEW.id,
+        rt.name,
+        rt.description,
+        rt.intent,
+        rt.priority,
+        rt.condition,
+        rt.negative_condition,
+        0.7,
+        rt.actions[1],
+        rt.actions,
+        rt.instructions,
+        rt.is_enabled_by_default,
+        rt.category,
+        rt.rule_id,
+        true,
+        NOW()
+      FROM public.rule_templates rt
+      ORDER BY rt.category, rt.sort_order
+      ON CONFLICT (user_id, rule_template_id) DO NOTHING;
+      GET DIAGNOSTICS v_rules_created = ROW_COUNT;
+      RAISE NOTICE '✓ User % initialized: settings created, % rules installed', NEW.id, v_rules_created;
+    ELSE
+      RAISE WARNING '⚠ rule_templates table not found for user %', NEW.id;
+    END IF;
-  END IF;
+  EXCEPTION
+    WHEN OTHERS THEN
+      RAISE WARNING '✗ handle_new_profile failed for user %: % (SQLSTATE: %)', NEW.id, SQLERRM, SQLSTATE;
+  END;
   RETURN NEW;
 END;
-$$ LANGUAGE plpgsql SECURITY DEFINER;
+$$;
 -- Add comment
-COMMENT ON FUNCTION public.handle_new_user() IS 'Automatically creates user_settings and installs rules from templates (including negative_condition) when a new user signs up';
+COMMENT ON FUNCTION public.handle_new_profile() IS 'Step 2: Initializes user_settings with encryption key and installs rules from templates (including negative_condition)';
 -- Log success
 DO $$
 BEGIN
-  RAISE NOTICE '✓ Updated handle_new_user() function to copy negative_condition from templates';
+  RAISE NOTICE '✓ Updated handle_new_profile() function to copy negative_condition from templates';
   RAISE NOTICE '  - New users will automatically get smart exclusion logic';
-  RAISE NOTICE '  - Also copies: description, instructions, priority fields';
+  RAISE NOTICE '  - Also copies: description, instructions, priority, encryption_key fields';
   RAISE NOTICE '  - Zero-Config UX: Complete!';
 END $$;

package/supabase/migrations/20260117000003_seed_default_rules.sql DELETED Viewed

@@ -1,77 +0,0 @@
--- Update rules action check constraint to support new actions
-ALTER TABLE rules DROP CONSTRAINT IF EXISTS rules_action_check;
-ALTER TABLE rules ADD CONSTRAINT rules_action_check
-    CHECK (action IN ('delete', 'archive', 'draft', 'star', 'read'));
--- Seed default rules for existing users
-DO $$
-DECLARE
-    user_rec RECORD;
-BEGIN
-    FOR user_rec IN SELECT id FROM auth.users LOOP
-        -- Archive Newsletters
-        IF NOT EXISTS (SELECT 1 FROM rules WHERE user_id = user_rec.id AND name = 'Archive Newsletters') THEN
-            INSERT INTO rules (user_id, name, condition, action, is_enabled)
-            VALUES (user_rec.id, 'Archive Newsletters', '{"category": "newsletter"}', 'archive', true);
-        END IF;
-        -- Archive Receipts
-        IF NOT EXISTS (SELECT 1 FROM rules WHERE user_id = user_rec.id AND name = 'Archive Receipts') THEN
-            INSERT INTO rules (user_id, name, condition, action, is_enabled)
-            VALUES (user_rec.id, 'Archive Receipts', '{"category": "transactional"}', 'archive', true);
-        END IF;
-        -- Trash Promotions (Disabled by default)
-        IF NOT EXISTS (SELECT 1 FROM rules WHERE user_id = user_rec.id AND name = 'Trash Promotions') THEN
-            INSERT INTO rules (user_id, name, condition, action, is_enabled)
-            VALUES (user_rec.id, 'Trash Promotions', '{"category": "promotional"}', 'delete', false);
-        END IF;
-        -- Flag Important
-        IF NOT EXISTS (SELECT 1 FROM rules WHERE user_id = user_rec.id AND name = 'Flag Important') THEN
-            INSERT INTO rules (user_id, name, condition, action, is_enabled)
-            VALUES (user_rec.id, 'Flag Important', '{"priority": "High"}', 'star', true);
-        END IF;
-        -- Auto-Trash Old Newsletters (30 days)
-        IF NOT EXISTS (SELECT 1 FROM rules WHERE user_id = user_rec.id AND name = 'Auto-Trash Old Newsletters') THEN
-            INSERT INTO rules (user_id, name, condition, action, is_enabled)
-            VALUES (user_rec.id, 'Auto-Trash Old Newsletters', '{"category": "newsletter", "older_than_days": 30}', 'delete', true);
-        END IF;
-    END LOOP;
-END $$;
--- Update trigger for new users to include default rules
-CREATE OR REPLACE FUNCTION public.handle_new_user()
-RETURNS TRIGGER
-LANGUAGE plpgsql
-SECURITY DEFINER SET search_path = ''
-AS $$
-DECLARE
-  profile_count int;
-BEGIN
-  SELECT count(id) INTO profile_count
-  FROM public.profiles;
-  -- Create Profile
-  INSERT INTO public.profiles (id, first_name, last_name, email, is_admin)
-  VALUES (
-    new.id,
-    new.raw_user_meta_data ->> 'first_name',
-    new.raw_user_meta_data ->> 'last_name',
-    new.email,
-    CASE WHEN profile_count > 0 THEN false ELSE true END
-  );
-  -- Insert Default Rules
-  INSERT INTO public.rules (user_id, name, condition, action, is_enabled)
-  VALUES
-    (new.id, 'Archive Newsletters', '{"category": "newsletter"}', 'archive', true),
-    (new.id, 'Archive Receipts', '{"category": "transactional"}', 'archive', true),
-    (new.id, 'Trash Promotions', '{"category": "promotional"}', 'delete', false),
-    (new.id, 'Flag Important', '{"priority": "High"}', 'star', true),
-    (new.id, 'Auto-Trash Old Newsletters', '{"category": "newsletter", "older_than_days": 30}', 'delete', true);
-  RETURN new;
-END;
-$$;

package/supabase/migrations/20260120100000_fix_auth_triggers.sql DELETED Viewed

@@ -1,44 +0,0 @@
--- Fix Auth triggers by setting robust search_path
--- This resolves "Database error creating new user" (unexpected_failure) during setup
-CREATE OR REPLACE FUNCTION public.handle_new_user()
-RETURNS TRIGGER
-LANGUAGE plpgsql
-SECURITY DEFINER SET search_path = public
-AS $$
-DECLARE
-  profile_count int;
-BEGIN
-  SELECT count(id) INTO profile_count
-  FROM public.profiles;
-  INSERT INTO public.profiles (id, first_name, last_name, email, is_admin)
-  VALUES (
-    new.id,
-    new.raw_user_meta_data ->> 'first_name',
-    new.raw_user_meta_data ->> 'last_name',
-    new.email,
-    -- If it's the first user, make them admin. Otherwise, standard user.
-    CASE WHEN profile_count > 0 THEN false ELSE true END
-  );
-  RETURN new;
-END;
-$$;
-CREATE OR REPLACE FUNCTION public.handle_update_user()
-RETURNS TRIGGER
-LANGUAGE plpgsql
-SECURITY DEFINER SET search_path = public
-AS $$
-BEGIN
-  UPDATE public.profiles
-  SET
-    first_name = new.raw_user_meta_data ->> 'first_name',
-    last_name = new.raw_user_meta_data ->> 'last_name',
-    email = new.email,
-    updated_at = now()
-  WHERE id = new.id;
-  RETURN new;
-END;
-$$;

package/supabase/migrations/20260131110000_auto_init_user_data.sql DELETED Viewed

@@ -1,90 +0,0 @@
--- Migration: Auto-initialize user data on signup
--- Creates user_settings record and installs Universal Pack automatically
--- Function to initialize user settings and install Universal Pack
-CREATE OR REPLACE FUNCTION public.handle_new_user()
-RETURNS TRIGGER AS $$
-DECLARE
-  pack_install_id UUID;
-  user_exists BOOLEAN;
-BEGIN
-  -- Check if user exists in auth.users to avoid foreign key violation
-  SELECT EXISTS (
-    SELECT 1 FROM auth.users WHERE id = NEW.id
-  ) INTO user_exists;
-  IF NOT user_exists THEN
-    RAISE NOTICE 'User % does not exist in auth.users yet, skipping initialization', NEW.id;
-    RETURN NEW;
-  END IF;
-  -- 1. Create user_settings record with defaults (with conflict handling)
-  INSERT INTO public.user_settings (
-    user_id,
-    llm_provider,
-    llm_model,
-    user_role,
-    onboarding_completed,
-    created_at,
-    updated_at
-  ) VALUES (
-    NEW.id,
-    'realtimexai',
-    'gpt-4o-mini',
-    NULL,
-    FALSE,
-    NOW(),
-    NOW()
-  )
-  ON CONFLICT (user_id) DO NOTHING;
-  -- 2. Install ALL rules from templates
-  -- First, check if rule_templates table exists (for backwards compatibility)
-  IF EXISTS (SELECT FROM information_schema.tables WHERE table_name = 'rule_templates') THEN
-    -- Copy ALL rules from templates (some enabled by default, others disabled)
-    INSERT INTO public.rules (
-      user_id,
-      name,
-      intent,
-      condition,
-      action,
-      actions,
-      is_enabled,
-      pack,
-      rule_template_id,
-      is_system_managed,
-      created_at
-    )
-    SELECT
-      NEW.id,
-      rt.name,
-      rt.intent,
-      rt.condition,
-      rt.actions[1], -- First action as primary (for backwards compat)
-      rt.actions,    -- All actions array
-      rt.is_enabled_by_default, -- Some enabled, others disabled
-      rt.pack_id, -- Keep for backwards compat
-      rt.rule_id,
-      true, -- is_system_managed
-      NOW()
-    FROM public.rule_templates rt
-    ORDER BY rt.pack_id, rt.sort_order;
-  END IF;
-  RETURN NEW;
-END;
-$$ LANGUAGE plpgsql SECURITY DEFINER;
--- Trigger to call the function when a new profile is created
-DROP TRIGGER IF EXISTS on_profile_created ON public.profiles;
-CREATE TRIGGER on_profile_created
-  AFTER INSERT ON public.profiles
-  FOR EACH ROW
-  EXECUTE FUNCTION public.handle_new_user();
--- Grant necessary permissions
-GRANT EXECUTE ON FUNCTION public.handle_new_user() TO authenticated;
--- Comment
-COMMENT ON FUNCTION public.handle_new_user() IS 'Automatically creates user_settings and installs Universal Pack when a new user signs up';

package/supabase/migrations/20260131150000_fix_trigger_error_handling.sql DELETED Viewed

@@ -1,71 +0,0 @@
--- Migration: Add error handling to user initialization trigger
--- Prevents user creation from failing if trigger has issues
--- Recreate function with exception handling
-CREATE OR REPLACE FUNCTION public.handle_new_user()
-RETURNS TRIGGER AS $$
-BEGIN
-  -- Wrap everything in exception handler to prevent user creation failure
-  BEGIN
-    -- 1. Create user_settings record with defaults
-    INSERT INTO public.user_settings (
-      user_id,
-      llm_provider,
-      llm_model,
-      user_role,
-      onboarding_completed,
-      created_at,
-      updated_at
-    ) VALUES (
-      NEW.id,
-      'realtimexai',
-      'gpt-4o-mini',
-      NULL,
-      FALSE,
-      NOW(),
-      NOW()
-    )
-    ON CONFLICT (user_id) DO NOTHING;
-    -- 2. Install ALL rules from templates
-    IF EXISTS (SELECT FROM information_schema.tables WHERE table_name = 'rule_templates') THEN
-      INSERT INTO public.rules (
-        user_id,
-        name,
-        intent,
-        condition,
-        action,
-        actions,
-        is_enabled,
-        pack,
-        rule_template_id,
-        is_system_managed,
-        created_at
-      )
-      SELECT
-        NEW.id,
-        rt.name,
-        rt.intent,
-        rt.condition,
-        rt.actions[1],
-        rt.actions,
-        rt.is_enabled_by_default,
-        rt.pack_id,
-        rt.rule_id,
-        true,
-        NOW()
-      FROM public.rule_templates rt
-      ORDER BY rt.pack_id, rt.sort_order;
-    END IF;
-  EXCEPTION
-    WHEN OTHERS THEN
-      -- Log error but don't fail user creation
-      RAISE WARNING 'Failed to initialize user data for %: % (SQLSTATE: %)', NEW.id, SQLERRM, SQLSTATE;
-  END;
-  RETURN NEW;
-END;
-$$ LANGUAGE plpgsql SECURITY DEFINER;
-COMMENT ON FUNCTION public.handle_new_user() IS 'Automatically creates user_settings and installs rules when a new user signs up (with error handling to prevent user creation failure)';