The background daemon refuses to start when a namespace collapses all users to one id.
What's wrong with this entry?
On Linux and macOS, the daemon start path now checks first for a user-namespace setup where every user collapses to the same id, and refuses to start with cause uid_collapse plus guidance to start with a uid map or pass a socket path explicitly. Windows skips the check entirely.
- Returns a failure result and records a telemetry event rather than launching and failing later.
daemon_ensure_running
Strings lifted out of the shipped bundle, so the claim above can be checked against them.