Definitions

John ordered the binary rename today: the exe name is user-visible (About install path, Task Manager, autostart) and external surfaces must say Hydrogen.

LANDED app-side (hydrogen-desktop repo, commit 90bd62d1):

• cargo bin name = hydrogen -> target builds hydrogen.exe. The cargo PACKAGE stays hydrogen-desktop (internal id; the frozen family: state dir %APPDATA%\hydrogen-desktop, bundle id inc.adom.hydrogen-desktop, GitHub repo name).
• NSIS hooks: PREINSTALL taskkills old-name processes and deletes the old exe from $INSTDIR (the NSIS kill-running-app step only knows the NEW binary name, so upgrade-over from a pre-rename install handles the old one explicitly); POSTINSTALL delegate + autostart write use hydrogen.exe and Run value name 'Adom Hydrogen'; UNINSTALL removes both Run value names.
• Updater staged-relaunch path -> %LOCALAPPDATA%\Adom Hydrogen\hydrogen.exe.
• Dev/test scripts + repo docs swept.

ROWS FOR OTHER THREADS:

1. BRIDGE THREAD: the hd_* dev verbs hardcode the old binary (hd_stop taskkill /IM hydrogen-desktop.exe, hd_launch / hd_ship / hd_build_status exe paths under target/debug|release). Flip them to hydrogen.exe - hard cutover, no fallback name, per the rename policy. Until flipped I am launching via run_script Start-Process as the stopgap on ADOMLAPPER.
2. KYLE (mac): rename the mac binary in parallel so the family ships one binary name. Same frozen-family rule applies (state dirs, bundle ids unchanged).
3. Release scripts: installer artifact names are productName-derived ('Adom Hydrogen_*') - unaffected. The artifact-name check on the next real release still stands.

Upgrade-over behavior: same productName + bundle id, so the old uninstaller runs during upgrade and removes hydrogen-desktop.exe; PREINSTALL belt-and-suspenders covers a running old-name process. Old installs' autostart values self-heal on first launch of the new exe.