Neil 1772b455f6 fix(ssh): say what to do when a host's server setup stops on a known cause (#38508) ...

* fix(ssh): say what to do when a host's server setup stops on a known cause

A managed SSH host whose server setup deferred always showed "Orca couldn't
start its server on this host. Try connecting again.", even when a retry
can't help (full disk, an interrupted update needing Recover, another Orca
runtime on the host's data). The deferral code was dropped before it reached
the host status.

Carry the code as an optional field on the unserved status, keep the retry
line only for codes a later connect clears, and name the fix for the ones a
user can act on. Older hosts and thrown errors carry no code and keep the
retry line.

Refs #38347

* fix(ssh): drop the Recover advice a first setup can't act on

Connect already runs activation recovery before deploying, and an unregistered
host has no Recover control, so that code now points at Details. Soften the
live-runtime line, keep waiting causes in the warning tone, and test the
published code and its remedy rather than English copy.

Refs #38347

* fix(ssh): treat an unreadable server build as needing Details, not a retry

Refs #38347

2026-11-05 02:49:13 -08:00

..

src

fix(ssh): say what to do when a host's server setup stops on a known cause (#38508)

2026-11-05 02:49:13 -08:00

fixtures.html

…

index.html

…

popout.html

…

space.html

…

web-index.html

…