Adom Bridge

Request: an Adom-branded overlay next to the REAL OS cursor whenever AD drives the mouse

Why (from John): when AD moves and clicks the real Windows cursor (via desktop_click / desktop_hover), the user should be able to tell at a glance that Adom is controlling their mouse — not Claude's browser extension, not malware, not a stuck cursor. Right now the OS cursor moves with zero attribution. This is a trust/safety feature: a user watching their mouse move on its own needs to know it's their Adom agent doing authorized work.

This came up doing real work: AD's desktop_hover-then-desktop_click is the ONLY thing that can drive Google's FedCM "Sign in with Google" account chooser (every in-page/CDP/UIA click is rejected), and it will be used heavily for hours-long autonomous tasks (e.g. downloading electronics libraries, clicking native Save-As dialogs). Users need persistent visible attribution during that.

What pup already did (the in-page half): the pup bridge (v1.9.164/165) injects a teal Adom cursor with a small Adom orbital badge for its in-page CDP clicks. But that only works inside a web page pup controls — it can't render over native dialogs, the taskbar, cross-origin FedCM iframes, or anything outside the DOM. The OS-level overlay is AD's to own because AD owns the SendInput path.

Proposed: a small always-on-top, click-through (WS_EX_LAYERED | WS_EX_TRANSPARENT | WS_EX_NOACTIVATE) overlay window that:

1. Shows the Adom logomark (teal 2p-orbital mark) pinned just off the cursor hotspot (e.g. bottom-right, ~16px), following the cursor whenever an AD-driven move/click is in flight.
2. Optionally a brief label/toast on the FIRST action of a burst: "Adom is controlling your mouse — <thread name / reason>" (the caller identity AD already has), then quiets to just the badge.
3. Appears only while AD is actively driving (a move/click within the last N seconds), auto-hides when idle so it never clutters normal use.
4. Respects the same foreground-etiquette AD already enforces (the badge is the visible consent signal the user sees when a window is foregrounded for a real click).

Nice-to-have: a subtle glide animation on the cursor move (like the pup in-page cursor and the nbrowser extension's animated cursor) so the motion reads as deliberate agent action, not a glitch.

Filed from the pup bridge maintainer thread; pup will link its in-page cursor to this so the two are visually consistent (same Adom mark) once AD ships the OS overlay.