just install confirms the new hub-daemon started, or says macOS refused to start it #361

Current state

After just install replaces hub-daemon with a changed build, signals stop for over a minute while nothing says why. The install prints restarted hub-daemon and exits successfully, but macOS kills the first start of the new binary with last exit reason = OS_REASON_CODESIGNING. On 2026-10-17, launchd's next start came 79 seconds after the install and ran normally, with nobody touching anything. An install whose binary had not changed started at once. Whether macOS ever refuses for longer, and what it shows when it does, has not been seen.

Ideal state

• just install reports success only once the new daemon has started under launchd: a start line from a new pid
• When macOS refuses to start the new daemon, just install says so plainly

Decisions

Constraints

• 020 — Hub runs an unattended surface — the daemon is the surface that keeps signals arriving, so a daemon that fails to start after an install has to be noticed then

Open

No open decisions.

Starting points

• scripts/src/daemon_agent/command.rs — restart_if_running, which just install calls, and the launchctl steps it runs
• scripts/src/daemon_agent/plan.rs — the steps a restart takes, including kickstart -k