spine-framework 0.3.124 → 0.3.126

package/.framework/migrations/025_retype_threads_messages.sql

@@ -1,240 +0,0 @@
--- Migration 025: Retype existing support/community threads and messages
--- After creating support_thread, support_reply, community_thread, community_reply
--- types, this migration retypes existing rows that were created with the generic
--- thread/message types and re-stamps design_schema/validation_schema.
---
--- It is self-contained: it creates/updates the required types first so that the
--- migration does not depend on app seed files having already been run.
---
--- It preserves the existing design_schema.scope (inherited from the parent record)
--- so account-scoped support records stay account-scoped and platform-scoped
--- community records stay platform-scoped.
-
--- Helper function to pick the first active type by slug
-CREATE OR REPLACE FUNCTION public._tmp_first_type_id(p_slug text)
-RETURNS uuid AS $$
-  SELECT id FROM public.types WHERE slug = p_slug AND is_active = true ORDER BY created_at LIMIT 1;
-$$ LANGUAGE sql STABLE;
-
--- 0. Ensure the required types exist and have the correct scope/kind.
-
--- 0a. Fix generic thread and message types: scope should be account.
--- (They may be under any app_id; we update all active ones.)
-UPDATE public.types
-SET design_schema = jsonb_set(
-  COALESCE(design_schema, '{}'::jsonb),
-  '{scope}',
-  '"account"'
-)
-WHERE slug IN ('thread', 'message')
-  AND is_active = true
-  AND COALESCE(design_schema->>'scope', 'platform') != 'account';
-
--- 0b. Deactivate any stale community_reply item type so it does not shadow the
--- message type. It is safe to deactivate because no items should reference it.
-UPDATE public.types
-SET is_active = false
-WHERE slug = 'community_reply'
-  AND kind = 'item'
-  AND is_active = true;
-
--- 0c. Determine the owner app_id for the new domain types.
--- Prefer the app that owns support_ticket/community_post; fall back to portal,
--- then any active app.
-DO $$
-DECLARE
-  v_owner_app_id uuid;
-BEGIN
-  SELECT app_id INTO v_owner_app_id
-  FROM public.types
-  WHERE slug IN ('support_ticket', 'community_post')
-    AND is_active = true
-  LIMIT 1;
-
-  IF v_owner_app_id IS NULL THEN
-    SELECT id INTO v_owner_app_id FROM public.apps WHERE slug = 'portal' AND is_active = true LIMIT 1;
-  END IF;
-
-  IF v_owner_app_id IS NULL THEN
-    SELECT id INTO v_owner_app_id FROM public.apps WHERE is_active = true LIMIT 1;
-  END IF;
-
-  -- Create the four domain types if they don't already exist with the correct kind.
-
-  -- support_thread
-  IF NOT EXISTS (SELECT 1 FROM public.types WHERE slug = 'support_thread' AND kind = 'thread' AND is_active = true) THEN
-    INSERT INTO public.types (id, app_id, kind, slug, name, description, icon, color, ownership, is_active, validation_schema, design_schema)
-    VALUES (
-      gen_random_uuid(),
-      v_owner_app_id,
-      'thread',
-      'support_thread',
-      'Support Thread',
-      'Customer-visible conversation thread attached to a support ticket',
-      'message-square',
-      '#EF4444',
-      'tenant',
-      true,
-      '{}'::jsonb,
-      jsonb_build_object(
-        'scope', 'account',
-        'record_permissions', jsonb_build_object(
-          'system_admin', ARRAY['create', 'read', 'update', 'delete'],
-          'support_admin', ARRAY['create', 'read', 'update'],
-          'support', ARRAY['create', 'read', 'update'],
-          'member_admin', ARRAY['create', 'read', 'update'],
-          'member', ARRAY['create', 'read', 'update']
-        )
-      )
-    );
-  END IF;
-
-  -- support_reply
-  IF NOT EXISTS (SELECT 1 FROM public.types WHERE slug = 'support_reply' AND kind = 'message' AND is_active = true) THEN
-    INSERT INTO public.types (id, app_id, kind, slug, name, description, icon, color, ownership, is_active, validation_schema, design_schema)
-    VALUES (
-      gen_random_uuid(),
-      v_owner_app_id,
-      'message',
-      'support_reply',
-      'Support Reply',
-      'Customer or agent message within a support thread',
-      'message-circle',
-      '#EF4444',
-      'tenant',
-      true,
-      '{}'::jsonb,
-      jsonb_build_object(
-        'scope', 'account',
-        'record_permissions', jsonb_build_object(
-          'system_admin', ARRAY['create', 'read', 'update', 'delete'],
-          'support_admin', ARRAY['create', 'read', 'update'],
-          'support', ARRAY['create', 'read', 'update'],
-          'member_admin', ARRAY['create', 'read', 'update'],
-          'member', ARRAY['create', 'read', 'update']
-        )
-      )
-    );
-  END IF;
-
-  -- community_thread
-  IF NOT EXISTS (SELECT 1 FROM public.types WHERE slug = 'community_thread' AND kind = 'thread' AND is_active = true) THEN
-    INSERT INTO public.types (id, app_id, kind, slug, name, description, icon, color, ownership, is_active, validation_schema, design_schema)
-    VALUES (
-      gen_random_uuid(),
-      v_owner_app_id,
-      'thread',
-      'community_thread',
-      'Community Thread',
-      'Public discussion thread attached to a community post',
-      'users',
-      '#6366F1',
-      'tenant',
-      true,
-      '{}'::jsonb,
-      jsonb_build_object(
-        'scope', 'platform',
-        'record_permissions', jsonb_build_object(
-          'system_admin', ARRAY['create', 'read', 'update', 'delete'],
-          'support_admin', ARRAY['create', 'read', 'update'],
-          'support', ARRAY['create', 'read', 'update'],
-          'member_admin', ARRAY['create', 'read', 'update'],
-          'member', ARRAY['create', 'read', 'update']
-        )
-      )
-    );
-  END IF;
-
-  -- community_reply
-  IF NOT EXISTS (SELECT 1 FROM public.types WHERE slug = 'community_reply' AND kind = 'message' AND is_active = true) THEN
-    INSERT INTO public.types (id, app_id, kind, slug, name, description, icon, color, ownership, is_active, validation_schema, design_schema)
-    VALUES (
-      gen_random_uuid(),
-      v_owner_app_id,
-      'message',
-      'community_reply',
-      'Community Reply',
-      'Public reply within a community thread',
-      'message-circle',
-      '#22C55E',
-      'tenant',
-      true,
-      '{}'::jsonb,
-      jsonb_build_object(
-        'scope', 'platform',
-        'record_permissions', jsonb_build_object(
-          'system_admin', ARRAY['create', 'read', 'update', 'delete'],
-          'support_admin', ARRAY['create', 'read', 'update'],
-          'support', ARRAY['create', 'read', 'update'],
-          'member_admin', ARRAY['create', 'read', 'update'],
-          'member', ARRAY['create', 'read', 'update']
-        )
-      )
-    );
-  END IF;
-END $$;
-
--- 1. Support threads -> support_thread
-UPDATE public.threads t
-SET
-  type_id = public._tmp_first_type_id('support_thread'),
-  design_schema = jsonb_set(
-    (SELECT design_schema FROM public.types WHERE id = public._tmp_first_type_id('support_thread')),
-    '{scope}',
-    COALESCE(t.design_schema->'scope', '"account"')::jsonb
-  ),
-  validation_schema = (SELECT validation_schema FROM public.types WHERE id = public._tmp_first_type_id('support_thread'))
-FROM public.items i
-WHERE t.target_type = 'items'
-  AND t.target_id = i.id
-  AND i.type_id = public._tmp_first_type_id('support_ticket')
-  AND t.type_id != public._tmp_first_type_id('support_thread');
-
--- 2. Community threads -> community_thread
-UPDATE public.threads t
-SET
-  type_id = public._tmp_first_type_id('community_thread'),
-  design_schema = jsonb_set(
-    (SELECT design_schema FROM public.types WHERE id = public._tmp_first_type_id('community_thread')),
-    '{scope}',
-    COALESCE(t.design_schema->'scope', '"platform"')::jsonb
-  ),
-  validation_schema = (SELECT validation_schema FROM public.types WHERE id = public._tmp_first_type_id('community_thread'))
-FROM public.items i
-WHERE t.target_type = 'items'
-  AND t.target_id = i.id
-  AND i.type_id = public._tmp_first_type_id('community_post')
-  AND t.type_id != public._tmp_first_type_id('community_thread');
-
--- 3. Support messages -> support_reply
-UPDATE public.messages m
-SET
-  type_id = public._tmp_first_type_id('support_reply'),
-  design_schema = jsonb_set(
-    (SELECT design_schema FROM public.types WHERE id = public._tmp_first_type_id('support_reply')),
-    '{scope}',
-    COALESCE(t.design_schema->'scope', '"account"')::jsonb
-  ),
-  validation_schema = (SELECT validation_schema FROM public.types WHERE id = public._tmp_first_type_id('support_reply'))
-FROM public.threads t
-WHERE m.thread_id = t.id
-  AND t.type_id = public._tmp_first_type_id('support_thread')
-  AND m.type_id != public._tmp_first_type_id('support_reply');
-
--- 4. Community messages -> community_reply
-UPDATE public.messages m
-SET
-  type_id = public._tmp_first_type_id('community_reply'),
-  design_schema = jsonb_set(
-    (SELECT design_schema FROM public.types WHERE id = public._tmp_first_type_id('community_reply')),
-    '{scope}',
-    COALESCE(t.design_schema->'scope', '"platform"')::jsonb
-  ),
-  validation_schema = (SELECT validation_schema FROM public.types WHERE id = public._tmp_first_type_id('community_reply'))
-FROM public.threads t
-WHERE m.thread_id = t.id
-  AND t.type_id = public._tmp_first_type_id('community_thread')
-  AND m.type_id != public._tmp_first_type_id('community_reply');
-
--- Drop the temporary helper
-DROP FUNCTION IF EXISTS public._tmp_first_type_id(text);

