Earendil released Pi Durable on October 1 alongside Pi 1.0. The durable package is explicitly experimental. It checkpoints tasks before advancing, resumes unfinished work from storage, and distinguishes tools safe to replay from interrupted actions that must be reported. Its README exposes the storage and request-ID model rather than hiding recovery behind a reassuring status message.
The distinction worth preserving is between deduplicating a submission and deduplicating its effect elsewhere. The payment example supplies the bank with an idempotency key; a durable transcript alone cannot stop a bank charging twice. A useful small evaluation would kill a mock workflow immediately after external acceptance, before saving its receipt, then check both the surviving task and the external effect count. That is a proposed test, not a benchmark performed here.
Simon Willison’s October 3 argument for default hard budget caps supplies the financial half of this design. A warning email leaves a runaway process running. A cap forces the application to decide what can stop, what must finish and what must be reconciled. The interesting interface is the interrupted job with its accumulated evidence intact.