ci: keep the satellite frame cache for the window plus one hour

A round pulls HOURS + 1 hours of frames, so eight hours covers the
six-hour window with an hour of slack (twenty-six for the daily Meteosat
window); the scans stay archived at the agencies.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: ringsaturn

.github/workflows/publish-goeseast.yml

@@ -108,8 +108,8 @@ jobs:
       # A warped frame is 3-6 MB, seven variables share a slot and a day is
       # 144 slots, so a day of the cache is some 4.5 GB. The viewer plays a
       # six-hour window and the agency archives the scans, so the mirror
-      # keeps that window and a little slack: a round pulls HOURS + 1 hours.
-      FRAMES_KEEP_HOURS: "12"
+      # keeps that window and an hour of slack: a round pulls HOURS + 1 hours.
+      FRAMES_KEEP_HOURS: "8"
       ONCE: ${{ !inputs.loop }}
       ROUND_MINUTES: ${{ inputs.round_minutes || '5' }}
       # For a looping dispatch: run past the hour, and hand over to the next

.github/workflows/publish-goeswest.yml

@@ -108,8 +108,8 @@ jobs:
       # A warped frame is 3-6 MB, seven variables share a slot and a day is
       # 144 slots, so a day of the cache is some 4.5 GB. The viewer plays a
       # six-hour window and the agency archives the scans, so the mirror
-      # keeps that window and a little slack: a round pulls HOURS + 1 hours.
-      FRAMES_KEEP_HOURS: "12"
+      # keeps that window and an hour of slack: a round pulls HOURS + 1 hours.
+      FRAMES_KEEP_HOURS: "8"
       ONCE: ${{ !inputs.loop }}
       ROUND_MINUTES: ${{ inputs.round_minutes || '5' }}
       # For a looping dispatch: run past the hour, and hand over to the next

.github/workflows/publish-himawari.yml

@@ -108,8 +108,8 @@ jobs:
       # A warped frame is 3-6 MB, seven variables share a slot and a day is
       # 144 slots, so a day of the cache is some 4.5 GB. The viewer plays a
       # six-hour window and the agency archives the scans, so the mirror
-      # keeps that window and a little slack: a round pulls HOURS + 1 hours.
-      FRAMES_KEEP_HOURS: "12"
+      # keeps that window and an hour of slack: a round pulls HOURS + 1 hours.
+      FRAMES_KEEP_HOURS: "8"
       ONCE: ${{ !inputs.loop }}
       ROUND_MINUTES: ${{ inputs.round_minutes || '5' }}
       # For a looping dispatch: run past the hour, and hand over to the next

.github/workflows/publish-meteosat.yml

@@ -111,8 +111,8 @@ jobs:
       FRAME_CACHE: "true"
       # A warped frame is 3-6 MB and a day is 24 slots of six variables. The
       # viewer plays a day and the store archives the scans, so the mirror
-      # keeps that window and a little slack: a round pulls HOURS + 1 hours.
-      FRAMES_KEEP_HOURS: "30"
+      # keeps that window and an hour of slack: a round pulls HOURS + 1 hours.
+      FRAMES_KEEP_HOURS: "26"
       ONCE: ${{ !inputs.loop }}
       ROUND_MINUTES: ${{ inputs.round_minutes || '5' }}
       # For a looping dispatch: run past the hour, and hand over to the next

CLAUDE.md

@@ -380,7 +380,7 @@ model starts here; the frontend mirror is `FORECAST_MODELS` in
   outside the grid is refused, since a blank warp is also a lost
   projection), `assemble.py` caches the
   frame (`data/raw/himawari-frames/<variable>/*.tif`, mirrored like the JMA
-  frames but kept twelve hours, `FRAMES_KEEP_HOURS`, since the agencies
+  frames but kept eight hours, `FRAMES_KEEP_HOURS`, since the agencies
   archive the scans and a day of seven variables is ~4.5 GB) and writes the window series with `gdal_translate -of netCDF`
   through a VRT carrying `NETCDF_DIM_*` metadata, `fetch.py` runs a window
   (`fetch.py::_fetch_satellite_run` in the top-level module dispatches on

README.md

@@ -589,7 +589,7 @@ secret and read in process with the `R2_*` credentials
 dataset bucket's token cannot read it, else that token), with the `cma`
 dependency group synced. The Himawari job is the JMA shape with a
 frame cache of warped GeoTIFFs (`data/raw/himawari-frames/<variable>/`,
-one directory per channel and per Dust RGB gun, kept twelve hours on the
+one directory per channel and per Dust RGB gun, kept eight hours on the
 bucket — the window plus slack, since NOAA archives the scans and a day of
 the cache is some 4.5 GB; `FRAMES_KEEP_HOURS`), a six-hour window
 (`HOURS=6`), the `satellite` dependency group