v0.25.1 — the final Python engine

This is the final release of the Python engine. trck is a single binary from
v0.26.0 onward.

Nothing about your tracker changes. The on-disk format is identical, and the binary reads an
existing issues/ directory exactly as it stands — there is no migration to run.

Getting the binary

curl -fsSL https://raw.githubusercontent.com/leonkacowicz/trck/main/scripts/install.sh | sh

It picks the right target from uname, verifies the published checksum, and installs to the
first writable directory on a short list. Binaries for Linux (glibc and musl, x86_64 and
aarch64), macOS (Intel and Apple Silicon) and Windows are attached to the v0.26.0 release, and
there is a Homebrew formula in packaging/homebrew/.

What changed in 0.25.1

trck update no longer tries to update. It fetched ./trck from the repository tree at the
newest release tag, and that file is going away — an engine that kept fetching would report
HTTP Error 404 and blame the network for a decision this project made, forever, because no
later Python release will exist to correct it. It now says where to go instead.

trck update --ref <tag> still fetches a specific Python version if you need to pin one.

Why

The engine was one standard-library-only Python file, which bought a great deal: no install, no
dependencies, and a copy you could commit next to your data. What it could not buy was speed at
the size trackers actually reach, or a single artifact that runs where Python isn't. The Rust
engine is measured against the same executable specification this one was — conformance/, 227
fixtures, run against the binary on every commit and against the published artifact before any
release is allowed to exist.

Marked as a pre-release so that curl | sh and /releases/latest continue to resolve to the
binary. It is not a preview — it is the last one.