package/.framework/migrations/026_fix_rls_policies.sql

@@ -1,47 +0,0 @@
--- Migration 026: Fix RLS policies to use current_actor_id() and runtime design_schema scope
---
--- The policies for threads and messages were using auth.uid() inside get_accessible_accounts(),
--- but that function expects the internal person_id (from current_actor_id()). This broke account
--- hierarchy checks for regular users. Additionally, the policies hardcoded the 'platform' scope
--- check. This migration makes them scope-driven: any non-platform scope is treated as account-scoped.
---
--- Threads and messages now look at the runtime record's stamped design_schema for access, and
--- messages also filter by visibility so internal support notes stay internal.
-
--- threads (runtime record design_schema is the source of truth for scope)
-DROP POLICY IF EXISTS threads_access ON public.threads;
-CREATE POLICY threads_access ON public.threads FOR ALL
-  USING (
-    design_schema->>'scope' = 'platform' AND public.current_actor_id() IS NOT NULL
-    OR account_id IN (SELECT public.get_accessible_accounts(public.current_actor_id()))
-    OR public.current_actor_id() IS NULL
-  );
-
--- messages (inherits thread access from the runtime record design_schema; visibility
--- filters internal notes to support/support_admin roles)
-DROP POLICY IF EXISTS messages_access ON public.messages;
-CREATE POLICY messages_access ON public.messages FOR ALL
-  USING (
-    EXISTS (
-      SELECT 1 FROM public.threads t
-      WHERE t.id = messages.thread_id
-      AND (
-        t.design_schema->>'scope' = 'platform' AND public.current_actor_id() IS NOT NULL
-        OR t.account_id IN (SELECT public.get_accessible_accounts(public.current_actor_id()))
-      )
-    )
-    AND (
-      messages.visibility IS NULL
-      OR messages.visibility = 'external'
-      OR (
-        messages.visibility = 'internal'
-        AND EXISTS (
-          SELECT 1 FROM public.people p
-          JOIN public.roles r ON p.role_id = r.id
-          WHERE p.id = public.current_actor_id()
-          AND (r.slug IN ('support', 'support_admin') OR r.is_system = true)
-        )
-      )
-    )
-    OR public.current_actor_id() IS NULL
-  );

