Adom Hydrogen (macOS)

We cannot tell which app a new sign-up came from when it is the Mac app (John, 2026-11-02: "we keep running blind on whether it's the windows hydrogen or Mac hydrogen that isn't succeeding when we get new sign ups").

What Windows Hydrogen does that the Mac app does not:

1. Passes its install ID into the sign-in. Adom Bot's sign-up post shows an "Install:" line for every Windows sign-up. Mac sign-ups have none.
2. Reports the sign-in right away. Windows sends a fleet event within seconds of sign-in, with the username. The Mac app only pings on its update check (launch, then every 4 hours). That first ping usually happens before the person signs in, so it carries no username, and the fleet first learns who they are up to 4 hours later.

Ask:

• Pass the Mac install ID on the sign-in/sign-up link the same way Windows does, so Adom Bot's post carries it.
• Send one fleet ping (product: hydrogen-macos, os: macos, username, user_id, install_id) as soon as sign-in completes, in addition to the update-check pings. The fleet service contract allows pings at setup steps; this is the Mac sign-in step.
• Include install_id in every Mac fleet ping (today it is empty).

Example: jsn.gao07 signed up 2026-11-02 22:41 UTC with no Install line and no report from any Hydrogen. The fleet's new 🧭 post can only say "most likely the Mac app or the website".

The fleet side is done: adom/service-fleet 0.12.0 posts which app every sign-up came from, and posts an update when the Mac report arrives. Once this lands, that update will come within seconds instead of hours. Linux Hydrogen should follow the same contract from its first release.