Adom Hydrogen (platform base)

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -40,7 +40,7 @@ image's Dockerfile (not this package at all).**  | Dep | Why it's here | Status | |-----|---------------|--------|-| `adom/core` | The whole Adom ecosystem — skills hub, distributor search, KiCad/Fusion, pup, `adom-cli`, the `adom-vscode` binary, `adompkg`, etc. Replaces what gallia used to bake. | ✅ published 4.9.1, anon + sudo-free |+| `adom/core` | The whole Adom ecosystem — skills hub, distributor search, KiCad/Fusion, pup, `adom-cli`, the `adom-vscode` binary, `adompkg`, etc. This is what the golden image bakes in. | ✅ published 4.9.1, anon + sudo-free | | `adom/adom-workspace-updater` | The in-distro updater daemon (systemd .service/.timer). | ✅ published 0.1.11, anon — **`needs_sudo: true`** | | `adom/adom-desktop` | The Adom Desktop relay CLI. | ✅ published 1.8.147, anon | 

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Hydrogen Desktop",   "brief": "Layer Hydrogen Desktop's workspace onto a standard Adom workstation.",-  "version": "0.2.3",+  "version": "0.2.4",   "description": "Hydrogen Desktop's PLATFORM-GENERIC workspace layer on top of adom/core. Installs adom/core for the full Adom ecosystem, then adds everything common to running inside Hydrogen Desktop on ANY platform: the runtime-neutral hd-* skills and the generic HD editor configuration (Claude Code CLI + extension, VS Code settings, trusted domains). Platform-specific layers depend on THIS: adom/hd-windows-bootstrap (WSL2), adom/hd-mac-bootstrap, adom/hd-ubuntu-bootstrap. The reference design other orgs copy to build their own bootstrap on adom/core.",   "org": "adom",   "platform": "any",@@ -21,5 +21,8 @@   "dependencies": {     "adom/core": "^4.9.0",     "adom/adom-desktop": "^1.8.0"+  },+  "hero": {+    "path": "docs/hero.png"   }-}+}\ No newline at end of file

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Hydrogen Desktop",   "brief": "Layer Hydrogen Desktop's workspace onto a standard Adom workstation.",-  "version": "0.2.3",+  "version": "0.2.4",   "description": "Hydrogen Desktop's PLATFORM-GENERIC workspace layer on top of adom/core. Installs adom/core for the full Adom ecosystem, then adds everything common to running inside Hydrogen Desktop on ANY platform: the runtime-neutral hd-* skills and the generic HD editor configuration (Claude Code CLI + extension, VS Code settings, trusted domains). Platform-specific layers depend on THIS: adom/hd-windows-bootstrap (WSL2), adom/hd-mac-bootstrap, adom/hd-ubuntu-bootstrap. The reference design other orgs copy to build their own bootstrap on adom/core.",   "org": "adom",   "platform": "any",@@ -25,5 +25,9 @@   "author": {     "name": "John Lauer",     "email": "[email protected]"+  },+  "hero": {+    "type": "image",+    "path": "docs/hero.png"   } }\ No newline at end of file

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -296,7 +296,7 @@ The setup/bootstrap process depends on a valid session token: 1. **inject-api-key** -- reads the HD-side `hydrogen-session.txt`, writes the    token into the workspace at `/var/run/adom/api-key` (mode 644) as the Adom    API key. If the token is missing or expired, this step fails and downstream-   steps (adom-cli, gallia, etc.) cannot authenticate.+   steps (adom-cli, etc.) cannot authenticate.  2. **Claude auth** -- uses `replay-claude-credentials.json` if available;    otherwise requires the user to complete the Claude OAuth flow inside the

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -122,7 +122,7 @@ Or if the workspace is in a broken state:  **"Why is CPU showing 200% / 1600%?"** It's not — the displayed % is capped at 100 for the bar fill, but the tooltip shows the real number. CPU of `100% of 16 cores` means 1 full vCPU pegged. -**"Why does RAM stay constant at ~4% even when I'm doing nothing?"** Code-server, the relay, gallia, the adom-vscode HTTP API, etc. all run in the workspace all the time. ~700 MB baseline is normal.+**"Why does RAM stay constant at ~4% even when I'm doing nothing?"** Code-server, the relay, the adom-vscode HTTP API, etc. all run in the workspace all the time. ~700 MB baseline is normal.  **"The 'restart needed' badge appeared — what happened?"** Almost always a hiccup after the host woke from sleep/hibernate, leaving the workspace or code-server unreachable. Click Restart Workspace in the Adom menu (top-left); HD restarts the workspace, re-ensures code-server, and the badge clears. 

⋯ 1 unchanged line ⋯

