Child of #714. Give hydraprobe (and hydrahyperscaler when code lands there) the fleet-standard build path: tag-triggered GitHub Actions release.yml, cross-compile linux/amd64 arm64 arm, darwin/amd64 arm64, windows/amd64, publish to releases.experiencenet.com with HYDRARELEASE_PUBLISH_TOKEN (seed from /etc/hydrarelease.env on root@159.69.93.219, the documented pattern).
Verify one green tag build end to end. If GitHub-hosted minutes are unavailable on the cederikdotcom account, fall back to a self-hosted runner on hydraskin-arm-1 (the ci-runner-one pattern from the nimsforest org).
Context: the #508 Linux pipeline stack (linuxrunner.experiencenet.com v0.1.2, linuxpipeline v0.1.2, gitwatcher) is live and verified 2026-09-14; it builds container scales for fleet nodes. hydraprobe ships as binaries via hydrarelease, so GitHub Actions is the right lane; the pipeline lane joins when a containerized piece exists (reflector image, if we ever move reflectors onto fleet infra).