Dreaming cron now survives runtime service changes

The scheduled job that manages memory "dreaming" — a background process that promotes short-term memories — would silently break whenever the cron service was swapped or reloaded during normal operation. Because cron reconciliation only happened once at startup, any runtime changes to the service, plugins, or configuration would leave the job stale or missing without warning.

A new reconciliation function now handles both startup and runtime paths. Instead of reconciling once and forgetting, the system re-checks the cron service state whenever configuration or plugins change. Missing jobs are recovered, and updates to schedules or timezones are applied automatically. A 60-second throttle prevents excessive reconciliation runs.

This fix lives in the memory-core extension and ensures that memory management continues reliably regardless of runtime service changes.