The Browser Harness daemon reads BU_CDP_* once, when it starts, and lives
across calls. The connect/disconnect swap reaps browsers through
cleanup_all_browsers(), which never stopped those daemons, so every
browser_exec after the swap kept driving the browser from before it while
the command reported the new endpoint. Since #125995 ships browser-harness
in every install, Browser Use is the default driver on Desktop too.
browser_exec now records each BU_NAME it drives, and
cleanup_all_browsers() stops them through the harness's own
identity-checked --reload; the next call respawns on the endpoint it
resolves.