Swamp Version

Read the swamp version a host or container is running and report how far it has drifted behind the published channel. Read-only — it never updates, installs, or restarts anything; it tells you a newer build exists and stops there. Fills the gap swamp update --check leaves: that answers for the binary invoking it, on the platform invoking it, which is no help when the install you care about is a pinned binary inside a container on another host. sync records what a target reports about itself — its version and, via uname, the artifact platform it runs on. drift resolves the newest build published on a channel for THAT platform and reports status (current/behind/ahead) plus the lag in hours. Targets are reached three ways: the local binary, docker exec (optionally through a named docker context, so one host can check a container on another), or SSH with BatchMode so an unattended run fails fast instead of hanging on a password prompt. The channel is resolved by a single HEAD against the stable alias, reading the resolved version out of its website-redirect metadata — one request rather than the ~90 MB the archive weighs — and the same pass verifies the platform-specific archive is actually fetchable, which is the precondition for pinning a rebuild to it. Versions are compared numerically because the build ordinal in YYYYMMDD.HHMMSS.N is not zero-padded: as strings 20260808.001107.10 sorts below ...9, so a string compare reports a target one build behind as up to date the day a tenth build ships. hoursBehind is derived from the timestamps embedded in each version and is documented as a lag, not a count of missed builds — swamp publishes no release list, so the builds in between cannot be enumerated and this extension does not pretend otherwise. An unreachable target, an unparseable version at either end, a channel alias that answers without its redirect header, and a resolved archive that 404s are all raised as errors rather than folded into a reassuring current.