Adom Hydrogen

@@ -45,7 +45,7 @@ On first launch Hydrogen runs a fully automated **20‑step setup cascade**. It  Hydrogen's first and biggest job is creating the environment everything else runs in. It provisions a dedicated WSL2 Ubuntu distro called **`Adom‑Workspace`** — enabling the WSL2 feature first if your PC doesn't have it yet (the one point where Hydrogen may need a reboot, after which it picks right back up on its own), then downloading and SHA‑verifying a pre‑baked ~400 MB "golden" image, importing it, and starting code‑server (VS Code in the browser) inside it. The cascade refuses to advance until that environment is genuinely up and answering. From there it wires the editor to the platform in a handful of quick steps — reloading to activate the pre‑baked `adom‑vscode` extension, writing the Adom platform URLs, injecting and validating your Adom session token so every tool authenticates as you, and applying a clean dark VS Code layout. -![Building the WSL2 Adom‑Workspace](screenshots/01_ensure-workspace_done.png)+![The setup cascade, reopened any time from the Adom menu: every step, its live output stream, and per-step run/rollback](screenshots/setup-steps.png)  ### 2 · It connects everything, then asks you to sign in to Claude — once @@ -112,6 +112,36 @@ Click the teal Adom logo in the top-left corner for the app-level menu:  ![The Adom menu: app-level actions, Bridge, container control, and admin](screenshots/adom-menu.png) +### Settings++One dialog for how the whole app looks and behaves: color schemes that restyle Hydrogen and the editor together (Adom Studio is the default; Adom Studio Dark, Kickstand, and Slate are a click away), the editor code font, behavior and wake options, the updater, and an **Adom Bridge** section for the companion app.++![Settings: appearance, behavior, wake, updater, and Adom Bridge](screenshots/settings-dialog.png)++### Ports++A live map of every port Hydrogen binds, across both layers: the Windows frontend (Control API, Container Proxy, WebView2 CDP, discovery, the direct API, the Bridge liveness beacon) and the Linux container backend (code-server, the relay, shotlog, bridges). Read live on every refresh; mirrored networking status up top explains how the frontend reaches the backend.++![Ports: the live two-layer port map](screenshots/ports-dialog.png)++### API Explorer++Browse and try every endpoint of Hydrogen's control API, the same API external AIs and scripts drive. Each endpoint documents itself; you can fire test calls from inside the dialog.++### Setup Steps++Reopens the first-run cascade any time: every step with its live output stream, per-step Run and Rollback, and the Virgin Reset entry point. The screenshot in the First Run section above is this panel.++### About++What Hydrogen is, in one card: the version and build you are running, and the short story of the app and Adom Bridge.++![About Hydrogen](screenshots/about-dialog.png)++### Container and admin++The Container group restarts or stops the Linux container without leaving the app. Admin holds Setup Steps, **Virgin Reset** (wipe the container and re-run the full first-run setup from the golden image), and the **Browser Picker Manager** for per-domain link routing choices.+ ## AI that designs alongside you  Claude Code is built into both the editor and the terminal and signed in with your own subscription, so the AI isn't a sidebar — it's a teammate that can read your project, search the wiki, install the right skill, and (through Bridge) drive your real EDA tools. On first run it already opens conversations that map your design stack and offer to wire your KiCad work to **live pricing** that re‑quotes as your board changes. Everything stays **opt‑in**: the AI proposes, you decide what actually runs.

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