@@ -27,13 +27,13 @@ You are running inside the **local workspace** managed by Hydrogen Desktop (HD).  If you ever need to confirm: `cat /etc/os-release`, `uname -m`, `/usr/lib/code-server/bin/code-server --version`. Don't speculate about alpine/arm64 — Ubuntu 24.04 matches the cloud container. -## Setup is via HD's setup-steps, NOT gallia bootstrap.sh+## Setup is via HD's setup-steps, NOT the legacy bootstrap.sh -HD provisions this workspace through its own **setup-steps** flow, shown as the "Install Tools" panel in the HD UI. It is a **different code path** than cloud containers, which run `gallia/scripts/bootstrap.sh`.+HD provisions this workspace through its own **setup-steps** flow, shown as the "Install Tools" panel in the HD UI. It is a **different code path** than cloud containers, which run the legacy `scripts/bootstrap.sh`. -Most tooling is NOT installed by a step — it's BAKED into the golden image at image-build time (gallia, the Adom CLIs, the claude CLI + Code extension, code-server, VS Code settings, and all `hd-*` skills). The provisioning step imports the golden image if the workspace isn't already registered, and the relay is started by the `start-relay` step. See `[[hd-setup-steps]]`.+Most tooling is NOT installed by a step — it's BAKED into the golden image at image-build time (the Adom CLIs, the adompkg skills, the claude CLI + Code extension, code-server, VS Code settings, and all `hd-*` skills). The provisioning step imports the golden image if the workspace isn't already registered, and the relay is started by the `start-relay` step. See `[[hd-setup-steps]]`. -When debugging install issues here, the source of truth is HD's setup-steps code — its step IDs (`ensure-workspace`, `install-adom-vscode`, `set-env-vars`, `inject-api-key`, `start-relay`, `claude-auth`, etc.) map 1:1 to what ran on this workspace. There is NO `install-claude-ext` / `install-claude-cli` / `install-gallia` / `write-vscode-settings` step — those are baked. Do NOT chase bugs into `bootstrap.sh` — that script lives in the baked image but HD itself never invokes it.+When debugging install issues here, the source of truth is HD's setup-steps code — its step IDs (`ensure-workspace`, `install-adom-vscode`, `set-env-vars`, `inject-api-key`, `start-relay`, `claude-auth`, etc.) map 1:1 to what ran on this workspace. There is NO `install-claude-ext` / `install-claude-cli` / `install-skills` / `write-vscode-settings` step — those are baked. Do NOT chase bugs into `bootstrap.sh` — that script lives in the baked image but HD itself never invokes it.  ## VS Code extension caveats @@ -120,7 +120,7 @@ adom-desktop desktop_open_folder '{"path": "<host folder path>"}' ## Environment variables  - `ADOM_DESKTOP_MODE=local` — indicates HD local mode-- `GALLIA_SERVICE=local` — tells gallia this is a local workspace+- `ADOM_SERVICE=local` — marks this as a local workspace - `VSCODE_PROXY_URI=http://localhost:7380/proxy/{{port}}/` — code-server's proxy  (Platform layers may set additional host-specific env vars — see `[[hd-container-windows]]`.)

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -1,6 +1,6 @@ --- name: hd-setup-steps-description: What HD's setup steps did to prepare your workspace — the install sequence that provisions the golden workspace image, injects your Adom session, wires up the relay, and walks the Claude auth gate. Use this skill 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, why is X installed, setup failed, install-tools, hd setup, claude code extension install, gallia install, hd workspace ready.+description: What HD's setup steps did to prepare your workspace — the install sequence that provisions the golden workspace image, injects your Adom session, wires up the relay, and walks the Claude auth gate. Use this skill 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, why is X installed, setup failed, install-tools, hd setup, claude code extension install, skills install, hd workspace ready. ---  # HD Setup Steps — what was done to prepare your workspace@@ -12,7 +12,7 @@ Windows/WSL2).  When you first launched Hydrogen Desktop (or after a virgin reset), HD ran an install sequence to turn a blank machine into a fully-tooled Adom workspace.-The heavy tooling (code-server, gallia, the Adom CLIs, the claude CLI + Code+The heavy tooling (code-server, the Adom CLIs, the adompkg skills, the claude CLI + Code extension, VS Code settings, and all `hd-*` skills) is already BAKED into the golden image; setup just provisions that image, injects your Adom session, wires up the relay, and walks the Claude auth gate. This skill explains what@@ -48,15 +48,15 @@ auto-retry. The exact steps and ordering are platform-specific — see ### Steps that NO LONGER EXIST (baked into the golden image)  These are NOT setup steps anymore — they are baked at image-build time:-`install-gallia`, `install-hd-skills`, `verify-adom-desktop`,+`install-hd-skills`, `verify-adom-desktop`, `install-claude-cli`, `install-claude-ext`, `write-vscode-settings`,-`set-trusted-domains`, `clean-layout`. If a user asks "what installed gallia /+`set-trusted-domains`, `clean-layout`. If a user asks "what installed the Claude extension / my skills / VS Code settings", the answer is: **baked into the golden image at build time, not a setup step.** See `hd-golden-image`.  ## Common user questions -**"Why is X installed in my workspace?"** → If X is gallia, an Adom CLI, the+**"Why is X installed in my workspace?"** → If X is an adompkg skill, an Adom CLI, the claude CLI, the Claude Code extension, VS Code settings, or an `hd-*` skill, it was **baked into the golden image** — not run as a setup step. The setup steps only provision the image, inject your session, wire the relay, and walk Claude

