@intelligo-dev/core 1.0.0-beta.1 → 1.0.0-beta.13

package/src/db/migrations/0019_db_driven_prompts.sql

@@ -1,20 +0,0 @@
--- Phase C — DB-driven prompts and model config.
---
--- Adds two columns to the agents table that turn the database into the
--- single source of truth for prompts and per-agent model selection. Both
--- columns are nullable so the migration is safe to apply before the seed
--- backfill runs; once the seed has populated the new fields, application
--- code reads only from the database (the legacy
--- apps/app/lib/prompts/career-advisor.ts file is removed in the same
--- phase).
---
--- system_prompt is shaped as the BilingualText JSON {"en": "...", "mn": "..."},
--- matching the existing `name` and `description` columns. model_config is a
--- forward-looking JSONB blob that will eventually replace `default_model`
--- with full routing rules; for now it stores at minimum { primary: "..." }.
---
--- Apply with: psql $DATABASE_URL -f packages/core/src/db/migrations/0019_db_driven_prompts.sql
-
-ALTER TABLE "agents"
-  ADD COLUMN IF NOT EXISTS "system_prompt" jsonb,
-  ADD COLUMN IF NOT EXISTS "model_config" jsonb;

package/src/db/migrations/0020_pending_extractions.sql

@@ -1,35 +0,0 @@
--- Phase F — pending_extractions queue.
---
--- Background-job queue for fact extraction. The chat handler enqueues
--- one row per ended conversation; the worker (in @intelligo-dev/agents)
--- polls 'pending' rows, transitions them through 'processing' →
--- ('completed' | 'failed'), and the conversation_id uniqueness
--- constraint guarantees a conversation is never enqueued twice.
---
--- Cron poller wiring lands in a follow-up; this migration only
--- creates the storage layer so the worker has somewhere to read from.
---
--- Apply with: psql $DATABASE_URL -f packages/core/src/db/migrations/0020_pending_extractions.sql
-
-CREATE TABLE IF NOT EXISTS "pending_extractions" (
-  "id" text PRIMARY KEY,
-  "conversation_id" text NOT NULL,
-  "workspace_id" text NOT NULL REFERENCES "organization"("id") ON DELETE CASCADE,
-  "user_id" text NOT NULL REFERENCES "users"("id") ON DELETE CASCADE,
-  "product_slug" text NOT NULL,
-
-  "status" text NOT NULL DEFAULT 'pending',
-  "attempts" integer NOT NULL DEFAULT 0,
-  "max_attempts" integer NOT NULL DEFAULT 3,
-
-  "last_error" text,
-  "next_retry_at" timestamp,
-
-  "enqueued_at" timestamp NOT NULL DEFAULT NOW(),
-  "started_at" timestamp,
-  "completed_at" timestamp
-);
-
-CREATE INDEX IF NOT EXISTS "pending_extractions_status_idx" ON "pending_extractions" ("status");
-CREATE INDEX IF NOT EXISTS "pending_extractions_workspace_idx" ON "pending_extractions" ("workspace_id");
-CREATE UNIQUE INDEX IF NOT EXISTS "pending_extractions_conversation_uniq" ON "pending_extractions" ("conversation_id");

package/src/db/migrations/0021_rag_documents.sql

@@ -1,39 +0,0 @@
--- Phase H — rag_documents table.
---
--- One shared table that backs every collection in
--- @intelligo-dev/agents/rag. Each typed Collection wrapper in a product
--- package writes through this table with its own `collection` slug
--- and Zod-validated metadata, so adding a new collection means
--- adding a TS file, not running a migration.
---
--- The pgvector index uses IVFFlat with cosine ops; the lists
--- parameter starts conservative for early-launch traffic and can be
--- tuned upward via REINDEX once we measure real recall vs. query
--- latency. The composite (collection, embedding) layout means a
--- per-collection ANN search filters first then ranks.
---
--- Apply with: psql $DATABASE_URL -f packages/core/src/db/migrations/0021_rag_documents.sql
-
-CREATE TABLE IF NOT EXISTS "rag_documents" (
-  "id" text PRIMARY KEY,
-  "collection" text NOT NULL,
-  "external_id" text,
-
-  "content" text NOT NULL,
-  "metadata" jsonb NOT NULL DEFAULT '{}'::jsonb,
-  "embedding" vector(1536),
-
-  "created_at" timestamp NOT NULL DEFAULT NOW(),
-  "updated_at" timestamp NOT NULL DEFAULT NOW()
-);
-
-CREATE INDEX IF NOT EXISTS "rag_documents_collection_idx" ON "rag_documents" ("collection");
-CREATE UNIQUE INDEX IF NOT EXISTS "rag_documents_collection_external_uniq" ON "rag_documents" ("collection", "external_id");
-
--- IVFFlat index for cosine similarity. lists=100 is a reasonable
--- starting point for ~10k documents per collection; bump after
--- measuring recall.
-CREATE INDEX IF NOT EXISTS "rag_documents_embedding_idx"
-  ON "rag_documents"
-  USING ivfflat ("embedding" vector_cosine_ops)
-  WITH (lists = 100);

