create-ailk 0.24.0 → 0.25.1

package/templates/database/migrations/20260920130000_lead_workspace_source_index/migration.sql

@@ -1,57 +0,0 @@
--- #6246 — Lead gains a second workspace-scoped composite index, this one
--- for the per-magnet Signups/Subscribers/Messages read.
---
--- The read is workspace_id = $1 AND source = $2, ordered by created_at desc
--- (spec § 1.5/D1) — an EXACT-EQUALITY match on `source`, distinct from
--- 20260920120000_lead_handled_at's own (workspace_id, handled_at)
--- composite, which serves an `IN`-over-a-four-value-allowlist filter. The
--- two indexes serve two different query shapes over the same two-column
--- narrowing pattern; neither can stand in for the other.
---
--- PURELY ADDITIVE (mirrors 20260920120000_lead_handled_at's own NFR1): one
--- CREATE INDEX, no column, no backfill, no data transformation — so this
--- migration carries none of the census/post-assertion apparatus
--- 20260919140000_inbox_workspace_key needed to prove ITS backfill correct.
---
--- RE-RUNNABLE (mirrors the same precedent's NFR2): IF NOT EXISTS on the
--- index, guarded on the referenced column's presence.
---
--- ORDER-SAFE: the index references "workspace_id", which
--- 20260919140000_inbox_workspace_key adds — a migration this one sorts
--- strictly after (20260920130000 > 20260919140000), so in the normal case
--- the guard below is a formality, kept for the same reason its precedent
--- keeps one: IF NOT EXISTS guards the INDEX's own name, not the column it
--- references, so an unguarded CREATE INDEX would abort inside prisma
--- migrate's per-migration transaction and wedge the ledger for the whole
--- deployment if that migration were ever skipped, renamed, or rolled back
--- on a given database.
---
--- CREATE INDEX is NOT CONCURRENT, and cannot be: CONCURRENTLY may not run
--- inside prisma migrate's per-migration transaction. It therefore takes a
--- lock on "leads" for its duration, the SAME accepted risk
--- 20260920120000_lead_handled_at's own header names — "leads" carries five
--- indexes already (siteId, createdAt, email, workspaceId,
--- (workspaceId, handledAt)) and is small at this pin. A deployment with a
--- large leads table should create this index out-of-band with
--- CONCURRENTLY first — the IF NOT EXISTS guard then makes this statement a
--- no-op.
---
--- Rollback: DROP INDEX "leads_workspace_id_source_idx";
--- Safe at any point — this migration adds no column and no application
--- state depends on the index existing, only on its absence being slower.
-
--- CreateIndex — the read is workspace_id = $1 AND source = $2, ordered by
--- created_at desc (spec § 1.5/D1). A two-column (workspace_id, source)
--- index serves it directly: it narrows to the tenant and then to the
--- exact-match magnet source in one pass.
-DO $$ BEGIN
-  IF EXISTS (
-    SELECT 1 FROM information_schema.columns
-     WHERE table_name = 'leads' AND column_name = 'workspace_id'
-  ) THEN
-    CREATE INDEX IF NOT EXISTS "leads_workspace_id_source_idx"
-      ON "leads"("workspace_id", "source");
-  ELSE
-    RAISE NOTICE '#6246: leads.workspace_id absent — index skipped. 20260919140000_inbox_workspace_key has not run against this database; the per-magnet list read cannot be served efficiently until it does.';
-  END IF;
-END $$;

package/templates/database/migrations/20260921120000_deliverable_grant_workspace_key/migration.sql

@@ -1,68 +0,0 @@
--- #6310 D8/D15 — DeliverableGrant gains its own `workspace_id`.
---
--- The one migration this spec carries — it moves no `DeliverableAsset` row
--- (D3: existing rows keep delivering, unmigrated; AC3's grounding is in the
--- spec, not here). It restores the serve-time tenancy re-check the legacy
--- arm already has (`asset.siteId !== grant.siteId`, routes/deliverables/index.ts)
--- for the new `Asset`-backed grant class: `workspaceId` is written at mint,
--- from the SAME value that authorized the mint-time resolution (D15), so the
--- serve read is `{ id, workspaceId }` rather than an unscoped `{ id }`.
---
--- NULLABLE, no default — mirrors database/migrations/20260919140000_inbox_workspace_key's
--- idiom step for step: a value this migration cannot derive (every grant
--- that exists at migration time is a legacy `dasset_`/`playbook:` grant
--- whose serve arm never reads this column) is left UNSET rather than
--- guessed. NO BACKFILL: there is nothing to backfill — the column has no
--- source column to derive from (unlike site_id -> workspace_id, this is a
--- wholly new fact, captured only at a FUTURE mint).
---
--- RE-RUNNABLE: `ADD COLUMN IF NOT EXISTS` covers the column; the format
--- CHECK is wrapped in an existence-guarded `DO $$` block since Postgres has
--- no `ADD CONSTRAINT IF NOT EXISTS`. No index — the column is read only by
--- `findFirst`-by-id, never filtered on.
---
--- Rollback: ALTER TABLE "deliverable_grants" DROP CONSTRAINT
--- "deliverable_grants_workspace_id_format", DROP COLUMN "workspace_id".
--- Safe unconditionally at this pin — no `asset_`-class grant exists yet to
--- lose data from.
-
--- The census the post-assertion compares against. ON COMMIT DROP: `prisma
--- migrate` runs each migration in one transaction, so this disappears with it.
-CREATE TEMP TABLE "_6310_deliverable_grants_census" ON COMMIT DROP AS
-  SELECT count(*) AS n FROM "deliverable_grants";
-
--- AlterTable
-ALTER TABLE "deliverable_grants" ADD COLUMN IF NOT EXISTS "workspace_id" TEXT;
-
--- Format CHECK — NULL-permitting, in the exact shape of the CHECKs
--- 20260713192429_prefixed_uuid_entity_ids/migration.sql already applies to
--- every other `workspace_id` column (mirrored verbatim from #6203's own
--- migration). Existence-guarded because Postgres has no
--- `ADD CONSTRAINT IF NOT EXISTS`.
-DO $$ BEGIN
-  IF NOT EXISTS (
-    SELECT 1 FROM pg_constraint WHERE conname = 'deliverable_grants_workspace_id_format'
-  ) THEN
-    ALTER TABLE "deliverable_grants" ADD CONSTRAINT "deliverable_grants_workspace_id_format"
-      CHECK ("workspace_id" IS NULL OR "workspace_id" ~ '^wksp_[0-9a-f]{8}-[0-9a-f]{4}-7[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$');
-  END IF;
-END $$;
-
--- ── POST-ASSERTION ──────────────────────────────────────────────────────────
--- NFR1's own enforcement: exactly one nullable column added, no row moved or
--- rewritten. No "nothing guessed"/"nothing missed" checks (unlike #6203) —
--- there is no backfill for those checks to verify.
-DO $$
-DECLARE
-  before_n bigint;
-  after_n  bigint;
-BEGIN
-  SELECT n INTO before_n FROM "_6310_deliverable_grants_census";
-  SELECT count(*) INTO after_n FROM "deliverable_grants";
-
-  IF before_n <> after_n THEN
-    RAISE EXCEPTION
-      '#6310 post-assertion: row count changed across a purely additive migration (deliverable_grants % -> %)',
-      before_n, after_n;
-  END IF;
-END $$;