diff --git a/.cursor/commands/pre-push.md b/.cursor/commands/pre-push.md
index 8e36bbd31..9e452ecad 100644
--- a/.cursor/commands/pre-push.md
+++ b/.cursor/commands/pre-push.md
@@ -1 +1 @@
-Please compare `origin/dev` to `origin/main` (feel free to check out the dev branch if needed) and ensure that all migrations are backwards compatible. In what ways could breakage occur? Report the result to me in detail. Anything else that's scary that could occur, or that we should think about while migrating?
+Please compare `origin/dev` to `origin/main` (feel free to check out the dev branch if needed) and ensure that all migrations are backwards compatible. In what ways (DB, API, or otherwise) could breakage occur? Report the result to me in detail. Anything else that's scary that could occur, or that we should think about while migrating? Should we migrate first and upgrade the code second, or the other way around? Are rollbacks safe? Think hard.
diff --git a/apps/backend/prisma/migrations/20260507000000_add_project_user_last_active_at_idx/migration.sql b/apps/backend/prisma/migrations/20260507000000_add_project_user_last_active_at_idx/migration.sql
index b45ed0585..6bc5308a6 100644
--- a/apps/backend/prisma/migrations/20260507000000_add_project_user_last_active_at_idx/migration.sql
+++ b/apps/backend/prisma/migrations/20260507000000_add_project_user_last_active_at_idx/migration.sql
@@ -2,4 +2,4 @@
 -- SINGLE_STATEMENT_SENTINEL
 -- RUN_OUTSIDE_TRANSACTION_SENTINEL
 CREATE INDEX CONCURRENTLY IF NOT EXISTS "ProjectUser_lastActiveAt"
-  ON "ProjectUser"("tenancyId", "isAnonymous", "lastActiveAt");
+  ON /* SCHEMA_NAME_SENTINEL */."ProjectUser"("tenancyId", "isAnonymous", "lastActiveAt");