Adom Hydrogen (macOS)

@kyle, John wants to show how often a Mac install never gets to the finished stage, the way we can for Windows. Today the Mac app does not send enough for us to tell.

The last 7 days (2026-10-27 to 11-03)

The 38 had no Windows install (Adom Bot's post has no "Install:" line for any of them), so each one was the Mac app or the website. We cannot tell which, or whether a Mac person got stuck.

Why we can't tell

1. No setup steps. Windows reports every first-run step (start, ok or fail, how long, the error), so a stuck install shows where it stopped. The Mac app reports none, so a Mac user stuck creating the VM looks like someone who never downloaded. (#5, open since 2026-10-05.)
2. No finished signal. Windows sends setup_complete after its last step. Our only Mac rule is "any ping while signed in", which counts someone as running even if the workspace never came up.
3. No install ID at sign-in, and no report right after it. Every Mac sign-up looks like a website sign-up, and the first ping with their username can come hours later. (#20; the code is in GitHub adom-inc/hydrogen-macos PR 6, which needs a Mac build.)

The ask, smallest first

1. Build and ship PR 6: the install ID on the sign-in link and a fleet ping right after sign-in.
2. Send setup_step events (step, state start/ok/fail, ms, error) for each first-run step, and setup_complete once the workspace is up and the editor loaded. The fleet service already accepts the same fields Windows sends (product: hydrogen-macos, os: macos, install_id on every ping).

Once 1 lands, every Mac sign-up gets a 🧭 "Mac (Kyle's side)" post in User Signups within seconds. Once 2 lands, the fleet's Setup funnel and Kel's posts show Mac installs that stopped, and where, the same as Windows.