Describe the strict page clock as the nearest 18:30 UTC

docs/CURRENT-STATE.md

@@ -417,7 +417,8 @@ one application, and only the globe-bound parts move to the next engine.
   and switch scenario under a deny-by-default network policy, with free map
   tiles from a disk cache and a trap that fails any read of Cesium before it
   has loaded. Every catalog layer must be asserted on both engines.
-  Page clocks start at `2026-11-03T18:30:00Z` unless a scenario supplies
+  Page clocks start at the 18:30 UTC nearest to the real time, so the sun is
+  up over the test cities whenever the run happens, unless a scenario supplies
   `time` (an ISO instant or `'real'`); `QA_EXIT_DIAGNOSTICS=1` preserves
   shutdown resources and prints them five seconds after completion.
   A timed-out scenario with passing evidence is `hung`; non-passing scenarios

scripts/qa-all-layer-switches.mjs

@@ -40,7 +40,8 @@ import {
 // scenario. A timed-out pass is hung; a retry that passes is flaky and does
 // not fail the run. QA_EXIT_DIAGNOSTICS=1 preserves Chrome resources and
 // reports them five seconds after strict completion instead of forcing exit.
-// Pages start at 2026-11-03T18:30:00Z unless createStrict's time overrides it.
+// Pages start at the 18:30 UTC nearest to the real time unless createStrict's
+// time overrides it.
 //
 //   node scripts/qa-all-layer-switches.mjs http://127.0.0.1:4208 <output>
 //     [--serve[=<commit>]]  build <commit> (default HEAD) keyless in a clean