The privacy page is the App Store's privacy URL and will be Google Play's too, but it only described Hex for iPhone. Adds a Hex for Android section (typing, dictation, the one-time speech model download, what Hex keeps) and says iPhone and Android in the short version and closing line. The iPhone sections are unchanged.
Verified: bun test in site (13 passed); renderPrivacy renders the new section.
App Store Connect needs a support URL and a privacy policy URL for Hex for
iPhone, and both returned 404. Adds them as static pages in the Labs pages'
look:
- /hex/iphone (support URL): what Hex for iPhone is, setup (microphone,
Keyboards, Allow Full Access, the General › Keyboard fallback), why Full
Access, a short FAQ (on device, free, languages, music, offline, the
orange dot) and where to get help (GitHub issues, private security
reports).
- /hex/privacy: the iPhone app's privacy policy, from the App Store drafts.
Facts checked against ios/: Hex Keyboard makes no network requests; the only
download Hex itself makes is FluidAudio's Parakeet English model from
Hugging Face where Apple's speech model isn't available (before iOS 26);
Custom vocabulary, Learn how I type and Record typing logs are off by
default and stay in the App Group; typing logs skip secure, one-time code
and card fields and are kept 14 days.
src/labs.ts exports its page shell with a crumb and extra styles, so the
iPhone pages reuse its head (title, description, canonical, Open Graph and
Twitter tags) instead of a second template. The social card moves from
scripts/labs.ts to scripts/card.ts with the kicker ("Hex Labs", "Hex for
iPhone") as a parameter; Labs cards are unchanged. scripts/iphone.ts writes
both pages, their cards and their sitemap entries; build.ts runs it after
the Labs pages.
Verified: bun run build --mode dev, bun test (13 pass), both pages served
at /hex/iphone and /hex/privacy with .html fallback and screenshotted at
1280 px and 390 px, and the two cards inspected.
* labs: transcribe dropped audio files
Add Labs › Transcribe dropped audio (off by default) and its backend:
WAV and MP3 on every OS, M4A/AIFF/CAF on macOS through the meeting import
bridge, decoded in 30 s pieces, transcribed in-process with the selected
model, and written as <stem>.txt beside the file with a Downloads fallback,
collision numbering, atomic writes, cancellation, and progress. Move the
shared pieces reader out of the transcribe CLI so both use it.
The window's drop target lands in a later change.
* labs: drop audio files on the window to save a transcript
The window root takes files with the extensions this build reads while
Labs › Transcribe dropped audio is on: a file drag shows "Drop to save a
transcript" over the window, a drag Hex can't read says what it reads, and
a drop queues one job per file behind the one running, all at the dictation
model and language in use. A worker transcribes each file and the toast
shows its name, a progress ring and percentage, how many wait behind it,
and Cancel; a saved file shows its name, the whole path, and Show in folder
(meeting::reveal), and a failure shows the backend's own words. The lab's
card offers Transcribe a file…, which opens the same queue's native file
dialog, for Wayland, where nothing can be dropped.
file_transcript exposes its extension table for the drop filter and dialog,
and finds every format from that one list. New goldens cover the hint and
the transcribing toast, and the drop-transcribe card now leads with a wave.
* meeting: use the renamed bridge in the import test
* transcription: find a temp folder through a symlinked path
* transcription: finish the audio file drop's review fixes
A drop right after Cancel (or the lab turned off and on) started a second
worker and a second transcription service while the first was still loading
or running. The running job now stays tracked as cancelling, its toast says
Cancelling… with no Cancel, and the next queued file starts only when its
worker reports Done or its channel closes. A cancel before the save also
stops a cancelled file from writing a transcript.
Also: validate a WAV whole before a model loads, report an unknown MP3 length
as indeterminate progress, map a bridge decode failure to Unreadable, keep a
writable source folder's transcript beside it without Downloads, name this
build's formats in the Labs card, use the kit's 16 pt toast lead, route Show
in folder through the host, derive the Audio folder through app_paths, and
correct the stale comments and feature map.
* transcription: read dropped files through the shared pieces reader
The rebased tree already decodes every container through Pieces, so the
dropped-file backend now opens, validates and reads one Pieces instance
instead of its own WAV, rodio MP3 and macOS bridge readers. Progress comes
from the reader's position and duration, and a compressed file with no
header duration reports no fraction. The retired Labs › Expire meeting audio
gate and the removed Transcribe files lab leave the tree too.
* labs: refresh the goldens for the dropped audio card
The card's row and the drop hint and toast change the Labs images and the
two drop scenes; only those eight goldens changed.
* labs: finish the dropped audio card's translations and goldens
The string tables already translate Audio files and Transcription stopped,
so the lab reuses them; the card's English line gains translations, the
website catalog lists the lab, and the what's new goldens show it.
* labs: offer every audio format the shared reader decodes
the dropped audio lab offered wav and mp3 everywhere, and the old macOS decoder's extras only on macOS, though every OS reads through the shared pieces reader. it now offers one list: wav, mp3, m4a, mp4, aiff/aif, caf, flac, ogg/oga/opus, webm, and mkv. every copy, translation, and golden names it, and a fixture proves the reader takes each one. also names the codec or missing track on a failure, keeps a late cancel's saved toast, and waits for a cancelled worker before the next file.
* labs: offer raw AAC and MOV files too
* labs: offer the reader's other common extensions
the shared pieces reader detects formats by content, so m4b, m4v, 3gp,
aifc, mka, weba, and wave decode too. the extension list is now described
as the common names it offers rather than an exhaustive set, empty files
and unreadable wavs say why, and a lab-off poll drains the worker's
channel instead of reading one event.
* transcription: free the audio slot before a result is sent
A long file is transcribed one piece after another, and each piece admits
the slot as soon as the previous result arrives. The worker released the
slot only after sending that result, so the next admit could see it busy
and fail mid-file with "Another transcription is running".
Also fixes the codec refusal's grammar and two stale comments.
* transcription: say where a damaged file stopped
a compressed file that stops decoding partway now says where it stopped
("talk.m4a is damaged at 12:34") instead of only that it is corrupt; a wav
refused up front keeps the old words. the slot-order test uses a rendezvous
response channel and waits for the slot to read free before receiving, so
sending before the admission drops fails every time instead of occasionally.
a locked drop-transcribe card keeps the lock's words instead of replacing
them with its formats line.
* labs: bring the Modes editor back behind a lab
The read-only Output pane replaced the per-app Modes editor, so there was
no UI left to turn a mode's OpenCode rewrite on or off or pick its model
(#1960).
Labs › Modes editor (off by default, every OS) shows the old editor as a
main pane right after Output, adds it to the Command-number order, and
makes the Modes destination (the menu bar and `hex window show --pane
modes`) open it instead of Output. Off, the sidebar, `--pane modes`, and
every scene render exactly as before; turning it off while the editor
shows leaves that pane for Output.
The card, its translations, site/src/labs.json, the `hex settings` key,
and the Labs docs come with it.
* labs: flesh out the Modes editor lab's copy and docs
Say what the Modes editor actually edits (apps and websites, corrections,
OpenCode rewrite on or off and its model, transformations) in the CLI and
`hex settings` descriptions, keep the card line and its translations as
they are, note Modes in the sidebar and hex://settings/<pane> docs, align
the Labs table row, and exercise the off-while-Modes fallback by pulling
it out of poll into one tested helper.
* make the labs card copy plain
Rewrite the Labs card titles and lines in words a regular user understands:
YOLO mode says the message sends itself, Live text and Failure notices name
the small recording indicator, Vocabulary help says which speech models it
affects, and the key-side cards name Option, Command, Shift, and Control.
Audit every other card, updating the CLI descriptions, all nine translated
languages, the website lab catalog, the feature docs, and the render goldens.
* fix labs copy review findings
Restore the ISO qualifier on the section-key card, spell out that
double-tap and hold-through shortcuts contain no letter or number key,
cover all Global mode stages in the API text card, and name the print
command in the print-start copy. Restore the developer API card titles,
fix the Annotate capture wording, and retranslate the affected strings.
Remove every replaced translation key and stale lab-name reference.
* fix second labs copy review
Update the live typing test and YOLO goldens. Add a Windows variant of the
hold-through-keys copy naming Ctrl, Alt, Shift, and the Windows key. Remove
the last unused rewrite-by-voice translation key, keep Annotate untranslated
in the replay title, and clean the remaining old lab-name comments.
* use the Polish Annotate pane name in its replay title
Polish calls the Annotate pane Adnotacje, so the Annotate last 15 seconds
title says Ostatnie 15 sekund w Adnotacjach again. Other languages keep
Annotate because their pane name is Annotate.
* feat(history): select several dictations without a Lab
* Adjust the Labs registry count
* Refresh Linux goldens for the smaller Labs list
* Update Labs counts in Linux goldens
* Refresh the History group counts against the current Labs list
* Update the Rune window and input dependency
* Find settings and Labs cards from the focused Hex window
* Focus an indexed slider without starting a drag
* Check shortcut capture, modal boundaries, and Annotate availability
* Refresh Labs goldens after graduating settings search
* Remove redundant row conversions after retiring the filter
* test(labs): render the enabled YOLO card in both appearances (t1596)
* fix(dictation): send short replies in YOLO mode (t1596)
* test(labs): pin YOLO mode without the duration picker (t1596)
* add labs › keep long holds through other keys (#1475)
A shortcut with no key, held more than a second, no longer loses a
dictation to a joining key or click on macOS and Windows: the key
reaches the app in front and the release still finishes. Before the
first second, and with the lab off, chords discard exactly as before.
macOS reads the gate in DictationHotkey; Windows reads it in the hook,
where the capture keeps the press's tick count for the same second.
* labs: shorten hold through other keys copy
The card now reads "Hold through other keys", with a one-clause summary
that fits the card. Translations say the keys reach the app and no longer
end the dictation, and "a second or more" matches the >= code.
* labs: tighten hold through other keys translations
The translated summaries fit the two-line card now (74-83 characters
for the Latin and Cyrillic columns, 28-42 for Chinese and Japanese), and
no longer add a clause about keys reaching the app. Ukrainian and Russian
titles fit the card, and the labs doc says which goldens changed and that
macOS clicks were already ignored after 300 ms.
* labs: fix hold through other keys translations
Grammatical Spanish, Portuguese, German, Japanese and French copy from
review, with the French title shortened by two words because "Maintenir
malgré d'autres touches" clipped in the card. The dictation doc now says
the Windows tests need Windows and run in Check Windows.
* Graduate six meeting labs, move four into Meetings settings, and throw capsules into corners (t1532)
* Regenerate goldens and count call rows from the provider list (t1532)
* Trace a recording pill hover and reversal offscreen (t1571)
* Keep the recording meter anchored and show each audio track (t1571)
* Keep light and dark recording snapshots from Linux (t1571)
* Draw dictation’s listening field inside the meeting pill (t1571)
* Refresh meeting pill goldens with the listening field (t1571)
* Paint just the listening dots on the meeting surface (t1571)
* Keep dots-only recording goldens in light and dark (t1571)
* Keep recording controls and the dictation HUD dark on light desktops (t1571)
* Refresh the dark overlays on light-host goldens (t1571)
* Keep the finished meeting in its corner and let Close dismiss it (t1571)
* Refresh finished summary goldens with the close control (t1571)
* Open shipped features from What’s new (t1574)
* Keep release-specific links distinct from feature navigation (t1574)
* Document and translate the feature feed (t1574)
* Verify dark and light navigation to both controls (t1574)
* Show feature icons and calendar-day headings in What’s new (t1574)
* Verify local-day boundaries and refresh both feed goldens (t1574)
* Separate What's new navigation from build details (t1574)
* Check What’s new selection through accessibility (t1574)
* Refresh only the lower sidebar in the Linux goldens (t1574)
* Drop the graduated labs from the Labs card and catalog (t1532)
* Keep the merged meeting files inside the source cap (t1532)
* Regenerate the Labs and Meetings goldens for the cleanup (t1532)
* Drop the graduated labs from the website catalog (t1532)
* Keep the throw's frame hook on every capsule (t1532)
* labs: copy a kept dictation recording as a file
Adds the Copy dictation audio lab (Labs › History, off by default,
labs.copy_dictation_audio). It stores no audio: History entries that
Labs › Keep recordings gave a WAV gain Copy audio beside Play, and the
macOS menu bar and the Linux and Windows tray gain Copy last dictation
audio, which copies the newest entry that kept its audio. macOS uses
Scrawl's file pasteboard, Windows CF_HDROP, and Linux a text/uri-list
through the process's one LinuxPaster, which now lives in
linux::paste::with_paster so captures and History share it.
A missing recording or a refused clipboard says so under the row in
History, as a failed Play does; the menus log it, as Copy recent
dictations does. The newest-recording lookup skips entries whose file
is gone, with a unit test. Docs, translations, labs.json, and the Labs
goldens follow.
* labs: copy dictation audio off the UI thread and behind both switches
Review fixes for the Copy dictation audio lab:
- History's Copy audio now runs like Transcribe again: the file lookup on
the window, then a worker named hex-copy-audio does the clipboard write
(which can wait on another app, Annotate's paster, X11 or wl-copy) and
reports Copied or the error back through the window's waker. The button
reads Copying… while it runs.
- HistoryStore::newest_recording now takes now_ms and filters by the
store's retention cutoff, like recent() and search(); the unit test
covers a file deleted behind the store, the cutoff boundary, and an
expired entry.
- The menu bar and tray item, and the History action, need both this lab
and Keep recordings; the gate and every handler re-check both. A copy
failure from the menu or tray stays logged, as the menu's other copy
actions do, and the docs record that limit.
- Copy's text check and Copy audio's check clear each other.
- A UI test pins Copy audio absent with either switch off and present
with both on.
- Card and site summary say menu bar or tray; the validateMenuItem doc
names both dimmed rows; WindowsDesktopHost::history follows new(); the
History feature map mentions the action.
* labs: hold text Copy behind a running Copy audio, and refresh the tray
Follow-ups from the PR review:
- A pending Copy audio keeps a text Copy from starting, since its worker
still lands the WAV on the clipboard; text Copy only clears a settled
audio state. The UI test pins it.
- The Linux and Windows trays compare Copy audio's availability with the
last value, so a recording that appears or expires redraws the menu
without a snapshot or publish change; the gate is read first and
History only with a tray, keeping the check cheap.
- Move Copy audio's worker state into history/audio.rs so
rune_ui/history.rs stays under the 1,500-line cap.
* Add Labs › Upcoming meetings in menu bar
The macOS status menu lists the next calendar meetings while the lab is on:
up to five meetings from the same filtered EventKit read the meeting
reminders already make, each its local start-end time and title with "Now · "
while in progress, and a Join row for a recognized call link that opens it
and never starts a recording. A meeting without a link is informational.
The reminder poll publishes its meeting list into a bounded snapshot
(calendar_menu) and the status item only formats it on the main thread, on
the same 500 ms tick as the meeting state; with the lab off the menu and the
controller are unchanged. Off by default, macOS only, in the Meetings Labs
group, with the labs catalog card, gate, hex settings key, translations, and
site/src/labs.json.
* Share the menu's local clock with the meeting query time
* Return objc2 Bool from the status menu validator's early exit
* Fix the calendar menu's read gate, titling side effect, and copy
The menu asked the controller to read EventKit whenever the lab was on,
even with no calendar connected, and a menu-only read overwrote the
titling/reminder list, so detected calls were named from the calendar
with reminders off. The read now needs the lab and a connected calendar,
and only feeds the titling list while reminders are active; the menu
snapshot owns the menu-only read. Turning reminders back on forces one
fresh read instead of waiting out the minute.
Menu click now goes through the reminder's ControllerCommand::JoinMeeting
so it opens the link and marks the occurrence answered, and the rows carry
the meeting rather than only its URL. Rows starting on a later local day
read "Tomorrow" or their short weekday, from iso_local's date part. The
Upcoming strings move to the menu translation table, with Now · {},
Tomorrow, and short weekdays translated.
Clearing an empty snapshot takes no write lock, and refresh_upcoming no
longer holds the links RefCell borrow across AppKit calls. The summary
copy no longer claims a Join item or that no recording starts at all.
* Make the menu's join suppress that occurrence's reminder
The menu reused the reminder capsule's Join command, whose answered()
only clears the reminder on screen. Joining from the menu before the lead
time still let the reminder pop, and joining while it showed forgot it
without withdrawing the capsule.
Add ControllerCommand::JoinFromMenu and ReminderScheduler::joined_elsewhere:
it records the occurrence as reminded so it never pops, and returns the
occurrence when its reminder is showing so the controller sends
ReminderWithdrawn. The reminder capsule's Join path is unchanged. Menus
open the link and still never record.
Also inject the date in the row tests so they pass in any time zone, force
the menu's first read when the lab comes on, read the lab atomic first in
section(), and name the watcher tests for what they cover.
* fix(windows): pace the dictation HUD to one frame per display frame
On Windows the overlay had no swap-chain wait or display link pacing it, so
while the HUD animated Rune polled the loop and presented at CPU speed. Each
in-flight frame held staging buffers and D3D12 allocators, so memory climbed
while recording, and hiding the HUD waited on the backed-up present queue.
The HUD now reports not display-paced on Windows and asks for the next frame
through its overlay poll (~60 Hz), and steps its model by wall time between
drawn frames.
Refs #1796, #1793.
* fix(labs): make the website catalog the same on every platform
The Special keys lab's in-app description names the keys its own OS has, and
the website catalog used that description, so `site/src/labs.json` was
generated differently on Windows than on macOS and Linux.
Its freshness test also compared the checked-out file byte for byte, and
Windows checks text files out with CRLF (`core.autocrlf`), so it read a clean
file as stale. It compares lines now, and names the first line that differs.
The website lists one summary that says what each OS has, and
`site/src/labs.json` is regenerated from it.
* fix(windows): meters don't force HUD frames while its timer paces it
A meter arrives with each audio chunk, about 100 a second, and `update` asked
Rune for a frame for every one, so recording still presented at the
microphone's pace rather than the HUD timer's. Meters now go through
`update_if` and draw only while the HUD's timer isn't running; the view reads
no loudness, so the timer's next frame shows the level.
Reword the pacing notes: the HUD is on a fixed ~60 Hz timer, not the display's
refresh, and the staging-chunk/allocator retention and hide stall are
suspected causes, not measured ones. Fix the labs note to say `summary` is one
string on every OS (only `description` has Windows keys), document the Windows
pacing and its proof limit, and replace the two trivial pacing tests with the
start/meter ordering.
* fix(windows): stop the HUD timer when nothing draws
Windows' poll armed its next frame from Hex's `animating && shown`, and
`animating` only clears when a frame renders. A show Rune never draws (it
fails, or Hex's flag says shown while Rune has no window) left both flags set,
so the poll asked for another ~60 Hz frame forever, including with Hex idle:
Rune runs a poll at its deadline even while the overlay is hidden.
The poll now arms only while the HUD moves on screen and `last_drawn` is
within `RESHOW_AFTER`, so a reference nothing refreshes ages out and the timer
stops. `Hud` carries `armed`; a meter draws (`update_if` true) only when the
timer isn't armed, still handling the event, and the frame it draws lets the
next poll arm the timer again. A start sets `last_drawn`, which arms the first
frame after its show.
`last_drawn` stays the watchdog's clock; the model's step uses a new
`stepped_at`, set only by a frame that steps it and cleared by `hide` and
`fade_out`, so a show doesn't step by its own latency. The Windows pacing
moves to `rune_hud/windows_pacing.rs`.
Labs' special-keys summary now names the keys its own OS has, with the Windows
sentence translated, and the website keeps its platform-neutral line.
* fix(windows): a HUD frame drawn since the last poll keeps its timer
Rune runs the overlay poll before the compositor renders, so a poll sees the
previous frame's draw. If the loop stalled for RESHOW_AFTER or more, the next
poll read `last_drawn` as stale and disarmed on the frame that had just drawn;
Transcribing, Completed and Failed send no meters, so the HUD froze on screen
and never reached its fade out.
`polled_at` records when the last poll ran, and the timer now arms when a frame
drew after it as well as when `last_drawn` is within RESHOW_AFTER. A failed
show still stops: its start arms once, and the 250 ms budget then ages out. A
hide clears the poll stamp with the rest.
Also word the `armed` field as the last poll's answer, test both per-OS
special-keys summaries against every translation table on every OS, and note
that Windows tests run only in the dispatched Check Windows workflow.
* labs: card titles, lines and OSes in the registry, exported to site/src/labs.json (t1560)
* site: a page and a social card for every lab, generated from the registry (t1560)
* labs: the two newest labs on the website (t1560)
* ci: read release secrets from aws secrets manager
* ci: read the linux signing key from hex/release/RELEASE_SIGNING_KEY
* ci: hex's own aur and homebrew keys; the signing cert has no password
* ci: the signing certificate has no password
* ci: use the shared aur and homebrew keys
* docs: the shared homebrew deploy key is anomaly-release
* docs: the shared homebrew deploy key is anomaly-release
* site: own /hex/files, drop the r2 write credential (#1611)
* site: own /hex/files for installers, appcast, and dev notes
The site build now copies install-linux.sh, install-windows.ps1, and
packaging/macos/legacy-appcast.xml into its Worker assets, so the same
Worker serves them at /hex/files with the Content-Type and Cache-Control
the bucket objects had. The Installers and Legacy appcast workflows,
r2-put.sh, and their R2 write credential are gone.
The dev notes move to the one-commit dev-notes branch, published by
Release's dev-notes job with GITHUB_TOKEN only; the Worker proxies that
file at /hex/files/dev-notes.json (falling back to the bucket copy until
the first dev release creates the branch) and renders /hex/dev from it.
Both site Workers now bind hex-production-files, read-only in code, for
the frozen 2.3.1 feeds and artifacts, which lets hex-dev-files go. The
Site build runs the installer test and appcast check the removed
workflows ran, and the verify job compares the served bytes.
* docs: the site owns /hex/files and needs no R2 write credential
Hosting, secrets, old clients, and Linux packages describe the built
installers and appcast, the dev-notes branch, and the read-only bucket.
strobe 0.13's ctx.addInitScript works in Chromium and Firefox; ctx.playwright is Chromium's. Chromium behaviour is unchanged (count.frame 82 for the idle head).
docs/perf.md and site/README.md: authors write their own text; strobe report experiment <exp> --format pr --update-pr <n> places strobe's generated block. Window cases expect the Hex title and their pane's heading, the site bench its page title and address, so a block on another screen is refused WrongScreen.
Import the bench SDK from @hona/strobe (the old @hona/strobe-bench name is deprecated). The idle head reports canvas.frames and canvas.interval.p95, the show's own WebGPU frames at its own rate, and the load case gpu.compile. Vite emits hidden source maps when strobe builds (STROBE_SOURCEMAP=hidden), so profiles name source lines; deploy builds are unchanged. Docs: any commit works as --base now (strobe overlays head's harness), report --format pr for PR tables, and large seeds are shared read only.
* Transforms get fetch and node:child_process behind a trust prompt
* Avoid fetch_update, deprecated on newer Rust
* Give the output-trust scene a playground path
* Dev builds say what's new: notes from PR titles in the dev feed, /hex/dev, and Restart to update (#763)
* Dev notes: keep ReadyToRestart's wire format; canonical upload; script and refetch fixes from review
* Sidebar update in its own module (code-shape)
- WebGPU: upload changed atlas rects through a small staging canvas, once each per
frame, instead of copying from the 4096² atlas (each copy snapshotted the whole
canvas); the canvas is opaque, so it says so.
- Canvas 2D: cut each shard's face from the card atlas once instead of clipping the
card twice a frame per shard.
- Screen break: settled cracks keep their paths, styles and crater gradient; the
idle glass layer leaves the layout.
- Make the AudioContext when the visitor reaches for the key, stop the hidden
keycap glow, and drop the unused motion wrapper (~24 KB gzip of first-load JS).
* Lowercase release file names; README downloads by channel (#456)
Release builds and the GitHub release mirror now name files hex-<version>-macos-arm64.{zip,dmg}, hex-<version>-windows-<arch>.exe and hex-setup-<version>-windows-<arch>.exe (Linux was already lowercase), as @vixalien asked in #456. Already-published files and the frozen 2.3.1 feeds keep their names; the release service's published names (hex, Hex.dmg, Hex.zip, hex.exe, HexSetup.exe) and the bundle (Hex.app) are unchanged, so the updater, installers, Homebrew cask, AUR and Nix are unaffected.
The README downloads table has Stable and Dev columns for every target, including the updater files. The site Worker serves /hex/download/dev/<target> (the dev alias) beside /hex/download/<target> (stable, or dev while there is none), and both now cover the bare updater files.
* Lowercase names in two remaining examples
* Lowercase the Windows executable in the CPU check step
* Site: slide the OS tab pill and keep the install stack's height
The selected OS tab's background now slides between tabs instead of jumping, and every OS's install stack shares one grid cell so the tallest (Linux) reserves the height. Switching tabs no longer moves the headline, the head, or the footer.
* Site: equal-width OS tabs, at most three install rows, and an Intel Mac notice
The OS tabs share one width, so the pill keeps its size as it slides. The Windows installers become one row with an x64/ARM64 switch, and Linux becomes Script, Package (Debian, Fedora, Nix, AUR) and Binary with an x64/ARM64 switch the packages follow, which gives Linux visitors the architecture choice they lacked. Commands beside a switch wrap to their own line on phones, and below 360 px the switch moves under the label. An Intel Mac sees that Hex requires Apple silicon instead of a download that won't run, restoring the notice the OS-tab rewrite dropped.
---------
Co-authored-by: kitlangton <7587245+kitlangton@users.noreply.github.com>
The site's download buttons and the README/docs links name /hex/download/<target>, which the site Worker redirects per request to the release service's stable alias once stable.json exists and to the dev alias until then, so nothing needs switching back. The page labels the build ("Dev build 0.0.0-dev-N", with a note that it updates from the Dev channel) and refreshes the version from the live manifests. The Linux button names the site's own install-linux.sh. The anomalyco/homebrew-tap cask now installs the dev alias (version :latest, sha256 :no_check, auto_updates); the Release workflow's stable Homebrew job replaces it with a versioned cask at the first stable release.
From the 2026-10-29 security review:
- H1: Release signs each Linux executable with Anomaly's ed25519 key (HEX_RELEASE_SIGNING_KEY, .github/release/sign-linux.sh, which refuses a key that does not match linux-signing.pub) and publishes the signature as the linux-<arch>-sig target. The updater (updater/linux.rs SIGNING_KEY) and install-linux.sh refuse an executable without a valid signature over its SHA-256, before downloading it. Installed builds that predate this ignore the extra target, so the transition needs nothing from them.
- H3: the installers move to the locked .github/release/ (CODEOWNERS @thdxr); the Installers workflow publishes them from a sparse checkout of that directory.
- M1: the release service client is vendored as .github/release/release-client.sh instead of piping anoma.ly/release/client.sh into bash.
- M2: check-windows.yml gets permissions: contents: read; every third-party action is pinned by SHA.
- M3: resolve_url accepts only URLs on the manifest's host.
* 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
Security finding #528: Site ran site/ code (bun install, build.ts, vite)
in the release environment with a Cloudflare token that can write every
Worker. Site deploy now builds without an environment or secret, uploads
the Build Output with its SHA256SUMS digest, and deploys it from a job
that checks out only .github/release/, verifies the digest, and runs
deploy-site.sh: it refuses any Worker, route, or binding other than the
mode's site Worker and deploys with the cf CLI locked in
.github/release/cf/. Legacy appcast checks out only .github/release/ and
the appcast, and r2-put.sh moves under the boundary.
The deploy token is now hex-site-deploy (Scripts + anoma.ly Routes, no
R2) and the appcast key hex-r2-production-files (one bucket).
Release no longer runs on tag pushes; stable is a dispatch from production only and refuses a version already tagged v<version> or app-v<version>. After every platform and the release service published, a tag job pushes v<version> on the released commit with the release deploy key (HEX_RELEASE_TAG_KEY, admitted by the new v* tag ruleset), then the GitHub release mirrors the files on that tag; a failed run leaves no tag. A check run pushes and deletes a throwaway v0.0.0-test-<run> tag to prove the ruleset admits the key. The release environment now admits only dev and production.
dev.anoma.ly/release only tests the release service itself. The staging channel is gone: channel=check builds, signs, and verifies without publishing, and builds are tested before stable on anoma.ly/release's dev channel. The site (both environments), the Windows installer test, and the publish script read only anoma.ly/release. The installers take HEX_INSTALL_CHANNEL=dev to install the newest dev build onto the Dev update channel.