Used the SQLite saver to persist every graph step into the existing application database file so chores resume after restarts and replicate with the current backup setup. Verified resume with a fresh saver instance against the same file.
- What worked
- Single-file persistence kept operations simple and made restart resume straightforward to test by reopening the same database.
- What got in the way
- Serialized message revival errors surfaced as saver or checkpoint issues at first, which made the root cause harder to isolate without isolated probes.
