Resume is a start button, not an engineering project

On ephemeral-sandbox platforms, letting a user return to last week's session is an engineering project: serialize the state before teardown, store it, re-hydrate a fresh sandbox on return, and hope the reconstruction is faithful.

On Hoody, the user's sandbox is a container that simply didn't die. Your product's Resume button is a start call. The filesystem is exactly as they left it, the SQLite rows are in place, and the daemons come back in their configured startup order. Tuesday's user sits down at Friday's machine.

The serialization format, the re-hydration pipeline, the faithfulness bugs: none of them were built, because none of them were needed.

Continuity isn't a feature you built. It's a property you inherited.