⋯ 1 unchanged line ⋯

@@ -20,8 +20,8 @@ live in the companion [[hd-setup-windows]] skill.  The HD setup process targets ZERO manual clicks for the user. The heavy lifting is already done at image-build time: the golden workspace image ships-with code-server, gallia, the Adom CLIs, the claude CLI + Code extension, VS-Code settings, and all `hd-*` skills BAKED IN. Setup just provisions that+with code-server, the Adom CLIs, the adompkg skills, the claude CLI + Code+extension, VS Code settings, and all `hd-*` skills BAKED IN. Setup just provisions that image, injects the user's session, wires up the relay, and walks the single human auth gate. If something is missing, HD downloads it — never tell the user to install something manually. See the `hd-golden-image` skill for the@@ -59,10 +59,10 @@ Conceptually the steps fall into these phases: ### Steps that NO LONGER EXIST (baked into the golden image)  These are NOT setup steps anymore — they are baked at image-build time and-must not be listed or "run": `install-gallia`, `install-hd-skills`,+must not be listed or "run": `install-hd-skills`, `verify-adom-desktop`, `install-claude-cli`, `install-claude-ext`,-`write-vscode-settings`, `set-trusted-domains`, `clean-layout`. gallia, the-Adom CLIs, the claude CLI + Code extension, code-server, settings, and all+`write-vscode-settings`, `set-trusted-domains`, `clean-layout`. The+Adom CLIs, the adompkg skills, the claude CLI + Code extension, code-server, settings, and all `hd-*` skills are baked into the golden image. See `hd-golden-image`.  ## Panel Buttons@@ -179,7 +179,7 @@ a real layout; `welcome` opens Claude Code and sends the first prompt; the final `open-welcome` gate opens welcome.html in HD's right pane and HARD-FAILS if the Welcome tab doesn't appear. -> Note: gallia, the Adom CLIs, the claude CLI + Code extension, VS Code+> Note: the Adom CLIs, the adompkg skills, the claude CLI + Code extension, VS Code > settings, and `hd-*` skills are NOT setup steps — they are baked into the > golden image. See `hd-golden-image`. 

⋯ 1 unchanged line ⋯

@@ -68,7 +68,7 @@ favicon, not `mdi:rocket-launch`.  ## Brand rule: icons must be monochrome `#e6edf3` -Per `gallia/skills/brand/SKILL.md`, **all Adom icons must be monochrome+Per the Adom `brand` skill, **all Adom icons must be monochrome white (`#e6edf3`)** — no colored icons, no multi-color, no brand-palette colors in icons. This applies to tab icons too. 

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -49,7 +49,7 @@ Tell them they have access to a full electronics prototyping ecosystem. Specific Adapt this to whatever the user's data is. Don't bullet-dump everything — write it as a warm welcome paragraph followed by capabilities. Use markdown.  ```markdown-You're **{user.formatted_name}**, signed in to Adom as **{user.name}** ({user.email}). You're running in **Hydrogen Desktop**, Adom's local AI dev environment, on your Windows machine. The workspace itself is Ubuntu 24.04 with code-server, the `claude` CLI, and the full Adom skill ecosystem (gallia + HD skills) already loaded.+You're **{user.formatted_name}**, signed in to Adom as **{user.name}** ({user.email}). You're running in **Hydrogen Desktop**, Adom's local AI dev environment, on your Windows machine. The workspace itself is Ubuntu 24.04 with code-server, the `claude` CLI, and the full Adom skill ecosystem (adompkg + HD skills) already loaded.  A few quick orientation notes: - Your **Linux username here is `adom`** (not `{user.name}`) — that's intentional, every Adom workspace uses `adom` for consistency. Your Adom identity (`{user.name}`) is what shows up across the Adom ecosystem.@@ -81,7 +81,7 @@ Ask me to do any of those, or just ask "what's the best way to start a new PCB p  - **Don't just bullet-dump every capability** — group them, lead with the personalized intro, end with an invitation. - **Pull real numbers** from `adom-cli` — generic "you have some repos" feels worse than "you have 4 repos."-- **Don't list internal jargon** — say "Adom's autorouter", not "the gallia/autorouter/v2 skill".+- **Don't list internal jargon** — say "Adom's autorouter", not "the autorouter/v2 skill". - **Mention the Linux username quirk early** — it WILL confuse users on first `whoami`. - **If a data fetch fails** (e.g. adom-cli not yet configured), gracefully say "I can't read your Adom session right now, but here's what HD can do once you're signed in" and pivot to capabilities only. 

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