Adom Hydrogen (macOS / Lima)

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (macOS / Lima)",   "brief": "The macOS platform layer for Adom Hydrogen.",-  "version": "0.1.13",+  "version": "0.1.15",   "description": "The macOS platform layer for Adom Hydrogen, where the workspace runs in a Lima Ubuntu VM hosting the Adom-Workspace systemd-nspawn machine. Depends on adom/hydrogen-bootstrap (the platform-generic Hydrogen layer) and adds everything specific to the Lima/nspawn runtime: the container/networking/ports/setup/topology/volume/workspace-lifecycle hydrogen-* skills (the macOS-runtime bucket), the in-machine workspace-updater daemon, and the macOS code-server workbench seed. Sibling layers adom/hydrogen-windows-bootstrap (WSL2) and adom/hydrogen-ubuntu-bootstrap depend on the same adom/hydrogen-bootstrap. This is the package the golden Lima image installs.",   "org": "adom",   "tags": [

@@ -3,8 +3,8 @@   "type": "bootstrap",   "slug": "hydrogen-mac-bootstrap",   "title": "Adom Hydrogen (macOS / Lima)",-  "brief": "The macOS platform layer for Adom Hydrogen \u2014 converges a Lima/nspawn workspace to the HD-on-Mac runtime.",-  "version": "0.1.13",+  "brief": "The macOS platform layer for Adom Hydrogen.",+  "version": "0.1.15",   "license": "proprietary",   "visibility": "public",   "metadata": {@@ -16,7 +16,7 @@     "type": "image",     "path": "screenshots/hero-v3.png"   },-  "discovery_pitch": "The macOS platform layer for Adom Hydrogen \u2014 the Lima/nspawn workspace runtime plus every mac-specific hd-* skill.",+  "discovery_pitch": "The macOS platform layer for Adom Hydrogen — the Lima/nspawn workspace runtime plus every mac-specific hd-* skill.",   "discovery_triggers": [     "Adom Hydrogen mac",     "hydrogen on macos",@@ -47,5 +47,36 @@       "label": "Workspace status",       "prompt": "is my Lima workspace machine healthy"     }-  ]+  ],+  "description": "The macOS platform layer for Adom Hydrogen, where the workspace runs in a Lima Ubuntu VM hosting the Adom-Workspace systemd-nspawn machine. Depends on adom/hydrogen-bootstrap (the platform-generic Hydrogen layer) and adds everything specific to the Lima/nspawn runtime: the container/networking/ports/setup/topology/volume/workspace-lifecycle hydrogen-* skills (the macOS-runtime bucket), the in-machine workspace-updater daemon, and the macOS code-server workbench seed. Sibling layers adom/hydrogen-windows-bootstrap (WSL2) and adom/hydrogen-ubuntu-bootstrap depend on the same adom/hydrogen-bootstrap. This is the package the golden Lima image installs.",+  "org": "adom",+  "tags": [+    "bootstrap",+    "adom-hydrogen",+    "hydrogen",+    "macos",+    "mac",+    "lima",+    "nspawn"+  ],+  "needs_sudo": false,+  "scripts": {+    "install": "./install.sh"+  },+  "dependencies": {+    "adom/hydrogen-bootstrap": "^0.3.0"+  },+  "files": [+    "install.sh",+    "skills/**",+    "README.md",+    "SKILL.md",+    "page.json",+    "docs/**",+    "screenshots/**"+  ],+  "author": {+    "name": "Kyle Bergstedt",+    "email": "[email protected]"+  } }\ No newline at end of file

@@ -55,7 +55,7 @@ native TCP listeners on the Mac — not inside the workspace machine. | Port | Service | Notes | |------|---------|-------| | 1420 | Dev file server | Dev mode only, serves `build/` |-| 8770 | adom-desktop direct connect | Owned by Adom Desktop, NOT Hydrogen |+| 8770 | adom-desktop direct connect | Owned by Adom Bridge, NOT Hydrogen | | 47080 | Hydrogen discovery server | | | 47083 | Hydrogen reverse proxy | Proxies to code-server | | 47084 | Hydrogen control API | Health, setup, eval, CDP, `/workspace/status`, `/port-forward` |@@ -178,5 +178,5 @@ limactl shell hd-builder -- sudo nsenter -t <leader> -a -S 1001 -G 1001 -- <cmd>    (`ADOM_CARBON_URL`, `ADOM_HYDROGEN_URL`) or discover via the direct    connect API. 6. **NEVER assume adom-desktop direct connect (8770) is owned by Hydrogen.**-   It's owned by Adom Desktop. Hydrogen's direct-api thread binds to 8770-   as a fallback but Adom Desktop takes priority when both are running.+   It's owned by Adom Bridge. Hydrogen's direct-api thread binds to 8770+   as a fallback but Adom Bridge takes priority when both are running.

