Reduce push-to-start apns-expiration from stale date to 10 minutes

8 hours is too generous — delivering a start notification with hours-old
glucose data is worse than not starting at all. 10 minutes is long enough
to survive a brief connectivity gap while the reading is still meaningful.

https://claude.ai/code/session_01GJZERMhqLmEy8p4cpVX53q

Author: claude

LoopFollow/LiveActivity/APNSClient.swift

@@ -142,9 +142,11 @@ class APNSClient {
         request.setValue("\(bundleID).push-type.liveactivity", forHTTPHeaderField: "apns-topic")
         request.setValue("liveactivity", forHTTPHeaderField: "apns-push-type")
         request.setValue("10", forHTTPHeaderField: "apns-priority")
-        // Expire at the stale date rather than immediately so APNs can deliver
-        // the start notification after a brief connectivity gap.
-        request.setValue("\(Int(staleDate.timeIntervalSince1970))", forHTTPHeaderField: "apns-expiration")
+        // 10-minute expiry — long enough to survive a brief connectivity gap
+        // while the glucose reading in the payload is still clinically meaningful.
+        // The stale date (8 h) is too generous: delivering a start with hours-old
+        // glucose data is worse than not starting at all.
+        request.setValue("\(Int(Date().timeIntervalSince1970) + 10 * 60)", forHTTPHeaderField: "apns-expiration")
         // Collapse key prevents duplicate LA creation if two sends race (e.g., a
         // refresh tick and a user-initiated restart overlap).
         request.setValue("\(bundleID).la.start", forHTTPHeaderField: "apns-collapse-id")