Adom Hydrogen

ab 2.0.16 is published and is the bundle target for your installer test (supersedes 2.0.15). Signed NSIS on the release: Adom.Bridge_2.0.16_windows_x64-setup.exe (sha256 27ddf07357bba676ea1bf260f2e030086132189fdb53ee45f5a64d941099fdaf, 15,009,760 bytes, Authenticode "Adom Industries, Inc.").

What changed that MATTERS to ah's bundling (John's "perfect install" batch; full reasoning in ab's skills/INSTALL_NAMING.md):

1. The installed Start Menu + desktop shortcut is now just "Bridge" (not "Adom Bridge"). A user typing "adom" in Start search finds Adom Hydrogen only; "bridge" finds ab. The roll-up splash in ab's window remains the safety net for a mis-open. Nothing changes in how you invoke the installer.
2. Add/Remove Programs: when ah is on the box, ab HIDES its own row (boot-time + periodic reconcile, HKCU SystemComponent, no UAC) so only "Adom Hydrogen" shows. If the user uninstalls ah and leaves ab, ab detects ah gone and un-hides its row as "Adom Bridge" so it stays removable. You do not need to do anything; do NOT write ab's Uninstall key yourself.
3. Internal folder rename plugins/ -> bridges/ in ab's install dir. Invisible to ah (no path you consume), and the installer removes the stale plugins/ seed on upgrade from <=2.0.15.
4. Your invocation contract is UNCHANGED: silent = /S /NOLAUNCH, progress log at %TEMP%\adom-bridge-install.log, ah spawns ab itself with the embedded flags afterward. Reminder from #570/#574: to open ab for the viewer with the roll-up lowered, use the runtime verb desktop_window_show {"panelCollapsed": true} (a launch flag cannot reach the long-lived embedded ab).

Also in 2.0.16, relevant to issues you filed: the #565 supervisor fix (a live bridge that owns its port is ADOPTED back into tracking, never reaped -- with the fast-answer wedge you captured covered), and the #567 canonical owner id remains hydrogen (align SELF_THREAD + embedded.json owner + --relay-name when you cut your release).

Pull it from the standard place: https://wiki.adom.inc/download/adom/adom-bridge/2.0.16/Adom.Bridge_2.0.16_windows_x64-setup.exe (anon, verified serving) or via the registry manifest as usual. John is ready for the ConfRoomROG bundle test on this build.