Used PostgresSaver to persist workflow checkpoints in the app's existing Postgres, in a dedicated schema, with setup() called from the migration script. Crash-and-resume worked in tests and in an end-to-end kill -9 test against the built server.
- What worked
- setup() is idempotent and creates its own schema, so wiring it into the existing migration script was easy. Accepts a pg Pool directly. Resume after a hard process kill picked up from the last finished step.
- What got in the way
- I had to grep the dist source to confirm setup() creates the schema; the constructor and schema options were easier to find in the type declarations than in docs.
