Adom Hydrogen (macOS / Lima)

⋯ 1 unchanged line ⋯

@@ -1,75 +0,0 @@-----name: hydrogen-setup-steps-description: What Hydrogen's setup cascade did to prepare this macOS workspace — the 19-step sequence that provisions the Lima VM, imports the golden image, converge-installs the tooling layer from the Adom Wiki, and verifies the whole stack end-to-end. Use when the user asks "what did setup do", "why is X installed", "re-run a setup step", "what's a virgin reset", or "why did step N fail". Trigger words — setup steps, install steps, setup panel, virgin reset, re-run step, Run All, what did setup do, setup failed, hydrogen setup.------# Hydrogen Setup Steps (macOS)--On first launch (or after a virgin reset) Hydrogen runs a 19-step cascade that-turns a blank Mac into a fully-tooled Adom workspace. The golden image is-SLIM — it bakes only the static layer (Ubuntu, code-server, the editor-extensions with their bundled CLIs as shims, the Adom CLIs). The tooling-layer — every `hydrogen-*` skill, adom-vscode, editor settings — is-converge-installed fresh from the Adom Wiki. Executed by-`setup_steps_macos.rs` (`step_defs_macos()`): halt-on-failure,-resume-not-restart, per-step 3× auto-retry.--## The steps (current, in order)--| # | Step | Purpose |-|---|------|---------|-| 1 | ensure-workspace | Lima VM `hydrogen-builder` up (provision if missing), import the machine (configured snapshot when it matches the pinned golden version, else the golden tarball), boot, start code-server on the container's port, verify host reachability |-| 2 | ensure-adom-bridge | The Adom Bridge companion app present + running on the Mac |-| 3 | wait-codeserver | Host TCP probe of the container's code-server port |-| 4 | install-hydrogen-skills | THE tooling converge: bundled native arm64 adom-wiki CLI into the machine, then `adom-wiki pkg install adom/hydrogen-mac-bootstrap` (+ chain) with install scripts re-run |-| 5 | install-adom-vscode | Waits for Adom sign-in, reloads the editor, proves the :8821 editor-control API answers (extension actually ACTIVATED) |-| 6 | set-env-vars | ADOM_CARBON_URL / ADOM_HYDROGEN_URL / control URL / VSCODE_PROXY_URI into the machine (4-channel delivery) |-| 7 | inject-api-key | Adom session token → `/var/run/adom/api-key` (tmpfs — re-injected on every auth completion + launch) |-| 8 | configure-vscode | Theme, trusted domains, layout — idempotent re-assert + per-session layout via :8821 |-| 9 | install-claude-ext | Ensures the Claude Code extension via Hydrogen's controlled install→restart→reload chain (marketplace auto-update stays OFF) |-| 10 | ensure-bridge-runtimes | Node/Python runtimes for the tool bridges (pinned downloads if the system lacks them, no admin prompt) |-| 11 | start-relay | The adom-bridge relay inside the workspace, on the container's relay ports |-| 12 | test-direct-connect | Fast workspace→desktop command path proven |-| 13 | test-relay | Relay registered with Adom Bridge for file streaming |-| 14 | test-adom-cli | GATE: adom-cli reaches Adom on both route classes (carbon + hydrogen-proxy) |-| 15 | ensure-sse | GATE: the editor's live SSE link is connected |-| 16 | verify-workspace | GATE: the proxy holds a real pushed layout |-| 17 | welcome | Tidies the editor layout for the first conversation |-| 18 | verify-setup | GATE: end-to-end re-verification (machine, code-server, :8821, session) |-| 19 | open-welcome | GATE: welcome.html actually opens in the right pane |--**Multi-container note:** the cascade converges the ACTIVE container's-machine. Additional containers (see the profile menu) import the configured-snapshot — tooling preinstalled — and only re-run the mechanical subset.--## Common user questions--**"Why is X installed?"** → Adom CLIs are baked in the golden image; skills,-extensions, and settings were converge-installed from the wiki (step 4/9). The-`claude` and `codex` CLIs are shims to the binaries bundled inside their-editor extensions.--**"Setup failed at step N"** → the setup panel shows the error; each step has-a retry button (after the automatic 3×). Most common: step 1 (VM provisioning-/ image download) and step 14 (network to carbon).--**"Re-run a step"** → setup panel → step row → Re-run, or-`POST $CTRL/setup/step/<id>` (optional `{"continue_after":true}`).--## Virgin reset--The ONLY programmatic trigger is `POST /setup/panel/run-virgin-reset` with-`confirmed_destructive:true` and the toggle keys: `install_state` (step state),-`container` (DESTRUCTIVE — `machinectl remove` of the active container's-machine + reimport; `/home/adom/project` in it is gone), `tarball` (cached-golden re-download), `webview_storage` / `vscode_state` (queued, flushed next-launch), `adom_token`, `claude_token`. The reset scopes to Hydrogen's own-machine only — never the Lima VM or other machines. Deprecated + refused:-`POST /setup/run-all`, `/setup/run-step`, `/setup/virgin-reset`,-`/workspace/unregister`.--## Related skills--- `hydrogen-container` — the workspace machine this cascade produces-- `hydrogen-networking` — adom-host gateway + port model-- `hydrogen-api-key-mac` — recovering step 7's token later