The arm64 (apple-silicon) target assumed a native macOS runner, which
does not exist on the forge. There is one self-hosted runner, ws-brn,
registered linux-amd64:host -- jobs run directly on the host as brn,
with no docker. So cross-rs cannot run (no container engine), and it
cannot target apple-darwin from Linux regardless.
Build arm64 by native cross-compilation instead: rustup target add
aarch64-unknown-linux-gnu plus the host's aarch64-linux-gnu-gcc linker.
Same arm64 binary, no docker. The asset is now aarch64-linux.
Also drop the host-incompatible setup steps surfaced by running it on
the real runner: hurl is already installed (the sudo dpkg step failed,
brn has no passwordless sudo) and the aarch64 linker is already present.
Split a single test gate (test + hurl) from the per-target build matrix.
Pass inputs.tag via env to the staging step (sie review note, ANW-30).
Forgejo-side counterpart to the GitHub release.yml (ANW-29). Driven by
workflow_dispatch (UI or API) rather than a release-published event, so a
build can be triggered for a test. Builds the release binary natively per
target, runs the test suite first, and publishes the assets to a Forgejo
release via actions/forgejo-release.
Assumed runner labels linux-amd64 / macos-arm64 must match the forge's
act_runner registration; arm64 needs a native Apple Silicon runner. Flagged
to aav -- correct if the topology differs.