package/.framework/migrations/027_embedding_lifecycle.sql

@@ -1,176 +0,0 @@
--- Migration 027: Embedding lifecycle — approved_at, revoked_at, content_hash
---
--- Adds three columns to the embeddings table so that:
---   1. Only approved embeddings are returned by match_embeddings (hard filter, not prompt-based).
---   2. Embeddings are invalidated automatically when their source item is unpublished or deleted.
---   3. Re-embedding is skipped when content has not changed (content_hash deduplication).
---
--- Adds filter_item_types parameter to match_embeddings RPC so agents can restrict
--- retrieval to specific content types (kb_article, code_chunk, db_schema, etc.) at
--- the DB layer rather than relying on post-processing.
---
--- Adds helper functions revoke_embeddings_for_item and approve_embeddings_for_item
--- called by the items_embedding_sync trigger.
---
--- IMPORTANT: approved_at defaults to now() so all existing embeddings are treated
--- as approved. revoked_at defaults to NULL (not revoked).
-
--- ============================================
--- COLUMNS
--- ============================================
-
-ALTER TABLE public.embeddings
-  ADD COLUMN IF NOT EXISTS approved_at  timestamptz DEFAULT now(),
-  ADD COLUMN IF NOT EXISTS revoked_at   timestamptz DEFAULT NULL,
-  ADD COLUMN IF NOT EXISTS content_hash text        DEFAULT NULL;
-
--- Partial index for fast active-embedding lookups (approved and not revoked)
-CREATE INDEX IF NOT EXISTS embeddings_active_idx
-  ON public.embeddings (account_id, document_id)
-  WHERE approved_at IS NOT NULL AND revoked_at IS NULL;
-
--- ============================================
--- HELPER FUNCTIONS
--- ============================================
-
--- Revoke all embeddings for a given item (called when item leaves published state)
-CREATE OR REPLACE FUNCTION public.revoke_embeddings_for_item(p_item_id uuid)
-RETURNS integer
-LANGUAGE plpgsql
-SECURITY DEFINER
-SET search_path = public
-AS $$
-DECLARE
-  v_count integer;
-BEGIN
-  UPDATE public.embeddings
-  SET    revoked_at = now()
-  WHERE  document_id = p_item_id::text
-  AND    revoked_at  IS NULL;
-
-  GET DIAGNOSTICS v_count = ROW_COUNT;
-  RETURN v_count;
-END;
-$$;
-
--- Approve all embeddings for a given item (called when item re-enters published state)
-CREATE OR REPLACE FUNCTION public.approve_embeddings_for_item(p_item_id uuid)
-RETURNS integer
-LANGUAGE plpgsql
-SECURITY DEFINER
-SET search_path = public
-AS $$
-DECLARE
-  v_count integer;
-BEGIN
-  UPDATE public.embeddings
-  SET    approved_at = now(),
-         revoked_at  = NULL
-  WHERE  document_id = p_item_id::text;
-
-  GET DIAGNOSTICS v_count = ROW_COUNT;
-  RETURN v_count;
-END;
-$$;
-
-GRANT EXECUTE ON FUNCTION public.revoke_embeddings_for_item(uuid) TO service_role;
-GRANT EXECUTE ON FUNCTION public.approve_embeddings_for_item(uuid) TO service_role;
-
--- ============================================
--- ITEMS → EMBEDDINGS SYNC TRIGGER
--- ============================================
--- When an item's status changes, keep its embeddings in sync automatically.
--- published  → approve (clear revoked_at, set approved_at)
--- anything   → revoke  (set revoked_at, leave approved_at intact for audit)
-
-CREATE OR REPLACE FUNCTION public.sync_item_embeddings()
-RETURNS TRIGGER
-LANGUAGE plpgsql
-SECURITY DEFINER
-SET search_path = public
-AS $$
-BEGIN
-  -- Only act on status changes
-  IF OLD.status IS NOT DISTINCT FROM NEW.status THEN
-    RETURN NEW;
-  END IF;
-
-  IF NEW.status = 'published' THEN
-    PERFORM public.approve_embeddings_for_item(NEW.id);
-  ELSE
-    PERFORM public.revoke_embeddings_for_item(NEW.id);
-  END IF;
-
-  RETURN NEW;
-END;
-$$;
-
-DROP TRIGGER IF EXISTS items_embedding_sync ON public.items;
-CREATE TRIGGER items_embedding_sync
-  AFTER UPDATE OF status ON public.items
-  FOR EACH ROW
-  EXECUTE FUNCTION public.sync_item_embeddings();
-
--- ============================================
--- UPDATED match_embeddings RPC
--- ============================================
--- Adds filter_item_types parameter and hard approved_at / revoked_at filter.
--- Backward compatible: existing callers that omit filter_item_types get the same
--- behaviour as before, except that revoked / unapproved embeddings are now excluded.
-
-CREATE OR REPLACE FUNCTION public.match_embeddings(
-  query_embedding      vector(1536),
-  match_count          int            DEFAULT 10,
-  filter_account_ids   uuid[]         DEFAULT NULL,
-  filter_vector_type   text           DEFAULT NULL,
-  similarity_threshold float          DEFAULT 0.15,
-  filter_item_types    text[]         DEFAULT NULL
-)
-RETURNS TABLE (
-  id           uuid,
-  document_id  text,
-  content      text,
-  metadata     jsonb,
-  account_id   uuid,
-  similarity   float
-)
-LANGUAGE plpgsql
-SECURITY DEFINER
-SET search_path = public
-AS $$
-BEGIN
-  RETURN QUERY
-  SELECT
-    e.id,
-    e.document_id,
-    e.content,
-    e.metadata,
-    e.account_id,
-    1 - (e.embedding <=> query_embedding) AS similarity
-  FROM public.embeddings e
-  WHERE
-    -- ── Hard lifecycle filter — never negotiable ──────────────────────────
-    e.approved_at IS NOT NULL
-    AND e.revoked_at  IS NULL
-
-    -- ── Account scope (NULL = no account filter — platform-wide search) ───
-    AND (filter_account_ids IS NULL OR e.account_id = ANY(filter_account_ids))
-
-    -- ── Vector type (NULL = all types) ────────────────────────────────────
-    AND (filter_vector_type IS NULL OR e.metadata->>'vector_type' = filter_vector_type)
-
-    -- ── Item type (NULL = all item types) ─────────────────────────────────
-    AND (filter_item_types IS NULL OR e.metadata->>'item_type' = ANY(filter_item_types))
-
-    -- ── Similarity gate ───────────────────────────────────────────────────
-    AND (1 - (e.embedding <=> query_embedding)) >= similarity_threshold
-
-  ORDER BY e.embedding <=> query_embedding
-  LIMIT match_count;
-END;
-$$;
-
--- Re-grant execute to all roles (replace = drop+create resets grants)
-GRANT EXECUTE ON FUNCTION public.match_embeddings(vector, int, uuid[], text, float, text[]) TO authenticated;
-GRANT EXECUTE ON FUNCTION public.match_embeddings(vector, int, uuid[], text, float, text[]) TO service_role;
-GRANT EXECUTE ON FUNCTION public.match_embeddings(vector, int, uuid[], text, float, text[]) TO anon;