package/src/db/migrations/0022_user_quotas_usage_jsonb.sql

@@ -1,70 +0,0 @@
--- NOTE (2026-08-26): user_quotas is created here.
---
--- No migration ever created it — the table existed only in schema.ts,
--- so every environment got it from `drizzle-kit push` and replaying
--- the chain against an empty database died on the ALTER below. Of the
--- 49 tables in the schema it was the only one missing from the chain.
---
--- Created in this file rather than a new earlier one because this is
--- the first migration that touches the table; a repair migration would
--- have needed a number that sorts between 0021 and 0022. Guarded, so
--- databases that already have it are unaffected.
-CREATE TABLE IF NOT EXISTS "user_quotas" (
-	"id" text PRIMARY KEY NOT NULL,
-	"user_id" text NOT NULL,
-	"workspace_id" text NOT NULL,
-	"plan" text DEFAULT 'free' NOT NULL,
-	"chat_messages_used" integer DEFAULT 0 NOT NULL,
-	"assessments_used" integer DEFAULT 0 NOT NULL,
-	"reports_used" integer DEFAULT 0 NOT NULL,
-	"total_cost_usd" real DEFAULT 0 NOT NULL,
-	"created_at" timestamp DEFAULT now() NOT NULL,
-	"updated_at" timestamp DEFAULT now() NOT NULL,
-	CONSTRAINT "user_quotas_user_id_unique" UNIQUE("user_id")
-);
---> statement-breakpoint
-DO $$ BEGIN
-  ALTER TABLE "user_quotas" ADD CONSTRAINT "user_quotas_user_id_users_id_fk"
-    FOREIGN KEY ("user_id") REFERENCES "public"."users"("id") ON DELETE cascade ON UPDATE no action;
-EXCEPTION WHEN duplicate_object THEN NULL;
-END $$;
---> statement-breakpoint
-DO $$ BEGIN
-  ALTER TABLE "user_quotas" ADD CONSTRAINT "user_quotas_workspace_id_organization_id_fk"
-    FOREIGN KEY ("workspace_id") REFERENCES "public"."organization"("id") ON DELETE cascade ON UPDATE no action;
-EXCEPTION WHEN duplicate_object THEN NULL;
-END $$;
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "user_quotas_user_id_idx" ON "user_quotas" USING btree ("user_id");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "user_quotas_workspace_id_idx" ON "user_quotas" USING btree ("workspace_id");
---> statement-breakpoint
-
--- Wave 4 — userQuotas.usage JSONB column for generic per-action counters.
---
--- Adds a generic `usage` JSONB column alongside the legacy career-only
--- chat_messages_used / assessments_used / reports_used integer columns.
--- The new column starts at '{}' for every row; recordFeatureUsage in
--- @intelligo-dev/billing/feature-quota.ts dual-writes both the legacy
--- column AND the corresponding `usage[action]` slot so the read path
--- can be flipped atomically in a follow-up commit once production
--- soak confirms the JSONB pathway is reliable.
---
--- Backfill query (optional, for any rows that already have legacy
--- counts that need to be reflected in the JSONB shape):
---
---   UPDATE user_quotas
---   SET usage = jsonb_build_object(
---     'chat', chat_messages_used,
---     'assessment', assessments_used,
---     'report', reports_used
---   )
---   WHERE usage = '{}'::jsonb;
---
--- Run the backfill once after the deploy and verify counts match
--- before flipping the read path.
---
--- Apply with: psql $DATABASE_URL -f packages/core/src/db/migrations/0022_user_quotas_usage_jsonb.sql
-
-ALTER TABLE "user_quotas"
-  ADD COLUMN IF NOT EXISTS "usage" jsonb NOT NULL DEFAULT '{}'::jsonb;

