Adom Hydrogen (platform base)

@@ -17,8 +17,8 @@ description: >   screenshot, open a file on my computer, control my desktop, bridge to my pc,   send file to my desktop, pull file from my desktop, ah and ab, two apps, how   do ah and ab work together, talk to hydrogen desktop, desktop bridge, relay,-  embedded mode, ab hidden, hd_status, hd_api, shell_execute, adom-bridge-cli ping,-  adom-bridge-cli status.+  embedded mode, ab hidden, hd_status, hd_api, shell_execute, adom-bridge ping,+  adom-bridge status. ---  # Hydrogen ↔ Adom Bridge — your reach onto the user's real machine@@ -70,13 +70,13 @@ Here's the subtlety that matters when you reason about "who serves this verb?":    `desktop_record_*`, `desktop_recorder_*`, `desktop_list_monitors`,    `desktop_pull_glob`, `desktop_embedded_*`. -Both ends sit behind the same `adom-bridge-cli` relay, so from the CLI you don't+Both ends sit behind the same `adom-bridge` relay, so from the CLI you don't choose between them — the relay routes to whichever client is connected. But "will this verb work right now?" depends on which client is up. **Don't assume a verb exists — verify capability first:**  ```bash-adom-bridge-cli status   # → .capabilities lists what the connected client(s) can do+adom-bridge status   # → .capabilities lists what the connected client(s) can do ```  If `.capabilities` is missing `record` (or `desktop_list_monitors` errors with@@ -87,7 +87,7 @@ the KiCad/Fusion/browser bridges all work off Hydrogen's built-in bridge regardl  ## What ab/Hydrogen let you do on the user's real Windows machine -All via the `adom-bridge-cli` CLI from inside the workspace. Rather than+All via the `adom-bridge` CLI from inside the workspace. Rather than re-document every verb here, this is a **capability map → the focused skill**:  | Capability | Verb(s) / surface | Where it's documented |@@ -103,10 +103,10 @@ re-document every verb here, this is a **capability map → the focused skill**: | **Drive KiCad / Fusion 360 / Pup** | `kicad_*`, `fusion_*`, `browser_*` | the platform bridge skill set (**hydrogen-bridges** on Windows, the adom-bridge-macos skills on mac) | | **Embedded mechanics (tray/lifecycle)** | `desktop_embedded_*` | **hydrogen-embedded-bridge** (Windows bootstrap) — ab-served | -For the complete verb list run `adom-bridge-cli list_commands`.+For the complete verb list run `adom-bridge list_commands`. -> **CLI name per platform:** the bridge CLI is **`adom-bridge-cli`** on Windows-> and **`adom-bridge`** on macOS. Examples in this skill use `adom-bridge-cli`+> **CLI name per platform:** the bridge CLI is **`adom-bridge`** on Windows+> and **`adom-bridge`** on macOS. Examples in this skill use `adom-bridge` > — substitute `adom-bridge` on a mac workspace.  ### Host shell-trust model@@ -117,13 +117,13 @@ blocked on per-command approval dialogs — convenient, but it means anything yo run there really runs. Revoke the standing auto-approval at any time:  ```bash-adom-bridge-cli shell_auto_approve '{"duration_secs":0}'   # turn auto-approve off now+adom-bridge shell_auto_approve '{"duration_secs":0}'   # turn auto-approve off now ```  When you *don't* need a free-form shell, prefer the **no-escape structured runners** over hand-quoted `shell_execute` (ab ≥ 1.8.50):-`adom-bridge-cli run_script '{"interpreter":"bash|cmd|powershell","scriptB64":"<b64>"}'`-and (Windows) `adom-bridge-cli wsl_exec '{"distro":"Adom-Workspace","user":"adom","scriptB64":"<b64>"}'`+`adom-bridge run_script '{"interpreter":"bash|cmd|powershell","scriptB64":"<b64>"}'`+and (Windows) `adom-bridge wsl_exec '{"distro":"Adom-Workspace","user":"adom","scriptB64":"<b64>"}'` — base64 the script so no quoting survives to be mangled.  ### Auto-installing missing apps@@ -133,8 +133,8 @@ link — trigger an unattended install (the mechanism is platform-specific; the verb reports if unsupported on this platform):  ```bash-adom-bridge-cli desktop_install_kicad '{}'   # install KiCad-adom-bridge-cli desktop_install_node  '{}'   # install Node.js (unblocks the Pup bridge)+adom-bridge desktop_install_kicad '{}'   # install KiCad+adom-bridge desktop_install_node  '{}'   # install Node.js (unblocks the Pup bridge) ```  (`install_kicad` fires when `kicad_list_versions` returns@@ -152,41 +152,41 @@ without manual `send_files`/`pull_file` round-trips.  ## Talking to Hydrogen + ab from the CLI -You reach the host through the **`adom-bridge-cli` CLI**, which relays your commands+You reach the host through the **`adom-bridge` CLI**, which relays your commands over a WebSocket to the desktop client(s).  **Host shell + files:** ```bash-adom-bridge-cli shell_execute '{"command":"<cmd>","timeoutSeconds":60}'-adom-bridge-cli pull_file  '{"filePaths":["C:\\path\\file"],"saveTo":"/tmp"}'-adom-bridge-cli send_files '{"filePaths":["/tmp/x"],"saveTo":"C:\\Users\\<you>"}'-adom-bridge-cli desktop_list_windows+adom-bridge shell_execute '{"command":"<cmd>","timeoutSeconds":60}'+adom-bridge pull_file  '{"filePaths":["C:\\path\\file"],"saveTo":"/tmp"}'+adom-bridge send_files '{"filePaths":["/tmp/x"],"saveTo":"C:\\Users\\<you>"}'+adom-bridge desktop_list_windows ```  **Hydrogen control (the Hydrogen app itself):** ```bash-adom-bridge-cli hd_status            # is Hydrogen running + composed runtime state-adom-bridge-cli hd_screenshot        # window-bounded Hydrogen shot (resize <1500px before reading!)-adom-bridge-cli hd_log               # tail Hydrogen's log-adom-bridge-cli hd_launch            # start Hydrogen detached+adom-bridge hd_status            # is Hydrogen running + composed runtime state+adom-bridge hd_screenshot        # window-bounded Hydrogen shot (resize <1500px before reading!)+adom-bridge hd_log               # tail Hydrogen's log+adom-bridge hd_launch            # start Hydrogen detached # Direct Hydrogen control API (HTTP, no shell-escaping pain):-adom-bridge-cli hd_api '{"method":"POST","path":"/setup/run-all","body":{}}'-adom-bridge-cli hd_api '{"method":"GET","path":"/health"}'+adom-bridge hd_api '{"method":"POST","path":"/setup/run-all","body":{}}'+adom-bridge hd_api '{"method":"GET","path":"/health"}' ``` `hd_api` hits Hydrogen's **control API**, discovering its real port from `ports.json` (key `control`, fallback **47084**) in Hydrogen's app-data directory.  **Embedded-mode introspection (ab-served):** ```bash-adom-bridge-cli desktop_embedded_status   # embedded=true/false, enteredVia=launch-flag|runtime-adopt+adom-bridge desktop_embedded_status   # embedded=true/false, enteredVia=launch-flag|runtime-adopt ```  ## How the connection works (and how you check it)  ``` You (AI in the workspace)-  └─ adom-bridge-cli <verb> '<json>'        ← CLI in the distro-       └─ relay  (adom-bridge-cli serve: WS :8765 + HTTP :8766, started in the workspace)+  └─ adom-bridge <verb> '<json>'        ← CLI in the distro+       └─ relay  (adom-bridge serve: WS :8765 + HTTP :8766, started in the workspace)             └─ WebSocket ──► Hydrogen's built-in bridge AND/OR the embedded ab on the user's machine                  └─ acts on the OS / KiCad / Fusion / Chrome ```@@ -198,11 +198,11 @@ You (AI in the workspace)   forwarding on macOS) — see the `hydrogen-networking` skill. - **Always verify the bridge before acting on the host:**   ```bash-  adom-bridge-cli ping       # → {"status":"connected", ...} means a client is reachable-  adom-bridge-cli status     # who's connected + .capabilities + which local apps are installed/running+  adom-bridge ping       # → {"status":"connected", ...} means a client is reachable+  adom-bridge status     # who's connected + .capabilities + which local apps are installed/running   ```   If `ping` fails, no desktop client is connected — tell the user, and (if needed)-  walk the `adom-bridge-cli` setup steps. Don't claim you acted on their machine+  walk the `adom-bridge` setup steps. Don't claim you acted on their machine   without a successful round-trip. Don't try to "fix" a dead host client from in   here — surface it. @@ -224,7 +224,7 @@ When the user asks for something that lives on their real computer — "save thi to my Desktop", "what's on my screen", "open this in KiCad", "run this command on my machine" — that's an **ab** job, and you can do it. When it's about the workspace itself (editor, files under `/home/adom/project`, the runtime), that's-**Hydrogen**. Lead with what you can do, verify with `adom-bridge-cli ping`, then act.+**Hydrogen**. Lead with what you can do, verify with `adom-bridge ping`, then act.  ## Related skills - **hydrogen-embedded-bridge** (Windows bootstrap) — how Hydrogen installs + embeds ab (tray, lifecycle, standalone↔embedded)@@ -234,4 +234,4 @@ workspace itself (editor, files under `/home/adom/project`, the runtime), that's - **hydrogen-recording** (platform bootstrap; `hydrogen-recording-mac` on macOS) — screen vs tab recording (ab-served) - **hydrogen-notifications** (platform bootstrap) — desktop toasts; **hydrogen-captions** (platform bootstrap) — on-screen caption overlay - **hydrogen-open-url** (platform bootstrap) — the ways to open a URL (Pup, native browser, picker, …)-- `pup` — driving Pup browser windows; `adom-bridge-cli` — the full CLI verb reference+- `pup` — driving Pup browser windows; `adom-bridge` — the full CLI verb reference