package/.framework/migrations/028_fix_message_data_permissions.sql

@@ -1,49 +0,0 @@
--- Migration 028: Add AI metadata fields to support_reply/community_reply design_schema
---
--- Existing message rows were stamped with the old design_schema, which did not
--- declare permissions for AI metadata fields (message_type, confidence, retrieved_sources,
--- feedback, etc.). The permission sanitizer therefore stripped those fields from API
--- responses, hiding the AI label, confidence badge, sources, and feedback UI.
---
--- This migration updates both the type definitions and the stamped design_schema on
--- every existing message record so the new fields are readable (and feedback writable
--- by members) without loosening the permission model.
-
-DO $$
-DECLARE
-  ai_fields jsonb := '{
-    "message_type": { "data_type": "text", "label": "Message Type", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } },
-    "confidence": { "data_type": "number", "label": "AI Confidence", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } },
-    "retrieval_confidence": { "data_type": "number", "label": "Retrieval Confidence", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } },
-    "retrieved_sources": { "data_type": "json", "label": "Retrieved Sources", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } },
-    "agent_id": { "data_type": "text", "label": "Agent ID", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } },
-    "prompt_config_id": { "data_type": "text", "label": "Prompt Config ID", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } },
-    "sender_type": { "data_type": "text", "label": "Sender Type", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } },
-    "feedback": { "data_type": "text", "label": "Feedback", "system": true, "permissions": { "system_admin": ["read", "write"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read", "write"], "member": ["read", "write"] } },
-    "feedback_at": { "data_type": "datetime", "label": "Feedback At", "system": true, "permissions": { "system_admin": ["read", "write"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read", "write"], "member": ["read", "write"] } },
-    "escalated": { "data_type": "boolean", "label": "Escalated", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } },
-    "suggested_title": { "data_type": "text", "label": "Suggested Title", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } },
-    "tool_calls": { "data_type": "json", "label": "Tool Calls", "system": true, "permissions": { "system_admin": ["read"], "support_admin": ["read"], "support": ["read"], "member_admin": ["read"], "member": ["read"] } }
-  }'::jsonb;
-BEGIN
-  -- Update type definitions
-  UPDATE types
-  SET design_schema = jsonb_set(
-    design_schema,
-    '{fields}',
-    COALESCE(design_schema->'fields', '{}'::jsonb) || ai_fields
-  )
-  WHERE slug IN ('support_reply', 'community_reply')
-    AND kind = 'message';
-
-  -- Update stamped design_schema on existing messages
-  UPDATE messages
-  SET design_schema = jsonb_set(
-    design_schema,
-    '{fields}',
-    COALESCE(design_schema->'fields', '{}'::jsonb) || ai_fields
-  )
-  WHERE type_id IN (
-    SELECT id FROM types WHERE slug IN ('support_reply', 'community_reply') AND kind = 'message'
-  );
-END $$;

package/.framework/migrations/029_tighten_support_triage_prompt.sql

@@ -1,41 +0,0 @@
--- Migration 029: Tighten the support_triage prompt so the AI escalates when no relevant knowledge is retrieved.
---
--- The previous prompt told the agent to "respond helpfully and accurately" without
--- explicitly forbidding general-knowledge answers or clarifying questions. This led to
--- the AI asking questions even when the knowledge base was empty. This migration
--- updates both the prompt_config and the agent's system_prompt to enforce:
---   1. answer only from retrieved knowledge
---   2. escalate immediately when no relevant knowledge is retrieved
---   3. never ask the customer clarifying questions
-
-UPDATE prompt_configs
-SET context_template = 'A customer has submitted the following support request:
-
-{{user_message}}
-
-You may only answer using the relevant information provided in this prompt under ''## Relevant Information''.
-
-Rules:
-- If no relevant information is provided, or if it is insufficient to answer confidently, you MUST escalate to a human agent.
-- Do not ask the customer clarifying questions.
-- Do not answer from general knowledge or make up information.
-- Be concise, accurate, and empathetic.
-
-If you escalate, write a brief message telling the customer that a human support agent will review their request and follow up shortly.',
-    output_mode = 'text',
-    updated_at = now()
-WHERE slug = 'support_triage';
-
-UPDATE ai_agents
-SET system_prompt = 'You are a first-line support agent for a software platform. Your goal is to resolve customer issues accurately and efficiently on the first response, using only the knowledge retrieved for you.
-
-Guidelines:
-- Be concise and clear. Customers want answers, not essays.
-- You may only answer using the retrieved knowledge base articles and prior cases provided in your context.
-- If no relevant knowledge is retrieved, or if it is insufficient to answer confidently, escalate to a human agent immediately.
-- Do not ask the customer clarifying questions.
-- Never fabricate feature behaviour, make promises about the product, or answer from general knowledge.
-- If you escalate, tell the customer that a human support agent will review their request and follow up shortly.
-- Tone: professional but warm. Match the customer''s level of formality.',
-    updated_at = now()
-WHERE name = 'Support Triage Agent';

package/.framework/migrations/030_messages_updated_by.sql

@@ -1,6 +0,0 @@
--- Migration 030: Add missing updated_by column to messages table
--- The messages table was created without updated_by, causing PATCH requests
--- via admin-data to fail when the audit stamp tries to set that field.
-
-ALTER TABLE public.messages
-  ADD COLUMN IF NOT EXISTS updated_by uuid REFERENCES public.people(id) ON DELETE SET NULL;

package/.framework/migrations/031_seed_upsert_constraints.sql

@@ -1,35 +0,0 @@
--- Migration 031: Add unique constraints required for idempotent app seed upserts
---
--- The install-app seeder uses ON CONFLICT(app_id, name) for ai_agents and
--- pipelines, and ON CONFLICT(app_id, slug) for prompt_configs. Without these
--- constraints the seeder falls back to plain INSERT, causing duplicates on
--- re-install.
---
--- Safe to re-run: uses IF NOT EXISTS guard via DO block.
-
-DO $$
-BEGIN
-  -- ai_agents: unique on (app_id, name)
-  IF NOT EXISTS (
-    SELECT 1 FROM pg_constraint
-    WHERE conname = 'ai_agents_app_id_name_key'
-  ) THEN
-    ALTER TABLE public.ai_agents ADD CONSTRAINT ai_agents_app_id_name_key UNIQUE (app_id, name);
-  END IF;
-
-  -- prompt_configs: unique on (app_id, slug)
-  IF NOT EXISTS (
-    SELECT 1 FROM pg_constraint
-    WHERE conname = 'prompt_configs_app_id_slug_key'
-  ) THEN
-    ALTER TABLE public.prompt_configs ADD CONSTRAINT prompt_configs_app_id_slug_key UNIQUE (app_id, slug);
-  END IF;
-
-  -- pipelines: unique on (app_id, name)
-  IF NOT EXISTS (
-    SELECT 1 FROM pg_constraint
-    WHERE conname = 'pipelines_app_id_name_key'
-  ) THEN
-    ALTER TABLE public.pipelines ADD CONSTRAINT pipelines_app_id_name_key UNIQUE (app_id, name);
-  END IF;
-END $$;