chore(cutover): GitHub heartbeat schedule OFF — the mirror was billing us to watch ourselves #5520
ccantynzAI Reviewcommented 10d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 10d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
The GitHub budget root cause, removed
The heartbeat's 5-minute cron = ~8,600 Actions minutes/month on a private repo, which is billed — the workflow keeping us "safe" on GitHub was the thing charging us to stay. This removes the schedule (manual
workflow_dispatchstays as break-glass until Phase 4 archives the repo).Replacement is owned infrastructure that already exists:
jarvis-watchdogon the Vapron box probes gluecron.com every 5 minutes today. The Vapron-side briefing asks their agent to add two lines to it: POST results to/api/heartbeat/report(same token/shape the GitHub workflow used) and ping the healthchecks.io dead-man. Zero external spend, and the alerting is strictly better than what GitHub gave us — this week the GitHub heartbeat detected three outages and paged no one.Effective when the mirror is next pushed — the schedule lives in GitHub's copy. The owner's next
git push github canonical-main:mainstops the spend.🤖 Generated with Claude Code