DEPRECATED: Adom Bridge Control (moved into Adom Bridge)

@@ -33,12 +33,20 @@ pack of tested patterns, each one distilled from a real session, each labeling  ## The cross-cutting rules (true on every surface) -- **Background by default. Never steal the user's focus** unless you must. CDP eval-  (`nbrowser_eval`/`browser_eval`), UIA Invoke (`desktop_ui_click`), and-  `desktop_screenshot_window` all run on a BACKGROUND window. Only OS SendInput-  (`desktop_click`/`desktop_type`/`desktop_press_key`) needs the window foregrounded,-  so avoid it when a CDP/UIA path exists. (John: "browser windows should always be in-  the background so as not to disrupt the user's other work.")+- **Background by default. Foregrounding the user's window is RUDE, it interrupts their+  work.** There is almost always a background path, use it:+  - CAPTURE: `desktop_screenshot_window` (PrintWindow) and `desktop_record_window_start`+    (WGC) both grab a window even when it's occluded/off-screen. **NEVER** reach for+    `desktop_screenshot_screen` (fullscreen) or `desktop_bring_to_front` just to take a+    screenshot, that steals focus for zero reason. (John, repeatedly: foregrounding+    Fusion/Chrome to screenshot is "so rude... disrupt my work.")+  - INPUT: UIA verbs act in the background, `desktop_ui_click` (Invoke), `desktop_ui_set`+    (SetValue), `desktop_ui_scroll`, `desktop_ui_toggle`, `desktop_ui_select`. Drive a+    control by accessible NAME, no focus steal.+  - Only OS SendInput (`desktop_click`/`desktop_type`/`desktop_press_key`) and+    `desktop_screenshot_screen`/`desktop_bring_to_front` foreground. Reserve them for the+    rare case a control genuinely isn't in the UIA tree AND can't be reached via CDP.+    (A verb-level hint reprimanding gratuitous use of these is filed with AD/Colby.) - **Drive it yourself, including login. Never ask the user to click or log in.** You   can drive their real browser end to end, including OAuth, see native-browser-control. - **Upload files via DataTransfer, not the OS file picker.** Inject the bytes into the

@@ -4,7 +4,7 @@   "type": "skill",   "title": "Adom Desktop Control",   "brief": "Drive the user's real desktop from the cloud: their Chrome/Edge, headless pup, native UI, the Hydrogen editor, sibling Claude tabs, plus screen recording and video post.",-  "version": "1.1.0",+  "version": "1.2.0",   "description": "A skill pack of hard-won, tested patterns for driving an Adom user's actual machine from the cloud AI through Adom Desktop: their real logged-in Chrome/Edge via the browser extension (CDP), headless pup browsers, native UI via UIA and SendInput, the Hydrogen web editor, sibling Claude tabs, and a full screen-recording + video post-production pipeline. Every skill is distilled from real sessions and labels what works, what fails, and why.",   "org": "adom",   "dependencies": {},

@@ -4,7 +4,7 @@   "type": "skill",   "title": "Adom Desktop Control",   "brief": "Drive the user's real desktop from the cloud: their Chrome/Edge, headless pup, native UI, the Hydrogen editor, sibling Claude tabs, plus screen recording and video post.",-  "version": "1.1.0",+  "version": "1.2.0",   "description": "A skill pack of hard-won, tested patterns for driving an Adom user's actual machine from the cloud AI through Adom Desktop: their real logged-in Chrome/Edge via the browser extension (CDP), headless pup browsers, native UI via UIA and SendInput, the Hydrogen web editor, sibling Claude tabs, and a full screen-recording + video post-production pipeline. Every skill is distilled from real sessions and labels what works, what fails, and why.",   "org": "adom",   "dependencies": {},