Anton Panasenko 58be470d15 fix(remote-control): retry after auth recovery (#23775) ...

## Why

When remote control hits an auth failure such as a revoked or reused
refresh token, the websocket loop falls into reconnect backoff. If the
user fixes auth while that loop is sleeping, remote control can stay
offline until the old retry timer expires because nothing wakes the loop
or resets its exhausted auth recovery state.

## What Changed

Added an auth-change watch on `AuthManager` for refresh-relevant cached
auth updates.

The remote-control websocket loop now subscribes to that signal, resets
`UnauthorizedRecovery` and reconnect backoff when auth changes, and
retries immediately instead of waiting for the previous delay.

Updated the remote-control transport test to verify that reloading auth
with the now-available account id wakes enrollment before the prior
retry delay.

## Verification

`cargo test -p codex-app-server-transport
remote_control_waits_for_account_id_before_enrolling`

2026-05-21 14:38:30 -07:00

..

src

fix(remote-control): retry after auth recovery (#23775)

2026-05-21 14:38:30 -07:00

BUILD.bazel

app-server: move transport into dedicated crate (#20545)

2026-05-01 09:23:47 -07:00

Cargo.toml

Restore app-server websocket listener with auth guard (#22404)

2026-05-12 18:40:53 -07:00