Adom Bridge

@@ -474,7 +474,8 @@ Reference implementations: [`scripts/sample-bridges/hello-python/server.py`](../ - `send_files` -- Send files from the Docker container to the desktop. Files are base64-encoded in transit.
   - `filePaths`: array of absolute paths on the server
   - `targetApp`: "kicad", "fusion360", or "general"
-  - `dest`: **absolute** Windows path (under a safe root) to land the files exactly where you want (v1.8.148+). Prefer this when you know the target dir.
+  - `dest`: **absolute** Windows path (under a safe root) to land the files exactly where you want (v1.8.148+). Prefer this when you know the target dir. A folder is created if missing. For ONE file, `dest` may be the full file path instead. A `dest` ending in a slash or in `.pretty` / `.3dshapes` / `.app` / `.bundle` / `.framework` is always a folder (2.1.163+), so a KiCad footprint library works directly: `dest: "C:/Users/<you>/Documents/proj/lib/mylib.pretty"`.
+  - `destIsFolder` (2.1.163+): `true` forces `dest` to be a folder for any other dotted folder name; `false` forces it to be the file path.
   - `destinationFolder`: **relative subfolder only** (e.g. `"kicad/symbols"`, `"fusion"`). The desktop app controls the base directory. **Absolute paths are rejected.** With neither `dest` nor `destinationFolder`, files land in the laptop's **Downloads** folder.
   - Returns `destinationPaths[]` with the absolute path of every saved file, plus (v1.8.168) `savedToDir` (the folder) and a rich `_hint`. **The files land on the LAPTOP (Windows host), not in your container** — verify with `list_dir`, pull one back with `pull_file`.
   - **`send_files` only COPIES bytes — it does NOT install or register a bridge.** Dropping bridge files with `send_files` will NOT make a capsule appear or verbs route. To add a bridge use `bridge_install '{"manifestUrl":"…/<bridge>-bridge-manifest.json"}'`, then confirm with `bridge_list`.

⋯ 1 unchanged line ⋯

@@ -1,6 +1,6 @@ {
   "slug": "adom-bridge",
-  "version": "2.1.162",
+  "version": "2.1.163",
   "type": "app",
   "brief": "Adom Bridge unleashes your AI onto your full PC: full power, full safety. The AI breaks out of the container it runs in and onto your real machine, managing and running your entire laptop as you: launch apps, move files, drive any window, control KiCad, Fusion 360 or your real signed-in browser. Works with any AI, cloud or local (Claude Desktop, Claude Code, Codex), no Hydrogen required. Bridge and its bridges are an operating system for AI, with managed Node and Python runtimes, and a human-only permission system keeps you in charge of every side-effecting command.",
   "description": "Install this package in a cloud or Hydrogen Desktop container, not on the PC. It delivers two things: the Linux adom-bridge-cli (linked onto PATH) and the Claude skill set that teaches an AI every desktop verb (shell, files, screenshots, windows, notifications, KiCad, Fusion 360, browser automation). The CLI drives the Adom Bridge app running on your Windows PC over the relay; the Windows app itself is the separate installer in the Download box, not part of this package. Run adom-wiki pkg update to keep the CLI and skills current.",

@@ -1,6 +1,6 @@ {   "slug": "adom-bridge",-  "version": "2.1.162",+  "version": "2.1.163",   "type": "app",   "description": "Install this package in a cloud or Hydrogen Desktop container, not on the PC. It delivers two things: the Linux adom-bridge-cli (linked onto PATH) and the Claude skill set that teaches an AI every desktop verb (shell, files, screenshots, windows, notifications, KiCad, Fusion 360, browser automation). The CLI drives the Adom Bridge app running on your Windows PC over the relay; the Windows app itself is the separate installer in the Download box, not part of this package. Run adom-wiki pkg update to keep the CLI and skills current.",   "keywords": [

@@ -277,4 +277,7 @@ notify_user {   with ok/errorCode/error. Poll it (or notify_events) to learn what happened.
 - Verb names must be CURRENT: the first live demo armed a pre-rename verb and the click
   recorded verb_renamed. If a rename refusal comes back, re-arm with the new name.
+- Use the CLI spelling: `{"command": "hd_api", "args": {...}}` works as written (2.1.163+).
+  Before 2.1.163 a prefixed Hydrogen verb failed at click time with "Unknown hd command";
+  on an older box, arm `{"app": "hd", "command": "api", ...}` instead.
 - An expired or already-used click falls back to raising Adom Bridge, never a dead click.

@@ -474,7 +474,8 @@ Reference implementations: [`scripts/sample-bridges/hello-python/server.py`](../ - `send_files` -- Send files from the Docker container to the desktop. Files are base64-encoded in transit.
   - `filePaths`: array of absolute paths on the server
   - `targetApp`: "kicad", "fusion360", or "general"
-  - `dest`: **absolute** Windows path (under a safe root) to land the files exactly where you want (v1.8.148+). Prefer this when you know the target dir.
+  - `dest`: **absolute** Windows path (under a safe root) to land the files exactly where you want (v1.8.148+). Prefer this when you know the target dir. A folder is created if missing. For ONE file, `dest` may be the full file path instead. A `dest` ending in a slash or in `.pretty` / `.3dshapes` / `.app` / `.bundle` / `.framework` is always a folder (2.1.163+), so a KiCad footprint library works directly: `dest: "C:/Users/<you>/Documents/proj/lib/mylib.pretty"`.
+  - `destIsFolder` (2.1.163+): `true` forces `dest` to be a folder for any other dotted folder name; `false` forces it to be the file path.
   - `destinationFolder`: **relative subfolder only** (e.g. `"kicad/symbols"`, `"fusion"`). The desktop app controls the base directory. **Absolute paths are rejected.** With neither `dest` nor `destinationFolder`, files land in the laptop's **Downloads** folder.
   - Returns `destinationPaths[]` with the absolute path of every saved file, plus (v1.8.168) `savedToDir` (the folder) and a rich `_hint`. **The files land on the LAPTOP (Windows host), not in your container** — verify with `list_dir`, pull one back with `pull_file`.
   - **`send_files` only COPIES bytes — it does NOT install or register a bridge.** Dropping bridge files with `send_files` will NOT make a capsule appear or verbs route. To add a bridge use `bridge_install '{"manifestUrl":"…/<bridge>-bridge-manifest.json"}'`, then confirm with `bridge_list`.