Configuration

CLI flags

Flag	Default	Meaning
`-d, --days`	7	window to inspect (1–90)
`-w, --workflow`	all	only this workflow: file name (`nightly.yml` or `nightly`), path, display name or id; repeatable
`-f, --format`	text	`text`, `json`, `markdown`
`--org`		org-wide scan (same as `cronlag org <org>`)
`--fail-on`	never	`dropped`: exit 1 on DROPPING / NOT FIRING / DISABLED / INVALID; `late`: also LATE
`--late`	1h	lag above which a run is "very late" (also the LATE verdict threshold for the median)
`--on-time`	10m	lag still counted as on time
`--lite`	off	skip the workflow-file history lookup (fewer API calls; cron changes in the window are then not detected)
`--grace`	15m	catchup: how long after a slot before it counts as missed
`--dispatch`	off	catchup: actually dispatch
`--tz`, `-n`	UTC, 5	explain: timezone and number of fire times
`--token`	env / gh	GitHub token
`--no-color`	auto	plain output (`NO_COLOR` and `FORCE_COLOR` are honored)

Durations accept s, m, h, d (90m, 2h).

A run is attributed to a slot at most 24 hours after it (GitHub drops scheduled events queued longer).
Runs created up to 2 minutes before a slot count for it (clock skew).
A slot with no run is missed once it is 24h old or a later slot already got its run; until then it is overdue.