ReliabilityOpt-in

A cron that did not fire is still a failure

Cron triggers know when they should have fired. When one is late past its grace period, or a run has hung longer than its timeout, you hear about it in-app, in Slack, or through a signed webhook. Jobs that run elsewhere (a nightly backup, a data pipeline), get a heartbeat URL: hit it at start and finish and e-volv tracks them the same way.

Opt in: requires the monitoring.scheduled flag

• Lateness and hung-run detection on every cron trigger
• Heartbeat monitors for jobs outside e-volv: start, ok, fail
• Late-runs tile on the dashboard and a monitors page
• Alerts to notifications, Slack, and HMAC-signed webhooks (Opt in, Slack app beta and alerts.rules flag)

1. Alert rules & metricsOpt-inThreshold rules on success rate, tool failures, failed runs, and error-budget burn; a Prometheus endpoint for the rest.
2. SLOs & error budgetsOpt-in"95% of Code Review runs succeed over 30 days", the budget left, multi-window burn rate, and a README badge.