[Bug] Mobile Remote Control pairing fails with "upstream object error" after QR refresh — relay stalls at waiting_terminal (3.14.4, macOS)
已打开 06:02PM - 30 Sep 26 UTC
priority: P2
## Environment
- ZCode Desktop **3.14.4** (3.14.4.7912), macOS, Apple Silicon
- …Date: 2026-09-30, local times below
- Relay endpoint: `wss://zcode.z.ai/ws`
## Symptom
Pairing a phone via Mobile Remote Control (QR code or link) shows **"upstream object error"** on the web page, every time. Opening the same pairing link in a **desktop browser on the same Mac** reproduces the identical error — so this is not a phone/network issue.
## Timeline from desktop log (`~/.zcode/v2/logs/2026-09-30.log`)
1. **13:20:52** — pairing **succeeded**: `state-transition: authenticating → paired`, `pairStatus: matched`, relay device state `paired`.
2. **13:25:24** — QR refresh: `auth reset {"reason":"leaked-qr"}` + `auth cleared`.
3. **13:25:25 onward** — every subsequent pairing attempt: relay reaches `connecting → authenticating → waiting_terminal` in <1s and then **stalls at `waiting_terminal` indefinitely**. The connecting page errors with "upstream object error".
4. **13:49:56 / 13:50:46** — module restart (`reason=restart`) and manual stop/start with fresh QR codes — same stall, no recovery.
## What the desktop log does NOT show
- Zero `[error]`-level lines related to web-remote-control (only benign auto-updater errors).
- Zero `mobile diagnostic` events after 13:20 — the phone/browser failure never reaches the desktop process.
## Analysis
Pairing worked once *before* the QR refresh; every attempt *after* the `leaked-qr` auth reset fails at the same step. The web-side pairing validation appears to hit a wedged relay-side pairing state for this device. Nothing client-side recovered it (fresh QR, module restarts, multiple browsers).
Suspect the relay-side pairing/auth state for the device was corrupted by the `leaked-qr` reset. Could you check/clear the server-side state for this device? Happy to provide the full log file or my device sid suffix privately.
## Workaround attempts that did NOT help
- Fresh QR (multiple), refresh link
- Stopping Remote Control in all other windows
- Opening link in desktop browser, phone on cellular vs Wi-Fi
