Release v2.32.2

Signing up ended on an empty white page. The registration flow sends the signed-in user to the lobby's own registration page, which is served behind AuthProxy at the same /register path, but AuthProxy still treated that request as one of its own flows and cleared the route that forwards it. Nothing answered it, so the browser got an empty 404.

Fixed

• A signed-in user on /register with no registration pending is forwarded to the service behind the proxy, so the lobby's registration page loads after signing in. Anonymous callers and pending registrations are still answered by AuthProxy, and invitations are unchanged.