Cline fixes a memory leak that grew a background process to gigabytes

Cline's background Hub process was sending a full copy of the conversation transcript to every connected client on each session status update. On a long-running task, that meant every status change pushed megabytes of duplicate data, and the process grew to tens of gigabytes over a session. Version 4.1.17 fixes it: status snapshots now carry state only, not the transcript, according to the release notes.

Two other fixes are in the same release. A failed hook spawn used to crash the extension's core process and kill whatever task was running, taking down work that had nothing to do with the hook. Now a bad hook fails on its own without touching the rest of the extension. Checkpoint restore had a similar failure mode: if you made commits after a checkpoint and then tried to restore it, Cline would drop those commits, and the only way back was digging through the git reflog. It now refuses to restore when it detects commits made after the checkpoint, instead of proceeding and losing the work.

None of these are new features. They're the kind of bug that only surfaces under real use: a long session, a hook that happens to fail, a restore attempted after normal git activity. If you've had Cline balloon in memory on big tasks or lost checkpoint history to a restore, this release is why those stop happening, not why they started.