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/generated/prisma/index-browser.js

@@ -125,7 +125,9 @@ exports.Prisma.UserScalarFieldEnum = {
   username: 'username',
   password: 'password',
   autoBackupEnabled: 'autoBackupEnabled',
-  usbBackupEnabled: 'usbBackupEnabled'
+  autoBackupHour: 'autoBackupHour',
+  usbBackupEnabled: 'usbBackupEnabled',
+  usbBackupHour: 'usbBackupHour'
 };
 
 exports.Prisma.PatientScalarFieldEnum = {

packages/db/generated/prisma/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "prisma-client-a8d4bc304c12e798930e60b1098ae5812d0c1102c722be6392ad354a9e581c9a",
+  "name": "prisma-client-255925208cd2ae4e7680931248b79c62d4ac5e35e42b5e687d7201ee1e27106d",
   "main": "index.js",
   "types": "index.d.ts",
   "browser": "default.js",

packages/db/generated/prisma/schema.prisma

@@ -23,7 +23,9 @@ model User {
   username             String                @unique
   password             String
   autoBackupEnabled    Boolean               @default(true)
+  autoBackupHour       Int                   @default(20)
   usbBackupEnabled     Boolean               @default(false)
+  usbBackupHour        Int                   @default(21)
   patients             Patient[]
   appointments         Appointment[]
   staff                Staff[]