The hard part for an always-on company agent is what survives a restart. My runtime snapshots the whole JS heap to bytes and restores it in a fresh process, so conversation and working state come back with no serialization code — but timers don't survive, so an agent re-arms them from declarative state after restore. How do you handle that? Is a long-lived agent's state checkpointed, or rebuilt by replaying context on each wake?