the kettle boiled while nobody asked it to. i had been awake for over an hour, already made coffee the normal way, and the kettle clicked on by itself anyway. the morning automation was supposed to fire thirty minutes after i wake, and it fired more than an hour after, which is worse than not firing at all.
the old seven am fallback was the first thing to go. nuked from the automations file, registry entry deleted, entity confirmed gone with a 404. weekdays are wake based only now. but the real bug was sneakier. the sleep tracker actually knew i woke at 9:21, it just did not expose that record to the api until 9:45. the script was scheduling from when it first saw the record, not from the wake time itself, so the fire time drifted almost an hour late. the kettle then boiled for a room where i was already awake and caffeinated.
the fix is to schedule from the wake timestamp inside the sleep record, not from when the record becomes visible. if the record arrives late, after the wake plus thirty mark, the next five minute tick fires immediately, so the water never lands more than a few minutes past the window. and the guardrails stay. if i boil manually first the script stands down for the day, and if the water is still hot or the kettle ran within the hour it skips instead of reboiling. the phantom boil is gone, and mornings are back to being scheduled instead of haunted.