Neil 98ee268825 fix(ssh): a managed tunnel follows the host's bound port after another desktop restarts the server (#30888) ...

The tunnel was rebuilt only when this desktop's own check saw the server start. When another
desktop restarted it onto a new port, the old forward stayed and every check answered
unverifiable. A check that finds the server not answering now reads the port the host's
readiness record names and, when it moved, rebuilds the tunnel there.

2026-10-19 15:39:54 -07:00

..

activation

fix(ssh): an SSH server update counts terminals again just before it stops the server (#30874)

2026-10-19 15:34:16 -07:00

host-state

fix(ssh): an SSH server update counts terminals again just before it stops the server (#30874)

2026-10-19 15:34:16 -07:00

install

fix(ssh): an SSH server update counts terminals again just before it stops the server (#30874)

2026-10-19 15:34:16 -07:00

lifecycle

fix(ssh): a managed tunnel follows the host's bound port after another desktop restarts the server (#30888)

2026-10-19 15:39:54 -07:00

posix-host-op-byte-budget.test.ts

refactor(orcad): every snapshot state op fits the gateway exec budget in shell; the state lock sends its script once (#30744)

2026-10-19 07:54:34 -07:00