# Separate Shared Auth0 Readiness From Session Readiness

The mandatory Remote Dev full UI slice has layered readiness instead of one undifferentiated bit. Its session-owned static file server participates in `session_ready`. The shared `tidb-dev` Auth0 allow-list preflight participates through `ui_auth_ready`, and the prepared seed Account binding participates through `ui_identity_ready`; both feed aggregate `ui_ready` and browser acceptance, but neither identity failure denies readiness to an otherwise-valid backend session. This preserves a usable, potentially expensive Remote development environment when identity configuration drifts, while still refusing to claim that browser login works.