e368c01e28
The Desktop SSH bootstrap proves the remote `hermes serve --isolated` alive (`kill -0 … && echo ALIVE || echo DEAD`) and owned (argv probe printing OWNED/FOREIGN) over the same SSH channel that is often mid-teardown right after the served token was resolved. Both probes treated ANY answer that was not the positive sentinel as the negative verdict, so an exec that resolved with empty output was read as death: the boot failed with "remote dashboard exited while its served token was being resolved", the post-spawn cleanup ran the ownership probe on the same channel, read the lost answer as FOREIGN, skipped the kill and removed the lockfile — one orphaned ~144 MB backend per failed attempt, ten in one session on a 1 GB host (#111810). `execProbeVerdict` now runs both probes: an answer that is neither sentinel is indeterminate and is retried over a short bounded window (3 attempts, 500 ms); with no definite answer it fails closed with a `transient-transport-error`, so `cleanupStale` keeps the ownership record for the next connect to reap instead of leaving a lockless orphan. The post-spawn catch probes liveness first so a child that genuinely died at startup skips the ownership proof and the original error ("exited before announcing") stays visible. Slimmer redo of #111828 by @kokhlo: same mechanism, without the parallel `verifyRemotePidAlive`/`verifyPidOwnership`/`readOwnershipVerdict` layer that left `remotePidAlive` and the original probe as dead duplicates. Fixes #111810 Co-authored-by: Konstantin Khlopkov <47825603+kokhlo@users.noreply.github.com>