Connection diagnosis blames the remote host for local session-pending and invents successful earlier hops #29338

What happened

On 0.1.6 a connection failure displayed:

This device: ok
T3 Connect: ok
Remote desktop tunnel: ok
T3 Code on Remote desktop: FAILED
Cause: session-pending
Error: Waiting for the T3 Connect sign-in to load.

It linked to the host-not-answering troubleshooting section, sending investigation toward host ports, tunnels and restarts.

Diagnosis

getDpopToken emits session-pending when this client's cloud identity is missing, before remote authorization. In diagnosis.ts, locate() falls back to the server hop for any failure without a hop except network/timeout/transport. session-pending takes that server fallback. presentConnectionDiagnosis() then marks every earlier hop ok based solely on its position before the failed index. Those green entries are not independent successful probes.

Deterministic reproduction

Pass presentConnectionDiagnosis a relay-route state whose lastFailure is ConnectionTransientError with reason session-pending, the existing loading detail, and no explicit hop. Inspect headline, hop results, and help URL. No actual broken server is needed.

Expected

Classify this as local session initialization and provide a local sign-in loading/retry/reload explanation. Preserve unknown/not-checked status for hops that have not been verified. Avoid presenting inferred ordering as tested connectivity. Add focused diagnosis tests for this reason and hop-evidence handling.

Environment and evidence

Observed in Windows desktop 0.1.6 connecting to Windows desktop 0.1.6. Reloading the client restored session initialization; the user confirmed reconnection.

Source inspected at the installed release:

• https://github.com/pingdotgg/t3code/blob/v0.1.6/packages/client-runtime/src/connection/diagnosis.ts
• https://github.com/pingdotgg/t3code/blob/v0.1.6/packages/client-runtime/src/authorization/service.ts

Related: #11004 describes the earlier sign-in-changed wording, not this diagnostic hop fallback and inferred green-hop display.

Filed by gpt-6.1-sol through the Codex harness in T3 Code. User authorized filing these reports after confirming recovery.