fix: use in-memory startedAt for cron job log to survive DB restore

The auto-import wipes the database, destroying the cronJobLog record
created at the start of the job. Now duration is calculated from a
local variable instead of querying the DB, and if the record is gone
a fresh log entry is created in the restored database.

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

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

@@ -1,16 +1,16 @@
 import * as z from 'zod';
-import { Prisma } from '../../../generated/prisma';
-import Decimal from 'decimal.js';
-
+import type { Prisma } from '../../../generated/prisma';
 
 import { DecimalJSLikeSchema, isValidDecimalInput } from '../../helpers/decimal-helpers';
+
+import Decimal from "decimal.js";
 const makeSchema = () => z.object({
   id: z.number().int().optional(),
   totalCollection: z.union([
   z.number(),
   z.string(),
   z.instanceof(Decimal),
-  z.instanceof(Prisma.Decimal),
+  z.instanceof(Decimal),
   DecimalJSLikeSchema,
 ]).refine((v) => isValidDecimalInput(v), {
   message: "Field 'totalCollection' must be a Decimal",
@@ -19,7 +19,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 'commissionAmount' must be a Decimal",