Thanks for the focused launchd restart fix. I verified the premise still exists on current main: launchd_restart() returns immediately after _request_gateway_self_restart(pid) succeeds at hermes_cli/gateway.py:3667-3669, and the current test still asserts launchctl should not run in that path at tests/hermes_cli/test_gateway_service.py:697-718.

Problems

• The new fallback helper in this PR only treats launchctl exit codes 3 and 113 as an unloaded job. Current main now intentionally treats 125 as unloaded too, and falls back to detached background launch when launchd cannot manage the domain (5/persistent 125) at hermes_cli/gateway.py:3209-3218 and hermes_cli/gateway.py:3683-3706. A salvage should preserve that newer handling while adding the relaunch verification.

Suggested changes

• Integrate the relaunch/new-PID wait into current main’s launchd_restart(), but reuse _launchd_error_indicates_unloaded() and _launchctl_domain_unsupported() rather than hard-coding {3, 113}.
• Update tests/hermes_cli/test_gateway_service.py:697-718 so the successful self-restart path verifies relaunch behavior instead of asserting launchctl is never invoked, and keep coverage for the current 5/125 detached fallback.

This is an automated hermes-sweeper review.