batch-health

Batch health auditing cross-references scheduled enabled skills in aeon.yml against actual skill-runs output to detect silent misses, classify severity as OK/WARN/OUTAGE, and optionally create batch-outage issues.

Batch window validation filters enabled skills expected to run in the 06:00–07:30 UTC window, fetches actual execution logs, and flags any missing skills as warnings or outages based on threshold exceedance.

Yes, checking batch health requires access to aeon.yml to build the expected-run list and memory logs or skill-runs output to verify actual executions, enabling accurate cross-referencing and outage detection.

Yes, you can automatically create batch-outage issues when the cross-reference of expected versus actual scheduled runs identifies missing skills that exceed defined severity thresholds.

The best way to monitor daily post-batch execution status is running an automated audit each morning that compares expected scheduled skills against actual runs, maintaining a persistent log and notification workflow for operators.

Scheduled enabled skills may not appear in skill-runs output if they silently missed the 06:00–07:30 UTC batch window, which the audit detects by cross-referencing aeon.yml expectations against fallback memory logs.