Dev tool 'resumeproof' exposes the crash gap between action and acknowledgement

A developer has released resumeproof, a small offline laboratory tool designed to make visible the critical failure window that occurs after an external action executes but before the calling system records its acknowledgement. The tool uses two separate SQLite databases — a workflow journal and a simulated tool ledger — to replicate this scenario without any real network calls or transactions. A demo deliberately kills a child process after the tool ledger commits but before the journal acknowledges the result, illustrating how idempotent and non-idempotent workflows respond differently to recovery. Idempotent workflows can safely resume using the original receipt marked as replayed, while non-idempotent ones halt and require manual operator reconciliation due to unresolvable uncertainty. The project, requiring Python 3.11 or newer, aims to highlight that a clean process exit or successful HTTP response does not capture what happened in the gap between a provider's commit and a caller's acknowledgement.