0.7.1 — the CLI update panel tells the truth, and a session can move to a new CLI without losing the chat

Stoke followed the wrong update channel. checkForUpdate read the npm
latest dist-tag while claude update follows autoUpdatesChannel from
~/.claude/settings.json. On a machine pinned to stable those were fifteen
releases apart, so the panel advertised an update the CLI would always decline —
and then blamed your package manager for it, advice claude doctor flatly
contradicts. Stoke already drew that setting; one half of the app wrote the key
and the other half never read it. It reads the configured channel now, names a
channel that publishes nothing rather than substituting a number, and refuses to
auto-update when the CLI's own updates are switched off.

A running session is stuck on the claude it started with. Updating the CLI
leaves every open chat on the old binary, indefinitely, with nothing saying so.
The status bar now offers relaunch on <version> when the session in front is
behind the installed one: it stops the process and resumes the same conversation
on the new version, in the same tab. SSH tabs and --continue tabs are refused
with a reason rather than silently, because neither can be resumed safely.

Three bugs fixed on the way, two of them long-standing:

• The context meter read 200k for any resumed 1M session — the payload naming
  it is deleted with the old process and rewritten a second later, and nothing
  recomputed the window once the transcript stopped moving. Measured at
  125k/200k · 63% while the payload on disk said 1000000. This affected the
  paused-tab Resume too, since tab restore existed.
• verify-tabs.mts printed its own tally two thirds of the way up, so a third of
  the file could print FAIL and still exit 0.
• The relaunch pill could be double-clicked into five tabs and five claude
  processes resuming one transcript.

macOS auto-update from 0.7.0 works: same signing certificate, so no manual
install this time.
-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgRMU791FgMe8r+DfqyzVBFQ6kaz
8vnoPpPI8Ui7gGH3MAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
AAAAQKE4MQawCb86dcC/Yl8r2Pkvhtz4B7tuFYE9VIGHTx30FeEyNSbHnUBaiINj1Irli4
mtpYSJOQoOvi3x1pt3OAc=
-----END SSH SIGNATURE-----