Self-hosted server: cron failsafe logs neither document IDs nor timestamps

Context: self-hosted / local server. The periodic cron emits lines like:

[Cron] Failsafe: marked 1 queued docs (>4h) as failed

Two forensics gaps when reconstructing an incident later:

1. No document ID — the failsafe says it terminally failed a queued document, but not which one. After an upstream-provider outage we had three of these events and had to enumerate /v3/documents/list and diff statuses to identify the affected documents.
2. No timestamps on [Cron] lines — [Workflow] lines carry [HH:MM:SS] prefixes but cron lines don't, so the events can't even be dated from the log.

Also worth surfacing: documents failed by this failsafe appear to be terminal — the very next "stuck/failed document retry" pass reports Found 0 stuck/failed documents. If that's intended, a hint in the line (e.g. "terminal, will not retry") would make operator remediation obvious at a glance.

Ask: include the doc id(s) in the failsafe line, and timestamp the cron logger the way the workflow logger already is.