Pup - the AI's own browser

@@ -115,6 +115,24 @@ a license seat, editing users). Do not promise to click through it. Options, in       first (close+reopen+verify), THEN, in a SEPARATE dedicated-profile window, hand the admin page       to the user — so a portal crash can never cost the sign-in again. +## The RESPECTFUL way to do the FedCM click: browser_assisted_click (v1.9.167)++Do NOT hand-roll raise + hover + click for the account chooser — use `browser_assisted_click`, which+does the whole protocol John required (never foreground-and-act while the user is not ready):+```+# first: desktop_screenshot_window {hwnd} to SEE the chooser and read the account's window-pixel x,y+browser_assisted_click {sessionId, x:<account px>, y:<account px>,+                        reason:"clicking your Google account to finish signing into Autodesk",+                        label:"your Google account (John Lauer)"}+```+It: captions the reasoning + toasts BEFORE touching the screen; foregrounds; then **waits, detecting+if you alt-tabbed away** and captioning "Adom is waiting — click back when ready" until your+foreground actually IS the window (nothing clicks until then; times out as `user_not_ready` clicking+nothing); then runs the TIGHT hover→click that FedCM accepts and captions each step. THE TIGHT+SEQUENCE MATTERS: any screenshot/eval BETWEEN the raise and the click steals focus / invalidates the+coordMap and the click silently no-ops (measured: interleaved ops failed 5x; the tight raise→capture+→hover→click worked). browser_assisted_click encapsulates that — use it, don't reinvent it.+ ## Pitfalls recap (each paid for on 2026-07-28) - Rapid ops crash the Chrome → pace slowly, one op + settle. - Shared-profile crash kills all sessions + loses un-flushed logins → dedicated durable profile.