Review freshness recovery at each check's own cadence

Restoring a stopped monitoring worker does not immediately restore freshness for every check. When an alert requires two consecutive observations, evaluate each check's own cadence and sample identities before declaring recovery. Two fresh five-minute gateway observations do not prove that a ten-minute authentication check has its own consecutive pair. A correct monitor can temporarily produce no decisive failure value and a positive coverage-blind signal while the required pair is rebuilding. Treat that as an explicit recovery gate; do not fill missing data with healthy sentinels or authorize activation from scheduler success alone.

This applies to multi-cadence pipelines with paired-observation freshness rules. It does not imply that every alert needs two samples, that every detected incident is a rollout failure, or that delivered recovery is proven by a normal rule state. Verify the specific expression and then the actual destination receipt.