@adaptware/eagles-db 0.5.46 → 0.5.48

package/prisma/schema/migrations/20260821120000_drop_billing_product_and_mock_licensing/migration.sql

@@ -1,38 +0,0 @@
--- Preserve all billing_transactions rows.
--- Rename product identity to an opaque purchase_reference (values unchanged).
--- Drop catalog tables and mock licensing column only.
-
--- 1. Drop FK + rename product identity column
-ALTER TABLE "billing_transactions" DROP CONSTRAINT IF EXISTS "billing_transactions_product_id_fkey";
-ALTER TABLE "billing_transactions" RENAME COLUMN "product_id" TO "purchase_reference";
-DROP INDEX IF EXISTS "billing_transactions_product_id_idx";
-CREATE INDEX "billing_transactions_purchase_reference_idx" ON "billing_transactions"("purchase_reference");
-
--- 2. Drop mock licensing columns/indexes
-DROP INDEX IF EXISTS "billing_transactions_licensing_status_idx";
-ALTER TABLE "billing_transactions" DROP COLUMN IF EXISTS "licensing_status";
-
--- 3. Remap mock licensing failure category, then rebuild enum without LICENSING
-UPDATE "billing_transactions"
-SET "failure_category" = 'INTERNAL'::"BillingTransactionFailureCategory"
-WHERE "failure_category" = 'LICENSING'::"BillingTransactionFailureCategory";
-
-CREATE TYPE "BillingTransactionFailureCategory_new" AS ENUM ('RAZORPAY_ORDER', 'RAZORPAY_PAYMENT', 'REFUND', 'INTERNAL');
-
-ALTER TABLE "billing_transactions"
-  ALTER COLUMN "failure_category" TYPE "BillingTransactionFailureCategory_new"
-  USING ("failure_category"::text::"BillingTransactionFailureCategory_new");
-
-DROP TYPE "BillingTransactionFailureCategory";
-ALTER TYPE "BillingTransactionFailureCategory_new" RENAME TO "BillingTransactionFailureCategory";
-
--- 4. Drop catalog tables (order: prices → products)
-DROP TABLE IF EXISTS "billing_product_prices";
-DROP TABLE IF EXISTS "billing_products";
-
--- 5. Drop catalog FX table
-DROP TABLE IF EXISTS "billing_exchange_rates";
-
--- 6. Drop unused enums
-DROP TYPE IF EXISTS "BillingLicensingStatus";
-DROP TYPE IF EXISTS "BillingProductType";

package/prisma/schema/migrations/20260824120000_billing_transaction_purchase_display_name/migration.sql

@@ -1,2 +0,0 @@
--- AlterTable
-ALTER TABLE "billing_transactions" ADD COLUMN IF NOT EXISTS "purchase_display_name" TEXT;

package/prisma/schema/migrations/20260831120000_user_communication_email/migration.sql

@@ -1,6 +0,0 @@
--- Candidate contact email (separate from login `email`).
-ALTER TABLE "User" ADD COLUMN IF NOT EXISTS "communication_email" TEXT;
-
-UPDATE "User"
-SET "communication_email" = "email"
-WHERE "communication_email" IS NULL;

package/prisma/schema/migrations/20260901143000_assessment_question_bank_state/migration.sql

@@ -1,15 +0,0 @@
--- Question bank: category + stable plan identity on reusable Question rows.
-CREATE TYPE "QuestionCategory" AS ENUM (
-  'GENERAL_APTITUDE',
-  'DOMAIN_APTITUDE',
-  'DOMAIN_KNOWLEDGE'
-);
-
-ALTER TABLE "Question" ADD COLUMN IF NOT EXISTS "category" "QuestionCategory";
-ALTER TABLE "Question" ADD COLUMN IF NOT EXISTS "plan_index" INTEGER;
-
-CREATE INDEX IF NOT EXISTS "Question_assessment_library_id_candidate_id_plan_index_idx"
-  ON "Question" ("assessment_library_id", "candidate_id", "plan_index");
-
--- Incremental bank generation state on the reusable AssessmentLibrary.
-ALTER TABLE "AssessmentLibrary" ADD COLUMN IF NOT EXISTS "generation_state" JSONB;

package/prisma/schema/migrations/20260902120000_question_category_two_values/migration.sql

@@ -1,16 +0,0 @@
--- Collapse QuestionCategory to GENERAL_APTITUDE + DOMAIN_KNOWLEDGE (drop DOMAIN_APTITUDE).
-UPDATE "Question"
-SET category = 'DOMAIN_KNOWLEDGE'
-WHERE category = 'DOMAIN_APTITUDE';
-
-CREATE TYPE "QuestionCategory_new" AS ENUM (
-  'GENERAL_APTITUDE',
-  'DOMAIN_KNOWLEDGE'
-);
-
-ALTER TABLE "Question"
-  ALTER COLUMN "category" TYPE "QuestionCategory_new"
-  USING ("category"::text::"QuestionCategory_new");
-
-DROP TYPE "QuestionCategory";
-ALTER TYPE "QuestionCategory_new" RENAME TO "QuestionCategory";

package/prisma/schema/migrations/20260902143000_question_bank_item_key/migration.sql

