persistent Repository
Decorate runtimeRepository so that processes are checkpointed to snapshotStore and restored from it when runtime state has been lost.
The returned repository reads through: AgentProcessRepository.findById falls back to the snapshot store on a miss and warms the runtime repository with what it restores.
Parameters
fast, usually in-memory, repository holding live processes
durable backend supplied by the application
mapper used for the snapshot payload and for blackboard values not claimed by a supplied serializer
supplier of currently registered agents. Snapshots store the agent name, so restore binds a process to the live definition; this is a supplier because the platform is constructed after the repository
supplier of platform services for restored processes, a supplier for the same reason
when a process is written to the snapshot store. Defaults to LifecycleCheckpointPolicy, which checkpoints processes that are WAITING or finished
application serializers for blackboard values needing special handling, consulted in Spring @Order before the Jackson fallback
clock used to stamp snapshots