CRITICAL: Unhandled Promise Rejection! │ ========================================= │ Reason: Error: OAuth callback timeout │ Stack trace: │ Error: OAuth callback timeout │ at Timeout._onTimeout (file:///usr/local/lib/node_modules/@google/gemini-cli/bundle/

### What happened?

CRITICAL: Unhandled Promise Rejection! │ ========================================= │ Reason: Error: OAuth callback timeout │ Stack trace: │ Error: OAuth callback timeout │ at Timeout._onTimeout (file:///usr/local/lib/node_modules/@google/gemini-cli/bundle/chunk-7LQRUKPT.js:365572:29) │ at listOnTimeout (node:internal/timers:605:17) │ at process.processTimers (node:internal/timers:541:7)

### What did you expect to happen?

What's happen? there are lot of debug lines in my screen.

### Client information

* **CLI Version:** 0.52.0
* **Git Commit:** d14583b92
* **Session ID:** 91635fc7-e1ea-4ee3-8d44-0dcb6c97fc88
* **Operating System:** darwin v24.18.0
* **Sandbox Environment:** no sandbox
* **Model Version:** auto
* **Auth Type:** gemini-api-key
* **Memory Usage:** 583.4 MB
* **Terminal Name:** iTerm2 3.7.0beta7
* **Terminal Background:** #1a1a1a
* **Kitty Keyboard Protocol:** Supported

### Login information

_No response_

### Anything else we need to know?

_No response_

Start with the reported OAuth callback timeout in /usr/local/lib/node_modules/@google/gemini-cli/bundle/chunk-7LQRUKPT.js at line 365572, then determine why it becomes an unhandled promise rejection. Compare the observed debug output with the expected CLI behavior and verify that the timeout is handled without exposing excessive debug lines.

Written by the indexing model from the issue text.