package/src/db/migrations/0023_user_facts_user_scoped_unique.sql

@@ -1,17 +0,0 @@
--- AI-ARCHITECTURE follow-up: user_facts uniqueness must include user_id.
---
--- The original 0018 migration scoped the unique index to
--- (workspace_id, category, key), which made it impossible for two
--- members of the same org (family, classroom, team) to hold the
--- same fact key — e.g. two students both with `interest: mathematics`.
--- The second upsert would collide on the unique index and either
--- fail or silently overwrite the first user's fact.
---
--- Drop the old index and replace it with a (user_id, workspace_id,
--- category, key) unique index so facts are always scoped to the
--- owning user.
-
-DROP INDEX IF EXISTS "user_facts_workspace_category_key_uniq";
---> statement-breakpoint
-CREATE UNIQUE INDEX "user_facts_user_workspace_category_key_uniq"
-	ON "user_facts" USING btree ("user_id", "workspace_id", "category", "key");

package/src/db/migrations/0024_user_memories_hnsw.sql

@@ -1,23 +0,0 @@
--- AI-ARCHITECTURE follow-up: switch user_memories embedding index to HNSW.
---
--- The original 0018 migration used IVFFlat with `lists = 100`, a value
--- tuned for ~100k–1M rows. At launch the table starts empty, so for
--- the first several months IVFFlat recall will be degraded: with
--- rows << lists the probe count dominates and approximation quality
--- drops.
---
--- HNSW (available in pgvector >= 0.5.0) has no such tuning cliff —
--- recall is good from a handful of rows up through tens of millions,
--- at the cost of somewhat higher build time and ~2x memory per vector.
--- For this workload (synthesis-time recall, not per-request search)
--- that tradeoff is clearly worth it.
---
--- m / ef_construction values follow the pgvector docs' defaults
--- tuned for text embeddings; we can raise ef_construction later via
--- REINDEX if recall needs tightening.
-
-DROP INDEX IF EXISTS "user_memories_embedding_ivfflat";
---> statement-breakpoint
-CREATE INDEX "user_memories_embedding_hnsw"
-	ON "user_memories" USING hnsw ("embedding" vector_cosine_ops)
-	WITH (m = 16, ef_construction = 64);

package/src/db/migrations/0025_audit_trigger_errcode.sql

@@ -1,21 +0,0 @@
--- AI-ARCHITECTURE follow-up: fix audit trigger exception class.
---
--- 0018 used ERRCODE 25006 (read_only_sql_transaction) for the
--- append-only guard on user_memory_audit. That code is documented
--- for "SQL transaction is read-only" and is semantically wrong for
--- "this table rejects UPDATE/DELETE" — a Sentry filter or pg error
--- class handler could misroute the exception into the transient
--- retry bucket.
---
--- P0001 (raise_exception) is the correct generic class for
--- application-level invariants raised via RAISE EXCEPTION. The
--- trigger still fires on BEFORE UPDATE and BEFORE DELETE and the
--- hint stays PII-free.
-
-CREATE OR REPLACE FUNCTION public.user_memory_audit_block_mutation()
-	RETURNS trigger AS $$
-BEGIN
-	RAISE EXCEPTION 'user_memory_audit is append-only'
-		USING ERRCODE = 'P0001', HINT = 'INSERT new audit rows; do not UPDATE or DELETE existing ones.';
-END;
-$$ LANGUAGE plpgsql;

package/src/db/migrations/0026_user_profile_snapshots_composite_pk.sql

@@ -1,17 +0,0 @@
--- AI-ARCHITECTURE follow-up: user_profile_snapshots composite primary key.
---
--- 0018 used user_id alone as the PK, which hardcoded "one snapshot per
--- user globally". The moment a user belongs to more than one workspace
--- (family + classroom, personal + team, etc.) those workspaces would
--- be forced to share a single synthesized profile — collapsing
--- context that should stay separate.
---
--- Switch to a composite PK on (user_id, workspace_id). Existing rows
--- already have workspace_id populated, so the migration is a straight
--- PK drop + re-add.
-
-ALTER TABLE "user_profile_snapshots" DROP CONSTRAINT "user_profile_snapshots_pkey";
---> statement-breakpoint
-ALTER TABLE "user_profile_snapshots"
-	ADD CONSTRAINT "user_profile_snapshots_user_id_workspace_id_pk"
-	PRIMARY KEY ("user_id", "workspace_id");

