Google OAuth URL broken when initiated from Telegram channel

[sergeiest]

Description: When the agent initiates Google OAuth from within Telegram, the generated
URL contains a malformed parameter: clientid instead of client_id (missing
underscore). Google rejects this with "Error 400: invalid_request / Required parameter
is missing: response_type". The same OAuth flow works correctly when initiated from
the web chat interface.

Impact: HIGH — Google tool authentication is completely broken when triggered via
Telegram. Users are stuck and cannot proceed without switching to the web chat.

Reporter: Sergey

[henrypark133]

Additional Detail from Bug Bash Notes

From Sergey's session: The OAuth URL generated when initiated from Telegram contained clientid (no underscore) instead of client_id. The exact URL from the notes:

https://accounts.google.com/o/oauth2/v2/auth?clientid=491426360059-...

vs the working URL from web chat:

https://accounts.google.com/o/oauth2/v2/auth?client_id=491426360059-...

The URL also could not be regenerated when Sergey asked — the agent provided a stale/cached URL that no longer worked.