bernstein writes a write-ahead log to .sdd/persistence/ on every state transition. when you restart with bernstein run or bernstein resume, the orchestrator loads the wal, rebuilds the task table, re-attaches to live worktrees under .worktrees/, and continues from the last persisted checkpoint. tasks that were mid-flight when the process died are re-queued with a +1 attempt counter; the prior worktree is preserved so you can diff it before the retry overwrites the branch. never grep for the literal string bernstein and kill matches; use the pid file under .sdd/runtime/ instead (bernstein stop --hard does this for you).
canonical answer