Module login_flow 

Driving login from inside serve, so an assistant can walk a user through it.

The point is that a model can start the flow and relay the instructions itself, rather than telling someone to go and find a terminal. Credentials are still never automated: all this does is put a browser in front of the human and watch for K-Ruoka to start reporting an account.

It runs the existing login subcommand as a child process rather than growing a second browser mode inside serve. Two reasons: a profile directory supports only one Chrome, so serve has to let go of it anyway (see Session::release_for_login), and the subcommand already handles the parts that were awkward to get right – the xvfb re-exec, the separate tab for the human, the poller, and the graceful close that makes the cookies persist.

Structs

ChildLogin

LoginProgress

Traits

LoginFlow

What the login tools need. A trait so the tool surface can be tested without spawning a browser, the same reason crate::browser::KrApi is one.