# Does a REAL release (scripts/build-release.sh) ALSO produce the aarch64 (ARM64) tarball
# whp-<version>-aarch64.tar.gz, publish it as releases/whp-<version>-aarch64.json and
# latest-aarch64.json, and leave every x86_64 artifact exactly as it is?
#
#   disabled  the release is exactly the x86_64 one. The default; a MISSING marker means this too.
#   enabled   also build the aarch64 tarball. Requires scripts/go-release-payload = enabled (the
#             aarch64 whp, whp-privd and whp-pam-check come from CI, verified against
#             scripts/go-payload-aarch64.pins) and scripts/release-publish-mode = direct.
#
# A committed marker, like scripts/go-release-payload: no flag, no environment variable. Flip it
# to `enabled` in a reviewed commit only after docs/arm64/BUILD.md "Before enabling" is done:
# the aarch64 pins are recorded and a real ARM host has run the result.
disabled
