Cline's checkpoint restore was silently orphaning commits made after the checkpoint
GitHub·high signal
SDK 0.0.82 (2026-09-02) makes checkpoint restore refuse to run when HEAD has moved past the commit the checkpoint was taken on. The restore's `git reset --hard` had been knocking any later commits off the branch, leaving them reachable only through the reflog; the branch move is now a compare-and-swap so a commit landing mid-restore cannot be lost either. If you use checkpoint/revert as your agent safety net and commit while an agent works, this was a data-loss path.