browser-automation

Use `bb browser-automation`. Open one session, retain its session ID, then inspect, act, and verify in short scripts. Choose `--backend local --headless --machine <host-id>` for headless Chrome on an enrolled host. Choose `--backend desktop --machine <host-id> --desktop <instance-id>` for a new dedicated desktop automation tab. Starting desktop control opens the side panel and selects the browser tab only if its thread is already focused. New or activated controller pages follow the same rule; automation does not switch threads or bring the desktop window forward. Headless sessions remain headless. Plugin-owned local/headless Chrome launches with `--no-sandbox`, disabling Chrome's sandbox. Desktop attachment does not change the browser's launch flags. Resolve the explicit instance with `bb browser instances --host <host-id> --json` first. Never silently choose a different host, mode, or login profile. Adding `--tab <tab-id>` hands off an existing tab and its profile's logged-in authority; do so only when the user asked to use that tab. The CLI uses the current thread, or `--thread <id>` outside a thread. Each session belongs to that thread. CLI opening: ```sh bb browser-automation open --backend local --headless --machine <host-id> --json bb browser-automation open --backend desktop --machine <host-id> --desktop <instance-id> --json ``` Run scripts: ```sh bb browser-automation run <session-id> --script 'const p = await browser.getPage("main"); await p.goto("https://examp...