Measure WEB recovery deadlines across device sleep

Author: decoder-dev

CHANGELOG.md

@@ -10,6 +10,7 @@
 - Failed TCP endpoints share monotonic cooldown and a single recovery probe across contexts; duplicate connects reuse the existing connection, and closed interfaces release read buffers.
 - WEB resume requests coalesce per carrier. Stale callbacks cannot restart disabled/replaced profiles; duplicate failures count once and short-lived sessions retain backoff history.
 - Foreground events join an existing WEB bootstrap and respect its cooldown instead of superseding it; queued obsolete starts exit before opening a new session.
+- WEB elapsed-time checks use a continuous monotonic clock, including device sleep, for background dwell, session health and cooldown.
 - Removed the global WebSocket fallback cancellation and the mid-transaction state replay timeout. State replay finishes atomically instead of committing a prefix and resetting synchronization.
 - Stale PTS snapshots retry difference synchronization without a full account reset. WebSocket dial requests are one-shot across fallback gaps and use a monotonic fallback clock.
 - Fetch completion is logged once at queue removal, with location and episode, rather than again in the result observer. TCP attempts have IDs for correlation and log the effective connection deadline.

submodules/WebProxyTransport/Sources/WebProxyManager.swift

@@ -1,5 +1,13 @@
 import Foundation
 import Network
+import Darwin
+
+// Monotonic elapsed time including device sleep. systemUptime excludes sleep and
+// could make an overnight suspension look like a brief foreground flicker.
+// https://developer.apple.com/documentation/kernel/1646199-mach_continuous_time
+private func webProxyContinuousTime() -> Double {
+    return Double(clock_gettime_nsec_np(CLOCK_MONOTONIC_RAW)) / 1_000_000_000.0
+}
 
 public struct WebProxyConfiguration: Equatable {
     public let hostname: String