package/src/db/migrations/0027_billing_settings_mnt_columns.sql

@@ -1,54 +0,0 @@
--- Wave 4 — MNT-denominated billing + live settings row.
---
--- Adds the authoritative MNT columns that `packages/billing/src/quota.ts`
--- reads on every chat turn (chargedMnt, balanceMnt, credits*Mnt) and the
--- singleton `billing_settings` row that holds the current FX rate and
--- margin multiplier. The application reads these in-process with a 60s
--- TTL cache so prices can be tuned without a code push.
---
--- Safe to re-run: all statements use IF NOT EXISTS.
---
--- Apply with:
---   psql $DATABASE_URL -f packages/core/src/db/migrations/0027_billing_settings_mnt_columns.sql
-
--- billing_settings — singleton config row (id = 'default').
-CREATE TABLE IF NOT EXISTS "billing_settings" (
-  "id" text PRIMARY KEY NOT NULL,
-  "usd_to_mnt_rate" integer NOT NULL DEFAULT 3450,
-  "margin_multiplier_bp" integer NOT NULL DEFAULT 400,
-  "updated_at" timestamp NOT NULL DEFAULT now()
-);
---> statement-breakpoint
-
--- Seed the singleton row so getBillingSettings() has a hit on fresh installs.
-INSERT INTO "billing_settings" ("id", "usd_to_mnt_rate", "margin_multiplier_bp")
-VALUES ('default', 3450, 400)
-ON CONFLICT ("id") DO NOTHING;
---> statement-breakpoint
-
--- credit_balances — MNT balance columns (legacy `balance` column left intact).
-ALTER TABLE "credit_balances"
-  ADD COLUMN IF NOT EXISTS "balance_mnt" integer NOT NULL DEFAULT 0,
-  ADD COLUMN IF NOT EXISTS "total_purchased_mnt" integer NOT NULL DEFAULT 0,
-  ADD COLUMN IF NOT EXISTS "total_used_mnt" integer NOT NULL DEFAULT 0;
---> statement-breakpoint
-
--- usage_records — per-request MNT + trace fields.
-ALTER TABLE "usage_records"
-  ADD COLUMN IF NOT EXISTS "margin_multiplier" real NOT NULL DEFAULT 0,
-  ADD COLUMN IF NOT EXISTS "fx_rate" real NOT NULL DEFAULT 0,
-  ADD COLUMN IF NOT EXISTS "charged_mnt" integer NOT NULL DEFAULT 0,
-  ADD COLUMN IF NOT EXISTS "request_id" text,
-  ADD COLUMN IF NOT EXISTS "conversation_id" text;
---> statement-breakpoint
-
--- monthly_usage — MNT aggregate for O(1) plan quota checks.
-ALTER TABLE "monthly_usage"
-  ADD COLUMN IF NOT EXISTS "charged_mnt" integer NOT NULL DEFAULT 0;
---> statement-breakpoint
-
--- trial_credits — MNT-denominated grant replaces token counters.
-ALTER TABLE "trial_credits"
-  ADD COLUMN IF NOT EXISTS "initial_credits_mnt" integer NOT NULL DEFAULT 5000,
-  ADD COLUMN IF NOT EXISTS "credits_used_mnt" integer NOT NULL DEFAULT 0,
-  ADD COLUMN IF NOT EXISTS "credits_remaining_mnt" integer NOT NULL DEFAULT 5000;

package/src/db/migrations/0028_trial_credits_normalized_email.sql