@@ -22,10 +22,10 @@ The cascade is executed by `setup_steps_macos.rs` (`step_defs_machine()` / `run_ | 4 | set-env-vars | Set `ADOM_CARBON_URL`, `ADOM_HYDROGEN_URL`, `ADOM_HD_CONTROL_URL`, `VSCODE_PROXY_URI`, `ADOM_DESKTOP_MODE` | | 5 | inject-api-key | Write the Adom session token into the machine at `/var/run/adom/api-key` (mode 644) so adom-cli works | | 6 | configure-vscode | settings.json / trusted-domains / activity-bar are BAKED; re-asserts theme + workbench backstops idempotently, and applies the per-session layout via :8821 |-| 7 | ensure-adom-desktop | Verify the Adom Desktop companion app is running on the Mac (the relay's desktop bridge) |+| 7 | ensure-adom-desktop | Verify the Adom Bridge companion app is running on the Mac (the relay's desktop bridge) | | 8 | start-relay | Start the adom-desktop relay inside the workspace (ports 8765 WS / 8766 HTTP) | | 9 | test-direct-connect | Prove the fast container→desktop command path |-| 10 | test-relay | Register the relay with Adom Desktop for file streaming (file transfer + shell exec) |+| 10 | test-relay | Register the relay with Adom Bridge for file streaming (file transfer + shell exec) | | 11 | test-adom-cli | GATE: carbon path + hydrogen-proxy reachability via adom-cli (6 retries) | | 12 | claude-auth | The single human gate — restore Claude creds or drive the in-editor Claude.ai sign-in via the native browser Browser Picker; runs LAST before the payoff steps | | 13 | ensure-sse | GATE: confirm the editor browser SSE session is connected so Welcome's webview-open doesn't 409 |

@@ -43,10 +43,10 @@ per-step 3× auto-retry. State is tracked in `setup-steps-macos.json` | 4 | set-env-vars | ADOM_CARBON_URL / ADOM_HYDROGEN_URL / ADOM_HD_CONTROL_URL / VSCODE_PROXY_URI / ADOM_DESKTOP_MODE | ✓ | | 5 | inject-api-key | Write the Adom session token to `/var/run/adom/api-key` (mode 644) | ✓ | | 6 | configure-vscode | settings.json / trusted-domains / activity-bar are BAKED; re-assert theme + workbench backstops idempotently; apply per-session layout via :8821 | ✓ |-| 7 | ensure-adom-desktop | Verify the Adom Desktop companion app is running on the Mac | ✗ |+| 7 | ensure-adom-desktop | Verify the Adom Bridge companion app is running on the Mac | ✗ | | 8 | start-relay | Start the adom-desktop relay inside the workspace (8765/8766) | ✓ | | 9 | test-direct-connect | Prove the fast container→desktop command path | ✗ |-| 10 | test-relay | Register the relay with Adom Desktop for file streaming | ✗ |+| 10 | test-relay | Register the relay with Adom Bridge for file streaming | ✗ | | 11 | test-adom-cli | GATE: carbon path + hydrogen-proxy reachability via adom-cli (6 retries) | ✗ | | 12 | claude-auth | The single human gate; restore creds or drive in-editor Claude.ai sign-in; runs LAST before payoff | ✓ | | 13 | ensure-sse | GATE: editor browser SSE session connected so Welcome's webview-open doesn't 409 | ✗ |@@ -166,10 +166,10 @@ Writes the Adom session token into the machine at `/var/run/adom/api-key` ### Step 9 — test-direct-connect Proves the fast container→desktop command path. The CLI auto-probes the host control API (wired to the `adom-host` gateway by `/etc/init-host-internal.sh`) and-routes through Adom Desktop's direct connect API.+routes through Adom Bridge's direct connect API.  ### Step 10 — test-relay (register relay)-Registers the relay (started by step 8, `start-relay`) with Adom Desktop for+Registers the relay (started by step 8, `start-relay`) with Adom Bridge for file streaming via the code-server proxy path. This enables `pull_file`, `send_files`, and `shell_execute`. 

@@ -2,7 +2,7 @@ name: hydrogen-topology description: >   MUST READ before ANY Hydrogen work. Explains the three-layer topology: cloud-  Docker (where Claude runs), the user's Mac (where Hydrogen + Adom Desktop run),+  Docker (where Claude runs), the user's Mac (where Hydrogen + Adom Bridge run),   and the Hydrogen local workspace (the Adom-Workspace machine). Every command   you run goes through the relay to the Mac. You CANNOT directly access the   workspace machine — you must shell through the Mac. Trigger words — Hydrogen topology,@@ -22,13 +22,13 @@ CLI relay. There are THREE separate environments:  ### 1. Cloud Docker (where you run) - Your shell, your filesystem, your git repos-- `adom-desktop` CLI connects to Adom Desktop on the Mac via relay+- `adom-desktop` CLI connects to Adom Bridge on the Mac via relay - This container has NOTHING to do with Hydrogen's local workspace - Restarting the workspace machine on the Mac does NOT affect you - You can freely `git push`, edit code, run builds here  ### 2. The user's Mac (user's desktop)-- **Adom Desktop** — relay client app, listens on port 8770 (direct connect)+- **Adom Bridge** — relay client app, listens on port 8770 (direct connect) - **Adom Hydrogen** — the Tauri app you're building - **Lima VM (`hd-builder`)** — hosts the `Adom-Workspace` machine - You reach this via `adom-desktop shell_execute '{"command":"..."}'`@@ -56,7 +56,7 @@ adom-desktop shell_execute '{"command":"limactl shell hd-builder -- sudo nsenter ```bash adom-desktop shell_execute '{"command":"limactl shell hd-builder -- sudo nsenter -t <leader> -a -S 1001 -G 1001 -- adom-desktop ping"}' ```-This tests the FULL chain: machine → local relay → Adom Desktop on the Mac.+This tests the FULL chain: machine → local relay → Adom Bridge on the Mac.  ### Screenshot Hydrogen window ```bash@@ -71,7 +71,7 @@ adom-desktop pull_file '{"filePaths":["/Users/.../file"],"saveTo":"/tmp"}' ## The workspace machine ≠ Your Container  - If the `Adom-Workspace` machine on the Mac goes down, YOUR cloud container is fine-- You can still talk to Adom Desktop, screenshot windows, run shell commands+- You can still talk to Adom Bridge, screenshot windows, run shell commands - You just can't `nsenter` into the workspace machine until it's back - Starting/stopping the machine on the Mac is done via shell_execute. Only ever   touch `Adom-Workspace` (`machinectl terminate Adom-Workspace`) — NEVER tear down@@ -84,7 +84,7 @@ adom-desktop pull_file '{"filePaths":["/Users/.../file"],"saveTo":"/tmp"}' Cloud adom-desktop CLI   → WS relay (cloud :8765)     → internet-      → Adom Desktop on the Mac (relay client)+      → Adom Bridge on the Mac (relay client)         → executes command locally           → returns result             → back through relay to your CLI@@ -95,7 +95,7 @@ For the Hydrogen local workspace machine, there's a SECOND relay: Workspace's adom-desktop CLI   → local relay (machine :8765)     → code-server proxy (:7380/proxy/8765/)-      → Adom Desktop on the Mac (connected as WS client)+      → Adom Bridge on the Mac (connected as WS client)         → executes command           → returns through same chain ```@@ -104,11 +104,11 @@ Workspace's adom-desktop CLI  The Hydrogen install flow MUST verify this chain works: -1. **Verify Adom Desktop running on the Mac** — probe port 8770+1. **Verify Adom Bridge running on the Mac** — probe port 8770    If not running: tell user to install from wiki and launch it 2. **Install adom-desktop CLI into the workspace** — download binary 3. **Start relay inside the workspace** — `adom-desktop serve`-4. **Register relay with Adom Desktop** — `server_add` via direct connect+4. **Register relay with Adom Bridge** — `server_add` via direct connect    URL: `ws://127.0.0.1:{code_server}/proxy/8765/` 5. **Test round-trip** — `limactl shell hd-builder -- sudo nsenter -t <leader> -a -S 1001 -G 1001 -- adom-desktop ping`    Must return `pong` — proves the full chain works