ci: the two remaining present-tense "hourly" sentences follow the 4-hourly schedule

shard-timings-refresh.yml's Save-Turbo-cache paragraph and docs-deploy.yml's
cron-collision reasoning (the 0/6/12/18 set still holds: the 4-hourly
ci/lint runs meet it at 00 and 12 only).

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AjoNWTpihGQZrTamr1vd4W

Author: claude

.github/workflows/docs-deploy.yml

@@ -57,8 +57,10 @@ on:
     # snapshot owns :07 of 02, 08, 14 and 20. Of the six six-hour sets, only
     # 0/6/12/18 and 1/7/13/19 have hours with nothing scheduled after :00; the
     # first is taken because its :00 neighbours are short (release.yml's
-    # version-pr refresh, the hourly ci/lint runs), while 07:00 starts the
-    # showcase smoke. The MINUTE is off the top of the hour for the reason every
+    # version-pr refresh, the ci/lint full runs), while 07:00 starts the
+    # showcase smoke. Since #25771 those ci/lint runs are 4-hourly
+    # (00/04/08/12/16/20 :00), so they now meet this set only at 00 and 12 and
+    # 06/18 lose that neighbour; the choice still holds and nothing moved. The MINUTE is off the top of the hour for the reason every
     # patrol here gives: scheduled runs queue behind everyone else's :00 cron.
     #
     # This job spends almost nothing of the per-repository GITHUB_TOKEN budget

.github/workflows/shard-timings-refresh.yml

@@ -88,11 +88,12 @@
 #
 # ⛔ Do NOT make ci.yml's `Save Turbo cache (main only)` step fire on `schedule`
 # as well. It is `github.event_name == 'push'` on purpose and that is now
-# load-bearing here: if the hourly run seeded the cache it restores, the next
-# hourly run would replay almost the whole workspace, the generator would refuse
-# every replayed task, and this lane would measure nothing — by construction,
-# every hour, forever. Affected-only pushes seeding a narrower cache is the
-# direction that HELPS: it leaves more real misses for the hourly run to time.
+# load-bearing here: if the scheduled run seeded the cache it restores, the next
+# scheduled run would replay almost the whole workspace, the generator would
+# refuse every replayed task, and this lane would measure nothing — by
+# construction, every 4 hours, forever. Affected-only pushes seeding a narrower
+# cache is the direction that HELPS: it leaves more real misses for the
+# scheduled run to time.
 #
 # ⚠ AND IT IS "RUNS", PLURAL, WHICH THE DOCUMENTED PROCEDURE DOES NOT SAY.
 # Measured on this lane's first live run (34083991141), when the runs it read