@@ -1,37 +0,0 @@
--- Indexed per-email trial abuse check.
---
--- checkTrialAbuse() previously did `SELECT created_by_email FROM
--- trial_credits` (no WHERE, no LIMIT) and filtered in JS. That's a
--- full-table scan on every signup. Adding a normalized_email column
--- (populated at provisioning time) plus a btree index lets the same
--- check become `SELECT count(*) WHERE normalized_email = ?` — O(log n)
--- with index-only scan.
---
--- Apply with:
---   psql $DATABASE_URL -f packages/core/src/db/migrations/0028_trial_credits_normalized_email.sql
-
-ALTER TABLE "trial_credits"
-  ADD COLUMN IF NOT EXISTS "normalized_email" text;
---> statement-breakpoint
-
--- Backfill existing rows so the abuse check behaves consistently for
--- trials provisioned before this migration. Mirrors the JS rule in
--- normalizeEmailForAbuseCheck: lowercase, drop +aliases, collapse dots
--- on gmail/googlemail, rewrite googlemail.com → gmail.com.
-UPDATE "trial_credits"
-SET "normalized_email" = (
-  CASE
-    WHEN split_part(lower(trim("created_by_email")), '@', 2) IN ('gmail.com', 'googlemail.com')
-      THEN replace(split_part(split_part(lower(trim("created_by_email")), '@', 1), '+', 1), '.', '')
-           || '@gmail.com'
-    ELSE split_part(split_part(lower(trim("created_by_email")), '@', 1), '+', 1)
-         || '@'
-         || split_part(lower(trim("created_by_email")), '@', 2)
-  END
-)
-WHERE "created_by_email" IS NOT NULL
-  AND "normalized_email" IS NULL;
---> statement-breakpoint
-
-CREATE INDEX IF NOT EXISTS "trial_credits_normalized_email_idx"
-  ON "trial_credits" ("normalized_email");

package/src/db/migrations/0029_usage_records_conversation_idx.sql

