fix: auto-migrate after DB restore and force re-login

- After importing a backup, run prisma migrate deploy so any schema
  migrations the backup is missing are applied automatically. This
  prevents pages from failing due to missing tables/columns when the
  backup was taken on an older version of the app.
- Force logout and redirect to login after a successful restore so the
  JWT is refreshed against the restored database (prevents userId
  mismatch causing user-scoped queries to return empty results).
- Fix getTotalPatientCount() in /status route to pass userId so it
  counts only the current user's patients instead of all patients.
- Add prisma.$connect() after $disconnect() to ensure a clean reconnect.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

packages/db/shared/schemas/objects/ServiceLineTransactionCreateManyPaymentInput.schema.ts

@@ -1,9 +1,10 @@
 import * as z from 'zod';
-import { Prisma } from '../../../generated/prisma';
-import Decimal from 'decimal.js';
+import type { Prisma } from '../../../generated/prisma';
 import { PaymentMethodSchema } from '../enums/PaymentMethod.schema'
 
 import { DecimalJSLikeSchema, isValidDecimalInput } from '../../helpers/decimal-helpers';
+
+import Decimal from "decimal.js";
 const makeSchema = () => z.object({
   id: z.number().int().optional(),
   serviceLineId: z.number().int(),
@@ -12,7 +13,7 @@ const makeSchema = () => z.object({
   z.number(),
   z.string(),
   z.instanceof(Decimal),
-  z.instanceof(Prisma.Decimal),
+  z.instanceof(Decimal),
   DecimalJSLikeSchema,
 ]).refine((v) => isValidDecimalInput(v), {
   message: "Field 'paidAmount' must be a Decimal",
@@ -21,7 +22,7 @@ const makeSchema = () => z.object({
   z.number(),
   z.string(),
   z.instanceof(Decimal),
-  z.instanceof(Prisma.Decimal),
+  z.instanceof(Decimal),
   DecimalJSLikeSchema,
 ]).refine((v) => isValidDecimalInput(v), {
   message: "Field 'adjustedAmount' must be a Decimal",