* x86_64: keep ggml on x86-64-v3 and refuse older CPUs with a clear message (#592)
Reverts #595's Ivy Bridge floor: it slowed CPU transcription for everyone. ggml goes back to its x86-64-v3 defaults (AVX2, BMI2, FMA, F16C). Hex's own Rust stays baseline x86-64, and the first thing main does on Linux and Windows x86_64 is check AVX2/BMI2/FMA/F16C with is_x86_feature_detected!. Without them Hex prints and shows "Hex needs a 2013 or newer processor (Intel Haswell / AMD Excavator or later) with AVX2. This PC's processor isn't supported." (a native MessageBox on Windows; stderr, which the journal logs, and zenity, kdialog or notify-send on Linux) and exits 1. Every command is covered except --version and --help, which installers and the updater run. ggml-cpu has no static constructors, so nothing runs v3 code before main.
The release guard now asserts the opposite: ggml's CPU libraries must hold AVX2 and FMA (the build targets v3) and no AVX-512 or AMX. Docs state the requirement.
* cpu_floor: harden DLL search first; no dialog under systemd, in a terminal or for hex service; guard rejects AVX-VNNI
* cpu_floor: always exit 1; Windows always shows the message box; Linux skips the dialog in a terminal, under NOTIFY_SOCKET, or for hex service
* x86_64 releases: build ggml for the Ivy Bridge floor and fail on BMI2/AVX2/FMA (issue #592)
GGML_NATIVE=OFF alone leaves ggml's GGML_AVX2/BMI2/FMA/F16C on, so Hex 3.0.0 on Windows x64 died with 0xc000001d (illegal instruction) on an Ivy Bridge Xeon E3-1220 V2 once transcription started (reported by @Hc-Web-Dev). Linux and Windows x86_64 release builds now pin SSE4.2 + AVX + F16C and turn AVX2, BMI2, FMA, AVX-VNNI, AVX-512 and AMX off (scripts/ggml-x86-baseline.txt), the floor transcribe.cpp already uses on Intel Macs. Runtime dispatch (GGML_BACKEND_DL + GGML_CPU_ALL_VARIANTS) needs shared ggml libraries, which our single static executable can't ship. CPU transcription on newer x86 CPUs loses AVX2/FMA kernels; Vulkan is unaffected.
.github/release/check-x86-baseline.sh guards both build jobs: the executable may hold no BMI2 instruction (3.0.0's Linux build holds 100; Rust crates that use AVX2/FMA/AVX-512 behind run-time detection use none), and the ggml static libraries no AVX2, BMI2, FMA or AVX-512. No crate sets target-cpu; the only rustflags are +crt-static; no other C/C++ dependency builds with -march=native or AVX2 (Moonshine/ONNX are gone).
* check-x86-baseline: fail on missing inputs or empty disassembly; match llvm-objdump's suffixed BMI2 mnemonics
* Rename voice-control to hex everywhere, without migrations
The Cargo package and binary are now hex, every OS keeps its data in a
hex folder, and VOICE_CONTROL_* variables are HEX_*. Hex is a fresh
app: the macOS voice-control rename, its symlink, and the Windows and
Linux beta settings imports are gone. The Windows installer gets a new
AppId so it never takes over an old voice-control install's entry.
* Format
* Drop the Windows paste-last default only the beta import used
* Linux ARM64, .deb, and .rpm releases
Both Linux architectures build natively on Ubuntu 24.04 runners (glibc 2.39
floor, Vulkan on both), publish linux-arm64 plus linux-<arch>-deb and -rpm
(hex.deb, hex.rpm) built with nfpm and installed on Ubuntu and Fedora in the
build job. hex-bin gains aarch64. Package installs report deb-<arch> or
rpm-<arch> through dpkg/rpm ownership and get the stable update command.
* build-linux.sh prints only the executable's path
* Linux releases link no system BLAS, as the Arch build shipped
* Linux build: keep libopenblas-dev for build.rs's dropped -lopenblas
Dev and check runs stamp 0.0.0-dev-$GITHUB_RUN_NUMBER with no tag lookup; versions are display text that the release service and the updater never compare, so builds numbered below 2.3.1 are fine. macOS dev builds take the run number as CFBundleVersion. The Linux and Windows installers and the Windows Setup.exe no longer refuse to install a lower version than the one installed. Docs describe following the channel's current release, required releases, rollbacks, and confirmed channel switches. Also drops an unused import that failed Check macOS.
The updater refuses an update whose binary reports another version than the manifest, so staging stamps the prerelease into Cargo.toml and Cargo.lock before building; the AUR package spells it as pkgver X.Y.Z_dev.N.
The Release workflow uploads each target and the release to anoma.ly/release (dev.anoma.ly/release for staging) with curl and its GitHub OIDC token, records the AUR, Homebrew, and Nix distributions, mirrors the files to GitHub, and builds hex-bin from the published file. The ed25519 feeds, appcast generation, and Sparkle ZIP naming are gone; the 2.3.1 feeds stay frozen. Builds and installers use the release service names, the installers read the stable manifest and write the direct-install receipt, and the site reads its download links from the manifest.