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>

.turbo/preferences/tui.json

@@ -1,4 +1,4 @@
 {
   "is_task_list_visible": true,
-  "active_task": "backend#dev"
+  "active_task": "frontend#dev"
 }