@@ -1,17 +0,0 @@
--- Replace plan_index on Question with deterministic bank_item_key for idempotent persist.
-
-ALTER TABLE "Question" ADD COLUMN IF NOT EXISTS "bank_item_key" TEXT;
-
-UPDATE "Question"
-SET "bank_item_key" = 'legacy:' || "assessment_library_id" || ':' || "plan_index"::text
-WHERE "candidate_id" IS NULL
-  AND "plan_index" IS NOT NULL
-  AND "bank_item_key" IS NULL
-  AND "assessment_library_id" IS NOT NULL;
-
-DROP INDEX IF EXISTS "Question_assessment_library_id_candidate_id_plan_index_idx";
-
-ALTER TABLE "Question" DROP COLUMN IF EXISTS "plan_index";
-
-CREATE UNIQUE INDEX IF NOT EXISTS "Question_assessment_library_id_bank_item_key_key"
-  ON "Question" ("assessment_library_id", "bank_item_key");

package/prisma/schema/migrations/20260903120000_split_round_type_assessment/migration.sql

@@ -1,9 +0,0 @@
--- Add explicit MCQ round types for NEW aptitude / domain knowledge tests.
---
--- Keep RoundType.ASSESSMENT for backward compatibility.
--- Do NOT rewrite EvaluationPlan, OngoingEvaluation, or analytics rows.
--- Do NOT drop or recreate the enum.
--- Do NOT touch ActivityEventType.ASSESSMENT_* or ActivityEntityType.ASSESSMENT.
-
-ALTER TYPE "RoundType" ADD VALUE IF NOT EXISTS 'GENERAL_APTITUDE_ASSESSMENT';
-ALTER TYPE "RoundType" ADD VALUE IF NOT EXISTS 'DOMAIN_KNOWLEDGE_ASSESSMENT';

package/prisma/schema/migrations/20260904110000_restore_round_type_assessment_enum/migration.sql

@@ -1,5 +0,0 @@
--- Restore legacy RoundType.ASSESSMENT when an older enum swap dropped it.
--- Must run in its own migration: PostgreSQL requires new enum values to be
--- committed before they can be assigned to rows (see revert migration next).
-
-ALTER TYPE "RoundType" ADD VALUE IF NOT EXISTS 'ASSESSMENT';

package/prisma/schema/migrations/20260904120000_revert_wrong_split_assessment_round_types/migration.sql

@@ -1,42 +0,0 @@
--- Revert evaluation plans that were incorrectly stored as split MCQ round types
--- back to legacy ASSESSMENT.
---
--- Does NOT change rows already on ASSESSMENT.
--- Keeps intentional new GENERAL_APTITUDE_ASSESSMENT / DOMAIN_KNOWLEDGE_ASSESSMENT
--- rounds when title or details show an explicit split-type configuration.
---
--- Requires 20260904110000_restore_round_type_assessment_enum to run first so
--- RoundType.ASSESSMENT exists (some DBs lost it during an earlier bad enum swap).
-
-UPDATE "EvaluationPlan"
-SET type_of_round = 'ASSESSMENT'
-WHERE is_active = true
-  AND type_of_round IN ('GENERAL_APTITUDE_ASSESSMENT', 'DOMAIN_KNOWLEDGE_ASSESSMENT')
-  AND (
-    (
-      COALESCE((details #>> '{question_category_distribution,GENERAL_APTITUDE}')::int, 0) > 0
-      AND COALESCE((details #>> '{question_category_distribution,DOMAIN_KNOWLEDGE}')::int, 0) > 0
-    )
-    OR (
-      upper(COALESCE(details->>'primary_question_category', '')) = 'GENERAL_APTITUDE'
-      AND type_of_round = 'DOMAIN_KNOWLEDGE_ASSESSMENT'
-    )
-    OR (
-      upper(COALESCE(details->>'primary_question_category', '')) = 'DOMAIN_KNOWLEDGE'
-      AND type_of_round = 'GENERAL_APTITUDE_ASSESSMENT'
-    )
-    OR (
-      type_of_round = 'DOMAIN_KNOWLEDGE_ASSESSMENT'
-      AND lower(title) !~* '(domain knowledge|domain test|backend domain|frontend domain|\mdomain\M)'
-      AND COALESCE((details #>> '{question_category_distribution,GENERAL_APTITUDE}')::int, 0) = 0
-      AND COALESCE((details #>> '{question_category_distribution,DOMAIN_KNOWLEDGE}')::int, 0) = 0
-      AND NULLIF(trim(COALESCE(details->>'primary_question_category', '')), '') IS NULL
-    )
-    OR (
-      type_of_round = 'GENERAL_APTITUDE_ASSESSMENT'
-      AND lower(title) !~* '(aptitude|general aptitude|numerical|verbal reasoning|logical reasoning)'
-      AND COALESCE((details #>> '{question_category_distribution,GENERAL_APTITUDE}')::int, 0) = 0
-      AND COALESCE((details #>> '{question_category_distribution,DOMAIN_KNOWLEDGE}')::int, 0) = 0
-      AND NULLIF(trim(COALESCE(details->>'primary_question_category', '')), '') IS NULL
-    )
-  );

package/prisma/sql/add_user_deleted_at.sql

@@ -1,8 +0,0 @@
--- Add soft-delete timestamp for team member removal (distinct from is_active deactivate).
-ALTER TABLE "public"."User"
-ADD COLUMN IF NOT EXISTS "deleted_at" TIMESTAMP(3);
-
--- Optional: allow re-inviting the same email after soft delete (PostgreSQL partial unique index).
--- Run only if product requires re-invite while tombstone row exists.
--- DROP INDEX IF EXISTS "User_email_key";
--- CREATE UNIQUE INDEX "User_email_active_key" ON "public"."User" ("email") WHERE "deleted_at" IS NULL;