Provider reauthorization remains on the OAuth start screen

[Aaronontheweb]

Problem

The Provider Manager can remain on Starting device authorization... after an OAuth reauthorization starts.

The OAuth coordinator advances its state and requests a redraw. The keyed provider layout reuses the original OAuth child because its key does not include the state revision.

This defect hides the user code, authorization URL, success state, and error state.

Reproduction

1. Open netclaw provider.
2. Select an OpenAI provider with an invalid OAuth connection.
3. Start reauthorization with the ChatGPT subscription option.
4. Observe that the page remains on Starting device authorization....

Expected behavior

The page shows the authorization URL and user code after the OAuth request starts.

Acceptance criteria

• The OAuth device-flow page refreshes after each visible state transition.
• The page shows the user code and authorization URL.
• OAuth success and error states replace the start screen.
• A headless TUI test covers the start-to-user-code transition.