Lite accepts collector cadences above the delta gap policy, fabricating permanent quiet #3532

Any delta-family collector scheduled above 60 minutes exceeds the shared 3600s delta gap policy on every cycle, so every cycle takes the reset branch and emits zero deltas, forever. The product goes green precisely because it stopped measuring.

Evidence (verified): Lite/Services/ScheduleManager.cs:144-147 assigns FrequencyMinutes raw, no validation; every delta collector passes DefaultMaxGapSeconds = 3600 (CollectorDeltaCalculator.cs:42).

Scenario: set wait_stats to 90 minutes. Every delta is (0,0), the waits chart flatlines at zero, wait facts vanish (the fact collector filters > 0), baselines fill with zeros, no error anywhere.

Fix: clamp or refuse cadences above the gap policy for delta-family collectors in ScheduleManager (and verify Darling's schedule-editing path against the same bound); at minimum surface a warning naming the consequence. Add the cadence-vs-policy census to the schedule tests.

From the 2026-09 brains-review campaign (measurement lane, finding A9); verified first-hand at the cited lines.