[daveosterjr]

What changed

The timed catch-up for this repository's two Alma trackers (staging work and production builds) runs once a day instead of every 10 minutes: 08:17 UTC for staging and 08:43 UTC for production. Those are the schedules Alma's shared tracker generator writes, and the ones Website and Next already use.

• Staging pushes report at once. This repository's staging tracker has no deployment to follow, so it now also runs on every push to staging, the way Next and Mobile report. Before, the 10-minute timer was its only prompt.
• Unchanged: the runs right after each deployment, and running a tracker by hand.
• Why: each run starts a fresh Google Cloud CI machine. Across five repositories that was about 1,000 machine starts a day for a catch-up the staging intake and production release guides say should run daily, and the regular bursts kept idle CI machines up around the clock.
• When it saves: GitHub runs schedules from the default branch, so this takes effect once it reaches master with the next release.

Proof

Both workflow files parse, and each keeps its daily schedule, its manual run and its deployment or staging-push trigger.

Ticket: WORK-17632

🤖 Generated with Claude Code