|Options Edge|DEPLOYED
Wire the health check to an actual schedule
/api/cron/health has existed since 2026-03-28 (commit d6be16c) but nothing ever called it — no GitHub schedule, no entry in the server crontab. It checks Supabase auth, chain-capture freshness (<48h), and paper-trade-logger freshness,
/api/cron/health has existed since 2026-03-28 (commit d6be16c) but nothing ever called it — no GitHub schedule, no entry in the server crontab. It checks Supabase auth, chain-capture freshness (<48h), and paper-trade-logger freshness, so it would have caught the outage within 48 hours of it starting. It ran zero times in 4.5 months.
Runs every 6h and fails the job (not just the Discord embed) so a broken health check cannot itself pass silently.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Files Changed
Commit:37a4783