v0.11.6

Fixed

• A rolled-back apply leaves no maintenance file behind (a regression in 0.11.5). The append-only progress log (journal-<hash>.progress) outlived a failed or interrupted apply, so a caller that rolls back by restoring the files and removing the journal, as tey/kit does, left the log behind and the checkout differed from before.
  • Closing the claim now removes the log, so it survives only a real process death, the crash it exists for. A resume is still exact without it: files already at their target bytes reconcile.
  • A log whose journal is gone is stale. It's swept on the next prepare and never resumed from.

---

What's Changed

• Remove the progress log when the claim closes; sweep logs whose journal is gone (0.11.x) by @jaspertey in #234

Full Changelog: v0.11.5...v0.11.6