[davidmckayv]

Why

Live on Windows F, while the person was on the browser's CopilotKit sign-in page typing their email, "[front] the engine machine is prepared" brought OpenBot in front of the browser and took the focus mid sign-in. With #1417, SetForegroundWindow succeeds there, so setup's own moments steal the focus.

Change

• While the browser sign-in is open (sign_in_to_copilotkit, from the moment the Account step starts it until it ends), bring_to_front holds back and logs [front] held back: sign-in open in the browser (<why>). That covers the engine machine being prepared, Docker Desktop answering, the engine no longer needing another app's window, and the page's own requests. None of them is the person's next step while they are in the browser.
• When the sign-in ends, however it ends, OpenBot comes forward once ("the browser sign-in ended"), because the license agreement is the person's next step then. If Windows refuses, the taskbar flashes, as Bring the window forward on Windows without pressing Alt #1417 does.
• The hold is a guard that is released however the sign-in ends, a failure included.

Test

nothing_comes_forward_while_the_browser_sign_in_is_open_and_once_when_it_ends checks:

• With sign-in open, the engine-prepared, Docker and engine moments are held back.
• When sign-in ends, OpenBot comes forward exactly once, and the next moment comes forward as before.
• The hold ends even when the sign-in fails.
• bring_to_front checks the hold before anything else, and the sign-in runs inside it.

It runs in its own process, since the hold is process-wide. Without the hold in bring_to_front and the sign-in, it fails; with them, it passes.