Scheduled backup does not fire on wake from sleep when interval has elapsed

[PLK2]

Describe the bug

When the laptop lid is closed and the system sleeps, the scheduled backup (understandably) does not run. However, when the lid is reopened and the system wakes, no backup fires even if the configured interval has already passed. The next backup only runs after another full interval elapses from the wake time.

Expected behavior

On wake from sleep, if the time since the last successful backup exceeds the configured interval, a backup should trigger promptly (possibly with a brief delay to allow network reconnection).

Actual behavior

No backup fires on wake. The daemon appears to restart the full interval timer from the moment of wake rather than checking whether the interval has already been exceeded.

Config (relevant yaml section)

schedule:
  enabled: true
  every: "2h"
  on_startup: true

Environment

OS: macOS Tahoe 26.3.1
Vykar version: 0.12.13

Possible fix

???

[m3nu]

Reproduced and fixed in 9276384.

Root cause: Both the GUI and daemon schedulers stored next_run as std::time::Instant. On macOS (and Linux) monotonic clocks freeze during system sleep, so the crossbeam_channel::select! timeout (GUI) / thread::sleep polling loop (daemon) kept waiting as if no time had passed on wake — the full configured interval effectively restarted. on_startup: true did not help: it is evaluated only at process startup, and the GUI process is suspended rather than restarted across sleep on macOS.

Fix: Track next_run as SystemTime (wall clock) and cap each wait at 60s. After wake, SystemTime reflects real elapsed time, so next_run is already in the past and the backup fires immediately. The 60s cap bounds post-wake latency regardless of how large the configured interval is, without requiring platform-specific wake notifications (IOKit/logind).

Will ship in the next release.