(fix) use production Prisma migrations during deploy

[Ammaar-Alam]

Summary

• run Prisma migrations with the production-safe deploy command
• preserve the existing development migration command for local workflows

Context

The production database contains an applied historical migration that is no longer present in the repository. The deployment script used prisma migrate dev, which treated that history difference as drift and requested a schema reset in the non-interactive deployment job. Prisma migrate deploy accepts the current applied history and safely applies only pending committed migrations.

Validation

• production Prisma migration status reports the schema is up to date
• the exact patched command completed against production with no pending migrations
• backend TypeScript build passed
• frontend production build passed
• deployment shell syntax and diff checks passed

(PR written by Codex)

[Copilot]

Pull request overview

This PR updates the production deployment script to run Prisma migrations using the production-safe prisma migrate deploy flow, avoiding drift/reset behavior caused by prisma migrate dev in non-interactive deploy jobs.

Changes:

• Replaces the deployment-time migration step from pnpm db:migrate (dev-oriented) to prisma migrate deploy executed in the tigerspot-server workspace.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.