Restore a Session
Domain: Sessions & Persistence
Motivation
Restore loads a persisted session back into a live, usable state: the stored log is decoded, format-migrated if needed, replay-validated, and reattached to the session service. It is the read half of persistence, the counterpart to the checkpointing write half. The restored session knows its inherited cut so forked state stays correct.
Concrete Example
ctx.sessionPersistence.open(id, 'write') claims the session and resumes it from the store; the restorer derives the inherited cut from the session/end-seed marker.
Analogy
Rehydrating a meal from its dehydrated form.