Adom Hydrogen (platform base)

@@ -1,86 +0,0 @@-----name: hydrogen-golden-image-description: >-  Your Hydrogen workspace starts from a THIN golden WSL2 image (v24-thin and-  later): the image carries ONLY the OS baseline — Ubuntu, systemd, code-server,-  the folder contract, and the adom-wiki CLI. EVERYTHING Adom (the adom/core-  toolchain, the 8 CLIs, all hydrogen-* skills, the editor extensions including-  Claude Code) is installed LIVE by the setup cascade's first-  `adom-wiki pkg install adom/hydrogen-windows-bootstrap`, and kept current by-  the registry updater. READ THIS when a user asks "where did these skills/CLIs-  come from", "why did first-run setup take a few minutes", "how do I update-  the workspace", or "what's actually in the image". Trigger words — golden-  image, thin image, pre-baked, baked image, adom-golden, adom-golden.tar.gz,-  wsl --import, tarball version, adom-tarball-version, migrate tarball,-  install-hydrogen-skills, where did the CLIs come from, how do I update the-  workspace, re-run setup, lightweight image, install on demand, command not-  found, missing tool, apt-get install, is ffmpeg installed.------# Hydrogen Workspace = a thin golden image + a live first install--Since image **v24-thin** (2026-08-13, John's call: "simple golden image, setup-steps configure everything") the golden image is deliberately MINIMAL. What the-tarball actually contains:--- Ubuntu base + systemd (PID 1), the adom user, the folder contract-  (`~/project` is the workspace root)-- **code-server** (the VS Code backend) + its systemd unit-- systemd units for the relay and shotlog, guarded by `ConditionPathExists` so-  they wait quietly until setup installs their binaries-- the **adom-wiki CLI seed** at `~/.local/bin/adom-wiki` — the installer that-  brings everything else-- a first-boot oneshot that mints the per-import `/etc/adom-distro-id`--**Everything else arrives at setup time.** The setup cascade's update-packages-step runs `adom-wiki pkg install adom/hydrogen-windows-bootstrap`, the leaf-package whose dependency tree pulls hydrogen-bootstrap → adom/core and the-whole ecosystem: ~150 skills, ~22 packages, the 8 Adom CLIs, and ALL editor-extensions (adom-theme, adom-vscode, anthropic.claude-code). Measured cost:-about 7 minutes on a fresh install — that is the tradeoff for an image that is-125MB smaller and for day-one installs that are ALWAYS current (no stale baked-package can ever exist again; the slug-migration class of bug is structurally-impossible).--## Why this changed (history)--Images v15–v23 were FAT: the whole toolchain was baked at image-build time,-which made first runs fast but froze whatever package versions (and package-NAMES) existed on bake day into every container for months — the root cause of-the retired-slug pinning bug (adom/[email protected] sitting next to-adom/hydrogen-bootstrap on live machines). If you are inside an older fat-image-workspace, everything below still applies to you; the content is the same,-only WHO installed it differs.--## How updates work (same in both eras)--- The registry updater keeps packages current: `adom/hook` runs-  `adom-wiki pkg update` on agent activity, and ah's setup gates on-  hydrogen-bootstrap matching the registry's latest.-- The IMAGE only changes when ah ships a new pinned tarball-  (`/etc/adom-golden-version` says which rootfs you're on;-  `/etc/adom-tarball-version` says what ah imported). An image bump requires a-  workspace re-import (Virgin Reset) — package updates never do.-- Force a full converge by hand:-  `adom-wiki pkg install adom/hydrogen-windows-bootstrap` (idempotent).--## "Command not found" / missing tools--The image intentionally ships no long-tail tooling. Get tools on demand:-`apt-get install <tool>` (via sudo where available), `apt python3-<lib>` for-Python libraries (PEP-668: prefer apt; `pip --break-system-packages` or a venv-otherwise), and `adom-wiki discover search -q <capability>` for Adom packages.-The Claude Code CLI is installed by the `install-claude-cli` setup step and-self-updates thereafter.--## Answering common user questions--- "Where did all these skills come from?" → the setup cascade's first package-  install (fat-era workspaces: baked into the image). They live flat in-  `~/.claude/skills/` and update via the registry.-- "Why did first-run setup take a few minutes?" → the live toolchain install;-  it is downloading the current versions of everything rather than using-  months-old baked copies.-- "How do I update the workspace?" → you almost never need to; the registry-  updater converges packages continuously. A tarball-version bump (rare, OS-  level) comes through ah and needs a re-import.