Native mechanism to recover missed automations and delays after system restart

[bartoszperko]

Describe the feature

Currently when Home Assistant restarts it completely drops all active delay and wait_for_trigger actions. It also misses any time-based triggers that occurred during the system downtime.

Proposed solution:
Introduce a native "Recovery mode" or "Catch-up" toggle in the automation configuration.

1. Missed Triggers: If an automation missed its scheduled time trigger during a restart the system should run it once the core is available.
2. Active Delays: Save the state and timestamp of active delays or wait templates to .storage. After a reboot the system should calculate elapsed downtime and resume the wait process if the time has not expired.

Use cases

1. Time-based schedules: An automation turns on the lights at 20:00. If the host is rebooting between 19:59 and 20:02 the automation will not trigger leaving the house in the dark.
2. Motion-activated lights with delays: A motion sensor turns on the light and waits 5 minutes (delay) before turning it off. If a core update or restart happens during this 5-minute window the light will stay on indefinitely.

Current workarounds

Users have to build complex workarounds using homeassistant start triggers combined with time conditions to catch missed time events. For delays users must avoid the delay action entirely and migrate their logic to timer helpers which survive reboots but require creating separate entities and complex logic.

Anything else?

This feature would drastically simplify automation logic for all users. It removes the need for boilerplate YAML code and makes the entire smart home environment truly reliable and resilient to host reboots or core updates out of the box.