fix(scheduler): use context.Background() in panic-recovery defer UPDATE (F1089)

[molecule-ai]

Duplicate of staging fix — close this PR.

F1089 (context.Background() in scheduler panic-recovery defer) is already on staging via commit d87af75 (/pull/1233). PR #1241 targets main with the same 18-line change to scheduler.go, which will conflict when promoted. The fix on main should come via the normal staging→main promotion flow, not a separate backport PR.

Flagged for author review.

[molecule-ai]

PR Review: #1241 — fix(scheduler): use context.Background() in panic-recovery defer UPDATE (F1089)

Quality: HIGH — improvement over prior F1089 PRs. LGTM.

Improvement over prior F1089 PRs

This PR includes the same core fix (ExecContext(ctx, ...) → ExecContext(context.Background(), ...)) as PR #1211, but with two key additions:

1. Error logging on panic-recovery UPDATE failure:

   if _, execErr := db.DB.ExecContext(context.Background(), ...); execErr != nil {
       log.Printf("Scheduler: panic-recovery next_run_at UPDATE failed for schedule %s: %v", s2.ID, execErr)
   }

   This is a meaningful improvement. Previously the ExecContext error was silently swallowed. Now operators get visibility when the panic-recovery UPDATE itself fails (e.g., DB connection lost during panic). The schedule will still re-fire — but at least the failure is logged.

2. Panic logging enhancement: Both panic handlers now log the panic value and schedule name before the recovery UPDATE:

   log.Printf("Scheduler: PANIC firing '%s' on workspace %s — recovered: %v", ...)

   This gives operators actionable context — they can see WHICH schedule panicked and on WHICH workspace.

Note on fmt issue

PR #1211 had a Go formatter issue (extra indentation on closing }). This PR appears to use the correct if _, execErr := ...; execErr != nil { ... } pattern which avoids that problem.

Non-blocking

No tests — but this is a panic-recovery path that's hard to unit test. The pattern is simple and the logging is the key improvement. CI will validate.

Overall: Better than the prior F1089 PRs. The error logging is the right call. LGTM.