vhaudiquet
5e9952ac6d
The diagnostics page showed the status job "waiting" while its runs and the report-now kick died without a trace: any exception before the first log line was invisible, indistinguishable from a job that never starts. Every worker now wraps its run — a crash logs its type, message, and first frame; a cancellation logs as such and rethrows. The screen gains the report-now kick's own row (a one-time job's empty list is "never run", not an error) and the tap lands in the log, so the next stale-row mystery names its cause instead of hiding it.