Adom Hydrogen (macOS / Lima)

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

@@ -4,7 +4,7 @@   "slug": "hd-mac-bootstrap",   "title": "Hydrogen Desktop (macOS / Lima)",   "brief": "The macOS platform layer for Hydrogen Desktop.",-  "version": "0.1.10",+  "version": "0.1.11",   "license": "proprietary",   "visibility": "public",   "metadata": {

@@ -1,6 +1,6 @@ --- name: hd-container-description: Context for Claude Code running inside a Hydrogen Desktop workspace machine. Documents the exact OS (Ubuntu 24.04, code-server 4.112.0, the Adom-Workspace machine), explains how setup differs from Adom cloud containers (setup-steps NOT bootstrap.sh), what bridges are available, and how to use the relay. Trigger on startup, adom-cli errors, bridge commands, screenshot requests, container-platform questions, code-server / VS Code extension issues, or when the AI needs concrete facts about its environment instead of guessing.+description: Context for Claude Code running inside a Hydrogen Desktop workspace machine. Documents the exact OS (Ubuntu 24.04, code-server 4.112.0, the Adom-Workspace machine), explains how setup differs from Adom cloud containers (setup-steps), what bridges are available, and how to use the relay. Trigger on startup, adom-cli errors, bridge commands, screenshot requests, container-platform questions, code-server / VS Code extension issues, or when the AI needs concrete facts about its environment instead of guessing. ---  # Hydrogen Desktop Workspace (Machine)@@ -32,7 +32,7 @@ If you ever need to confirm: `cat /etc/os-release`, `uname -m` (expect `aarch64`  ## Setup is via HD's setup-steps -HD provisions this machine through its own **setup-steps** flow (Rust code in `hydrogen-desktop/src-tauri/crates/hd-app/src/setup_steps_macos.rs`, with the runtime mechanics in `hydrogen-desktop/src-tauri/crates/hd-app/src/runtime/macos.rs`), shown as the "Install Tools" panel in the HD UI. It is a **different code path** than cloud containers.+HD provisions this machine through its own **setup-steps** flow (Rust code in `hydrogen-desktop/src-tauri/crates/hd-app/src/setup_steps_macos.rs`, with the runtime mechanics in `hydrogen-desktop/src-tauri/crates/hd-app/src/runtime/macos.rs`), shown as the "Install Tools" panel in the HD UI. It is a **different code path** than cloud containers, which provision via the adompkg/wiki-package bootstrap (`adom/hd-bootstrap`).  The machine cascade is **18 steps** (state file `setup-steps-macos.json`) vs the legacy Docker flow's 24. Most tooling is NOT installed by a step — it's BAKED into `adom-golden.tar.gz` at image-build time (the 8 Adom CLIs, the claude CLI + Code extension, code-server, VS Code settings, and all `hd-*` skills). The Docker `pull-image` / `create-container` / `start-container` steps are collapsed into a single step 1, `ensure-workspace`, which runs `machinectl import-tar` of `adom-golden.tar.gz` if the machine isn't already present. The relay is started by the `start-relay` step. See `hd-golden-image`. @@ -82,7 +82,7 @@ adom-desktop browser_navigate '{"url": "..."}'  ### KiCad bridge ```bash-adom-desktop kicad_open_board '{"path": "/Users/john/path/to/board.kicad_pcb"}'+adom-desktop kicad_open_board '{"path": "/Users/<you>/path/to/board.kicad_pcb"}' adom-desktop kicad_screenshot_all adom-desktop kicad_run_drc '{"path": "..."}' adom-desktop kicad_window_info@@ -98,14 +98,14 @@ adom-desktop fusion_export_step '{"path": "..."}' ### File transfer ```bash adom-desktop send_files '{"files": [{"path": "/home/adom/file.txt"}]}'-adom-desktop pull_file '{"remotePath": "/Users/john/file.txt", "localPath": "/tmp/file.txt"}'+adom-desktop pull_file '{"remotePath": "/Users/<you>/file.txt", "localPath": "/tmp/file.txt"}' ```  ### Desktop interaction ```bash adom-desktop notify_user '{"message": "Build complete", "duration_ms": 3000}' adom-desktop desktop_open_url '{"url": "https://..."}'-adom-desktop desktop_open_folder '{"path": "/Users/john/project"}'+adom-desktop desktop_open_folder '{"path": "/Users/<you>/project"}' ```  ## What's different from Adom cloud containers

@@ -71,7 +71,7 @@ N/A on macOS — there are no Windows drive mounts. Use the relay instead (see b adom-desktop send_files '{"filePaths":["/home/adom/project/myfile.txt"],"targetApp":"general","destinationFolder":"."}'  # Pull a Mac file into the workspace's /tmp-adom-desktop pull_file '{"filePaths":["/Users/john/Downloads/myfile.txt"],"saveTo":"/tmp"}'+adom-desktop pull_file '{"filePaths":["/Users/<you>/Downloads/myfile.txt"],"saveTo":"/tmp"}' ```  ### 4. Open the workspace's `/home/adom/project/` in VS Code's File Explorer