@@ -1,13 +0,0 @@
--- Cover the conversation deep-link path on the usage dashboard.
---
--- usage_table.tsx renders a per-row link to /chat/<conversationId>;
--- once traffic grows, any reverse lookup (e.g. "all usage for this
--- conversation") has to seq-scan on the nullable conversation_id
--- column. Adding the index now while the table is still small is
--- cheap and future-proofs the lookup path.
---
--- Apply with:
---   psql $DATABASE_URL -f packages/core/src/db/migrations/0029_usage_records_conversation_idx.sql
-
-CREATE INDEX IF NOT EXISTS "usage_records_conversation_id_idx"
-  ON "usage_records" ("conversation_id");

package/src/db/migrations/0030_pending_extractions_composite_idx.sql

@@ -1,11 +0,0 @@
--- DB-02: Composite index for efficient workspace-scoped extraction polling.
---
--- The worker queries "status = 'pending'" filtered by workspaceId, but the
--- existing index is on status alone. A scan across all workspaces is
--- expensive as the queue grows. This composite index allows index-only
--- scan for workspace-scoped pending-extraction queries.
---
--- Apply with: psql $DATABASE_URL -f packages/core/src/db/migrations/0030_pending_extractions_composite_idx.sql
-
-CREATE INDEX IF NOT EXISTS "pending_extractions_status_workspace_idx"
-  ON "pending_extractions" ("status", "workspace_id");

package/src/db/migrations/0031_rag_documents_hnsw.sql

@@ -1,16 +0,0 @@
--- DB-04: Migrate rag_documents vector index from IVFFlat to HNSW.
---
--- IVFFlat with lists=100 degrades at < 100k docs (probe count dominates,
--- approximation quality drops). HNSW has no tuning cliff — recall is good
--- from a handful of rows through tens of millions.
---
--- Template: 0011_hnsw_vector_index.sql + 0024_user_memories_hnsw.sql
--- m / ef_construction follow pgvector docs defaults for text embeddings.
---
--- Apply with: psql $DATABASE_URL -f packages/core/src/db/migrations/0031_rag_documents_hnsw.sql
-
-DROP INDEX IF EXISTS "rag_documents_embedding_idx";
---> statement-breakpoint
-CREATE INDEX "rag_documents_embedding_hnsw_idx"
-  ON "rag_documents" USING hnsw ("embedding" vector_cosine_ops)
-  WITH (m = 16, ef_construction = 64);

package/src/db/migrations/0032_rate_limit_unique_idx.sql

@@ -1,16 +0,0 @@
--- DB-06: Unique constraint for rate limit deduplication.
---
--- Enables INSERT ... ON CONFLICT DO NOTHING as the authoritative rate limit
--- check instead of pre-count + insert (which allows 2× concurrent requests through).
--- The composite unique index is on (workspaceId, endpoint, minute_bucket).
--- minute_bucket floors requestedAt to the minute, so entries within the same
--- minute window conflict and only the first is inserted.
---
--- Apply with: psql $DATABASE_URL -f packages/core/src/db/migrations/0032_rate_limit_unique_idx.sql
-
-CREATE UNIQUE INDEX IF NOT EXISTS "rate_limit_entries_unique_bucket_idx"
-  ON "rate_limit_entries" (
-    "workspace_id",
-    "endpoint",
-    date_trunc('minute', "requested_at")
-  );

package/src/db/migrations/0033_pending_extractions_partial_idx.sql

@@ -1,18 +0,0 @@
--- DB-01: Partial index for workspace-scoped pending extraction polling.
---
--- Workers claim rows by: WHERE status = 'pending' AND workspace_id = ?
--- The existing composite index (status, workspace_id) forces a scan of
--- ALL pending rows across all workspaces before filtering by workspace.
--- This partial index narrows the scan to just pending rows for the target
--- workspace — an index-only scan at O(log n) per workspace instead of
--- O(pending_rows_total).
---
--- Applies to: claimNextExtraction() and listPendingExtractions() in
--- packages/agents/src/extraction/queue.ts
---
--- Run with: psql $DATABASE_URL -f packages/core/src/db/migrations/0033_pending_extractions_partial_idx.sql
--- Or via: cd packages/core && pnpm drizzle-kit push
-
-CREATE INDEX IF NOT EXISTS pending_extractions_workspace_pending_idx
-  ON pending_extractions (workspace_id)
-  WHERE status = 'pending';

package/src/db/migrations/0034_rate_limit_count.sql

@@ -1,9 +0,0 @@
--- B-05b: Rate limiter admits only ONE request per minute bucket.
---
--- The B-05 fix replaced check-then-insert with a unique constraint on
--- (workspace_id, endpoint, minute_bucket) + ON CONFLICT DO NOTHING, but
--- that admits exactly one request per bucket — the per-plan limit
--- (10/60/300 rpm) was never consulted. Add a counter column so the
--- upsert becomes DO UPDATE SET count = count + 1 RETURNING count, and
--- admission is count <= limit.
-ALTER TABLE "rate_limit_entries" ADD COLUMN IF NOT EXISTS "count" integer DEFAULT 1 NOT NULL;

package/src/db/migrations/0035_credit_reservations.sql

@@ -1,24 +0,0 @@
--- B-06: Close the checkQuota → recordTokenUsage TOCTOU window.
---
--- checkQuota was a pure read; the debit happened minutes later in
--- recordTokenUsage, so N concurrent requests could all pass admission
--- against the same balance. Admission now inserts a reservation for the
--- worst-case MNT estimate in the same transaction that sums the other
--- active reservations. recordTokenUsage settles it; abandoned rows
--- expire via expires_at (TTL >= chat route maxDuration) and are cleaned
--- by the cleanup cron.
-CREATE TABLE IF NOT EXISTS "credit_reservations" (
-	"id" text PRIMARY KEY NOT NULL,
-	"workspace_id" text NOT NULL,
-	"request_id" text NOT NULL,
-	"estimated_mnt" integer NOT NULL,
-	"status" text DEFAULT 'active' NOT NULL,
-	"created_at" timestamp DEFAULT now() NOT NULL,
-	"expires_at" timestamp NOT NULL,
-	"settled_at" timestamp,
-	CONSTRAINT "credit_reservations_request_id_unique" UNIQUE("request_id")
-);
---> statement-breakpoint
-ALTER TABLE "credit_reservations" ADD CONSTRAINT "credit_reservations_workspace_id_organization_id_fk" FOREIGN KEY ("workspace_id") REFERENCES "public"."organization"("id") ON DELETE cascade ON UPDATE no action;
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "credit_reservations_active_idx" ON "credit_reservations" USING btree ("workspace_id","status","expires_at");

package/src/db/migrations/0036_executions_audit_jobs.sql

@@ -1,96 +0,0 @@
--- Phase 2: the SaaS execution boundary (ADR-0003, ADR-0004).
---
--- Three tables, three owning packages:
---   executions   → @intelligo-dev/executions — one row per AI run: actor,
---                  workspace, capability, entitlement outcome, status,
---                  usage, cost. Records nothing about agents/tools/
---                  messages, which stay native to the AI framework.
---   audit_events → @intelligo-dev/audit — append-only who-did-what.
---   jobs         → @intelligo-dev/jobs — Postgres-backed queue (claimed
---                  with FOR UPDATE SKIP LOCKED).
---
--- usage_records gains execution_id rather than being duplicated into a
--- new usage_events table: it already IS the per-request usage/cost
--- detail. The rename happens with the Phase 4 package split.
-
-CREATE TABLE IF NOT EXISTS "executions" (
-	"id" text PRIMARY KEY NOT NULL,
-	"workspace_id" text NOT NULL,
-	"user_id" text,
-	"capability" text NOT NULL,
-	"request_id" text NOT NULL,
-	"status" text DEFAULT 'running' NOT NULL,
-	"model" text,
-	"input_tokens" integer,
-	"output_tokens" integer,
-	"total_tokens" integer,
-	"charged_mnt" integer,
-	"reserved_mnt" integer,
-	"refusal_reason" text,
-	"error_message" text,
-	"started_at" timestamp DEFAULT now() NOT NULL,
-	"finished_at" timestamp,
-	"duration_ms" integer,
-	"metadata" jsonb,
-	CONSTRAINT "executions_request_id_unique" UNIQUE("request_id")
-);
---> statement-breakpoint
-CREATE TABLE IF NOT EXISTS "audit_events" (
-	"id" text PRIMARY KEY NOT NULL,
-	"workspace_id" text,
-	"actor_id" text,
-	"actor_kind" text DEFAULT 'user' NOT NULL,
-	"action" text NOT NULL,
-	"resource_kind" text NOT NULL,
-	"resource_id" text,
-	"outcome" text DEFAULT 'ok' NOT NULL,
-	"metadata" jsonb,
-	"created_at" timestamp DEFAULT now() NOT NULL
-);
---> statement-breakpoint
-CREATE TABLE IF NOT EXISTS "jobs" (
-	"id" text PRIMARY KEY NOT NULL,
-	"workspace_id" text,
-	"kind" text NOT NULL,
-	"payload" jsonb,
-	"status" text DEFAULT 'pending' NOT NULL,
-	"attempts" integer DEFAULT 0 NOT NULL,
-	"max_attempts" integer DEFAULT 3 NOT NULL,
-	"run_at" timestamp DEFAULT now() NOT NULL,
-	"started_at" timestamp,
-	"finished_at" timestamp,
-	"last_error" text,
-	"created_at" timestamp DEFAULT now() NOT NULL
-);
---> statement-breakpoint
-ALTER TABLE "usage_records" ADD COLUMN IF NOT EXISTS "execution_id" text;
---> statement-breakpoint
-ALTER TABLE "executions" ADD CONSTRAINT "executions_workspace_id_organization_id_fk" FOREIGN KEY ("workspace_id") REFERENCES "public"."organization"("id") ON DELETE cascade ON UPDATE no action;
---> statement-breakpoint
-ALTER TABLE "executions" ADD CONSTRAINT "executions_user_id_users_id_fk" FOREIGN KEY ("user_id") REFERENCES "public"."users"("id") ON DELETE set null ON UPDATE no action;
---> statement-breakpoint
-ALTER TABLE "audit_events" ADD CONSTRAINT "audit_events_workspace_id_organization_id_fk" FOREIGN KEY ("workspace_id") REFERENCES "public"."organization"("id") ON DELETE cascade ON UPDATE no action;
---> statement-breakpoint
-ALTER TABLE "audit_events" ADD CONSTRAINT "audit_events_actor_id_users_id_fk" FOREIGN KEY ("actor_id") REFERENCES "public"."users"("id") ON DELETE set null ON UPDATE no action;
---> statement-breakpoint
-ALTER TABLE "jobs" ADD CONSTRAINT "jobs_workspace_id_organization_id_fk" FOREIGN KEY ("workspace_id") REFERENCES "public"."organization"("id") ON DELETE cascade ON UPDATE no action;
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "executions_workspace_started_idx" ON "executions" USING btree ("workspace_id","started_at");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "executions_status_idx" ON "executions" USING btree ("status","started_at");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "executions_capability_idx" ON "executions" USING btree ("capability","started_at");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "audit_events_workspace_created_idx" ON "audit_events" USING btree ("workspace_id","created_at");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "audit_events_action_idx" ON "audit_events" USING btree ("action","created_at");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "audit_events_resource_idx" ON "audit_events" USING btree ("resource_kind","resource_id");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "jobs_claim_idx" ON "jobs" USING btree ("status","run_at");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "jobs_kind_idx" ON "jobs" USING btree ("kind","status");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "jobs_workspace_idx" ON "jobs" USING btree ("workspace_id");
---> statement-breakpoint
-CREATE INDEX IF NOT EXISTS "usage_records_execution_id_idx" ON "usage_records" USING btree ("execution_id");

package/src/db/migrations/0037_rate_limit_minute_bucket.sql

@@ -1,46 +0,0 @@
--- Repair the rate-limit schema so a fresh database matches the code.
---
--- 0032 documented a unique constraint on (workspace_id, endpoint,
--- minute_bucket) but created an EXPRESSION index on
--- date_trunc('minute', requested_at) instead, and no migration ever
--- added the minute_bucket column. checkRateLimit's
--- `ON CONFLICT (workspace_id, endpoint, minute_bucket)` can only
--- resolve against a constraint on those literal columns, so replaying
--- the committed history against an empty database produced a
--- rate_limit_entries table that throws
--- `column "minute_bucket" does not exist` on every chat request.
--- Production only worked because the live database had been synced
--- with `drizzle-kit push` straight from schema.ts, bypassing these
--- files entirely.
-
-ALTER TABLE "rate_limit_entries"
-  ADD COLUMN IF NOT EXISTS "minute_bucket" timestamp;
---> statement-breakpoint
-
--- Backfill so the NOT NULL below can be applied to existing rows.
-UPDATE "rate_limit_entries"
-  SET "minute_bucket" = date_trunc('minute', "requested_at")
-  WHERE "minute_bucket" IS NULL;
---> statement-breakpoint
-
-ALTER TABLE "rate_limit_entries"
-  ALTER COLUMN "minute_bucket" SET NOT NULL;
---> statement-breakpoint
-
--- The expression index carries the name the constraint needs.
-DROP INDEX IF EXISTS "rate_limit_entries_unique_bucket_idx";
---> statement-breakpoint
-
--- Collapse any duplicate buckets the expression index allowed through
--- before the real constraint can be created.
-DELETE FROM "rate_limit_entries" a
-  USING "rate_limit_entries" b
-  WHERE a.ctid < b.ctid
-    AND a."workspace_id" = b."workspace_id"
-    AND a."endpoint" = b."endpoint"
-    AND a."minute_bucket" = b."minute_bucket";
---> statement-breakpoint
-
-ALTER TABLE "rate_limit_entries"
-  ADD CONSTRAINT "rate_limit_entries_unique_bucket_idx"
-  UNIQUE ("workspace_id", "endpoint", "minute_bucket");

package/src/db/migrations/0038_user_quotas_generic_usage.sql

@@ -1,25 +0,0 @@
--- Finish the user_quotas cutover to a generic usage map (B6).
---
--- The table carried three career-specific counters — chat_messages_used,
--- assessments_used, reports_used — alongside the generic `usage` JSONB
--- added in migration 0022. Since then recordFeatureUsage dual-wrote both
--- while reads still preferred the columns, so a public package's schema
--- named a vertical's actions and no vertical could add a fourth counter
--- without a migration to Intelligo (ADR-0004, ADR-0006).
---
--- Backfill first: rows written since the dual-write started already have
--- the keys in `usage`, and those values win. Rows that predate it have a
--- non-zero column and no key, so the built object supplies them. `||` is
--- right-biased, hence usage on the right.
-
-UPDATE user_quotas
-   SET usage = jsonb_build_object(
-                 'chat',       COALESCE(chat_messages_used, 0),
-                 'assessment', COALESCE(assessments_used, 0),
-                 'report',     COALESCE(reports_used, 0)
-               ) || COALESCE(usage, '{}'::jsonb);
-
-ALTER TABLE user_quotas
-  DROP COLUMN IF EXISTS chat_messages_used,
-  DROP COLUMN IF EXISTS assessments_used,
-  DROP COLUMN IF EXISTS reports_used;