Auto-suspend results in JWT error: "nbf" claim timestamp check failed

It does look like it’s waking up with the right clock now…

+      0s = 1753454998s - 1753454998s
-      0s = 1753454999s - 1753454999s
+      0s = 1753455000s - 1753455000s
-      0s = 1753455001s - 1753455001s
+      0s = 1753455002s - 1753455002s
-      0s = 1753455003s - 1753455003s
-      0s = 1753455004s - 1753455004s
+      0s = 1753455005s - 1753455005s
+      0s = 1753455006s - 1753455006s
-      0s = 1753455007s - 1753455007s

(That was after being asleep for 14+ hours, too.)

Thanks for fixing details like this!