Review on #132010 (Enough1122): the kind passthrough preserves
'interactive-auth' — the one SSH_ERROR not in TRANSPORT_KINDS — but no
part of the renderer chain had a slot for it. Both gateway-settings
errors tables collapsed it to the generic 'SSH connection failed.'
via the || sshErrUnknown fallback, losing the actionable 'run
ssh <host> true' Tailscale browser-check guidance that
ssh-connection.ts:471 composes. Add 'interactive-auth' to both tables,
the sshError union (global.d.ts), and a dedicated sshErrInteractiveAuth
key in all bundled locales + types, with a renderer regression test
that is red on the passthrough alone.
Also correct the test enumeration comment: exec() passes no
AbortSignal, so 'superseded' cannot reach this catch today (pinned
anyway as a sentinel contract), while 'interactive-auth' can and does.
71ddc56792