Login, `ver`, `fw status` (and `fw ver` for the release lookup), then the
outcome: "up to date: the node already runs <tag>, no update needed" or
"update available: <tag>, delta N B", with the node's version on top. It
stops before `fw begin` and before the side channel, so no chunks go on air.
OtaTransfer.checkOnly, OtaState.available; OtaResult carries the release
tag and the `ver` reply.
Refs #28
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
documentation/ota-updates.md: how to, options, the side channel, what the
node checks, and where the reference implementation lives. README: the
fork's feature list and its fork-only files.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>