Adom Hydrogen (platform base)

⋯ 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 ⋯

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.5.76",+  "version": "0.5.77",   "description": "Hydrogen'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 on ANY platform: the runtime-neutral hydrogen-* skills and the generic editor configuration (Claude Code CLI + extension, VS Code settings, trusted domains). Platform-specific layers depend on THIS: adom/hydrogen-windows-bootstrap (WSL2), adom/hydrogen-mac-bootstrap, adom/hydrogen-ubuntu-bootstrap. The reference design other orgs copy to build their own bootstrap on adom/core.",   "org": "adom",   "tags": [

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.5.76",+  "version": "0.5.77",   "description": "Hydrogen'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 on ANY platform: the runtime-neutral hydrogen-* skills and the generic editor configuration (Claude Code CLI + extension, VS Code settings, trusted domains). Platform-specific layers depend on THIS: adom/hydrogen-windows-bootstrap (WSL2), adom/hydrogen-mac-bootstrap, adom/hydrogen-ubuntu-bootstrap. The reference design other orgs copy to build their own bootstrap on adom/core.",   "org": "adom",   "tags": [@@ -65,4 +65,4 @@     "connect grok"   ],   "changelog": "0.5.68: memory guardrails in every Hydrogen workspace (section 4g): earlyoom stops a runaway job at 8% free memory before the workspace thrashes, code-server's inherited OOM protection is removed so the runaway is the one chosen, and swappiness drops to 10. Proven on AdomLapper: a 12 GB hog stopped in 39 s, code-server untouched."-}+}\ No newline at end of file

⋯ 1 unchanged line ⋯

@@ -4,8 +4,7 @@ description: >   What Hydrogen (ah) and Adom Bridge (ab) are, what each does, and how   they work together — so the AI in the workspace knows it has HANDS on the   user's real operating system. Hydrogen is the workspace app the user looks at; ab is-  the bridge that reaches the user's actual Windows machine (macOS/Linux coming-  soon) to create files & folders, run shell commands, take OS screenshots,+  the bridge that reaches the user's actual machine (Windows, macOS, Ubuntu) to create files & folders, run shell commands, take OS screenshots,   launch apps, open browsers (Pup / native), and drive KiCad / Fusion 360. Hydrogen   bundles ab during install and runs it in embedded mode, but ab is a standalone   product that ALSO connects Adom cloud containers to a user's machine. Hydrogen also@@ -37,7 +36,7 @@ create that file on your Desktop, screenshot your screen, and open it in KiCad."  ## Two names, one product (read before typing a command) -- **Inside the workspace** the CLI is `adom-bridge` (the retired name `adom-bridge-cli` still works as an alias; do not write it in new examples).+- **Inside the workspace** the CLI is `adom-bridge`. - **On the Windows side** the CLI binary is `adom-bridge-cli.exe`, because `adom-bridge.exe` is the Adom Bridge GUI itself. So a PowerShell or cmd example that runs the CLI on the host says `adom-bridge-cli.exe`; `taskkill /IM adom-bridge.exe` and the `%LOCALAPPDATA%\Adom Bridge\adom-bridge.exe` launch path refer to the GUI and are correct as written.  ## Two apps, two jobs@@ -90,7 +89,7 @@ bridge is — so recording / multi-monitor / glob-pull aren't available until ab is up. Screenshots, window control, files, shell, captions, notifications and the KiCad/Fusion/browser bridges all work off Hydrogen's built-in bridge regardless. -## What ab/Hydrogen let you do on the user's real Windows machine+## What ab/Hydrogen let you do on the user's real machine  All via the `adom-bridge` CLI from inside the workspace. Rather than re-document every verb here, this is a **capability map → the focused skill**:@@ -105,7 +104,7 @@ re-document every verb here, this is a **capability map → the focused skill**: | **Desktop notifications** | `notify_user` (title/body/level + action buttons) | **hydrogen-notifications** (platform bootstrap) | | **On-screen captions** | `caption` (always-on-top click-through overlay) | **hydrogen-captions** (platform bootstrap) | | **Open browsers** | `browser_*` (Pup) | **hydrogen-open-url** (platform bootstrap), `pup` |-| **Drive KiCad / Fusion 360 / Pup** | `kicad_*`, `fusion_*`, `browser_*` | the platform bridge skill set (**hydrogen-bridges** on Windows, the adom-bridge-macos skills on mac) |+| **Drive KiCad / Fusion 360 / Pup** | `kicad_*`, `fusion_*`, `pup_*` | the platform bridge skill set (**hydrogen-bridges** on Windows, the adom-bridge-macos skills on mac) | | **Embedded mechanics (tray/lifecycle)** | `desktop_embedded_*` | **hydrogen-embedded-bridge** (Windows bootstrap) — ab-served |  For the complete verb list run `adom-bridge list_commands`.@@ -175,7 +174,7 @@ adom-bridge hd_screenshot        # window-bounded Hydrogen shot (resize <1500px adom-bridge hd_log               # tail Hydrogen's log adom-bridge hd_launch            # start Hydrogen detached # Direct Hydrogen control API (HTTP, no shell-escaping pain):-adom-bridge hd_api '{"method":"POST","path":"/setup/run-all","body":{}}'+adom-bridge hd_api '{"method":"GET","path":"/setup/state"}' adom-bridge hd_api '{"method":"GET","path":"/health"}' ``` `hd_api` hits Hydrogen's **control API**, discovering its real port from

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -116,8 +116,8 @@ AI already keeps in the workspace; never print the tokens, print only the number | Grok Bot | Windows app, no file in the workspace: `grok_settings {"page":"usage"}` then `grok_screenshot` (see the `grok-account` skill) | the plan, weekly percent and reset, the on-demand cap | | Kimi Code | not mapped yet | | -The Title Bar widgets `claude-usage`, `codex-usage` and `antigravity-usage` show the same numbers-for this workspace (the `hydrogen-widget` skill).+On Windows, the Title Bar widgets `claude-usage`, `codex-usage` and `antigravity-usage` show the+same numbers for this workspace (the `hydrogen-widget` skill in the Windows layer).  ```bash python3 - <<'PY'

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -149,23 +149,6 @@ background and runs the Adom orbital animation until the app URL truly loads. Apps bundle nothing and opt into nothing. `launch.console: "hide"` mutes the command transcript (never the failures) when the output would be noise. -## Driving the dock from an AI thread (the ralph loop)--You do not click. ah's control API (see the hydrogen-api skill for the base URL and-`hd_api`) presses the dock for you and hands back what happened, so the loop is:-change the app in the container, launch it through the API, read the transcript, look-at the dashboard, repeat. Every response carries `_hints` saying what to do next.--| call | what it does |-|---|---|-| `GET /dock/apps` | every app: `id`, `wiki_repo`, `name`, `mode`, `running`, `launching`, `tab_open` (from the layout, the truth after a reload), `url`, `health`, `last_launch` summary |-| `POST /dock/launch {id, relaunch?, timeoutSec?}` | presses the button. `relaunch` defaults to true: close the tab, recreate it, run the steps again. Waits for the launch to finish (default 240 s) and returns `ok`, `url`, `reason`, `status`, `elapsed_ms`, `tab_open` and `console`, the same transcript the user sees in the loading screen: every status phase, every command and its container stdout/stderr, the failing step verbatim |-| `POST /dock/close {id}` | removes the app's webview tab and forgets its running state. Does not stop the app's container process; the next launch's serve retires it, or stop it with `/workspace/exec` |-| `POST /dock/refresh {full?}` | re-reads the curated apps.json now (with `full:true` also every display, manifest path and hero); call it after publishing a new apps.json or dockbar.json instead of waiting for the 6-hour poll |--`id` is the dock id (`kicad`, `nb`, `codex`), the wiki repo (`adom/nb-bridge`) or its slug.--```bash # the loop, from a thread adom-bridge hd_api '{"method":"POST","path":"/dock/launch","body":{"id":"nb","timeoutSec":300}}' #   -> ok, url, console[]   (ok:false -> reason + the failing step's output in console)@@ -275,17 +258,6 @@ canonical name in conversation, every time, even when the user used a different vocabulary is worse than modelling it: they will pick the name up from your reply, and the next time they will ask for it precisely. -## Back to the defaults (1.0.222)--Right-click the rail > **Reset to defaults (what every Adom user sees)**, click it again to-confirm, or `POST /dock/reset`. It drops the PERSONAL layer only: apps you added locally, pins,-the draft manifest URL override, the rail's width and collapsed state, the reveal flags and the-caches, then reloads the curated list from the wiki. The behaviour toggles in Settings > Dock Bar-(arm delay, alt-pin, collapse on launch...) are settings, not additions, and stay. The API answer-lists what was cleared and the curated app count:--```bash-curl -sX POST "$BASE/dock/reset" # -> {"ok":true,"cleared":["locally added apps","pins","rail width"],"apps":11} ``` @@ -300,3 +272,5 @@ is adom-curated and is ONLY a list: which apps appear and in what order, plus inline launch there overrides and freezes the manifest the app maintains. Being on it is not required to be dock-ready. To request listing, open an issue on the adom/hydrogen-desktop wiki page.++Driving the dock from an AI thread (`/dock/*` on the control API) and resetting it to the defaults are Windows-only today: see **hydrogen-dock-windows**.

⋯ 1 unchanged line ⋯

@@ -31,8 +31,8 @@ see "Why two paths" below) and runs your JS there, returning the value. ## Finding the control port + reaching it from the workspace  The control API port is **dynamic** (auto-resolves conflicts per launch). From inside-the workspace, reach Hydrogen on `127.0.0.1` (WSL2 mirrored networking shares loopback with the-Windows host). Read the live control URL from the discovery file `~/.adom/hydrogen-control-url`+the workspace, reach Hydrogen at the host address the discovery file names (`127.0.0.1` on Windows, where WSL2+mirrored networking shares loopback; `adom-host` on macOS). Read the live control URL from the discovery file `~/.adom/hydrogen-control-url` (your non-interactive Bash shells don't source `.bashrc`/`profile.d`, so the env var alone is unreliable): 

⋯ 1 unchanged line ⋯

@@ -77,7 +77,7 @@ from anywhere. | `hydrogen.editor_font_size`, `hydrogen.color_scheme`, `hydrogen.wake_heal`, ... | Hydrogen | The Settings dialog's preference tree. | | `hydrogen.runtime.<machine>` | Hydrogen | Live runtime identity, published at launch + every 4h: a JSON string `{host, control, proxy, cdp, code_server, instance_id, pid, install_path, version, ts}`. `<machine>` is the lowercase sanitized computer name. | | `bridge.container.<id>` | Adom Bridge | A container connection ab dials (may appear as legacy `desktop.container.<id>` until ab's rename ships). |-| `bridge.runtime.<machine>` | Adom Bridge | ab's live runtime identity (planned mirror of Hydrogen's entry, adom/adom-bridge#72). |+| `bridge.runtime.<machine>` | Adom Bridge | ab's live runtime identity, also the Adom Mesh directory record (node id, relay, version). |  ## Using a runtime entry (discovery) 

@@ -37,10 +37,8 @@ on Windows, `hydrogen-mac-bootstrap` on macOS. | **hydrogen-dock** | The dock bar (app launcher rail) and how any wiki app becomes a card in it — dockbar.json manifest, launch steps, AI threads. | | **hydrogen-doctor** | The one-click full-stack health scan (Doctor) with safe one-click fix; GET/POST /doctor. | | **hydrogen-eda-discovery** | EDA tool discovery / setup flow. |-| **hydrogen-editor-state** | The Editor State Machine — knowing the true VS Code / Claude conversation state, and the hard typing invariants. | | **hydrogen-eval** | Inject JS into any Hydrogen surface (shell/workbench/wiki/Claude) via /eval-in — add-ons, overlays, highlights, drive UI. | | **hydrogen-key-values** | The user's cloud key-value store (Carbon KV): hydrogen.* / bridge.* keys, read/write, conventions. |-| **hydrogen-lightbulb** | The 💡 sample-prompts menu in the title bar and sample-prompts.json. | | **hydrogen-monitor** | Real-time SSE event stream + Monitor-tool patterns for watching workspace mutations. | | **hydrogen-naming** | The naming doctrine: Hydrogen/ah, Bridge/ab, and WHY installers/shortcuts MUST say "Adom Hydrogen". | | **hydrogen-overview** | This index. |

⋯ 1 unchanged line ⋯

@@ -39,7 +39,7 @@ adom-bridge pup_screenshot '{"sessionId":"<task-name>"}'   # verify what's on sc ```  Every pup verb starts with `pup_` (`pup_navigate`, `pup_eval`, `pup_click`, `pup_close_window`,-...). The old `browser_*` names no longer exist and answer `unknown_verb`; `pup_describe '{}'`+...). `pup_describe '{}'` lists every verb the installed pup has.  - Reuse ONE window per task via a stable `sessionId` — open tabs in it rather

@@ -28,10 +28,6 @@ Preferences are saved per-user (`saveUserSetting` → `PATCH /user/hydrogen/sett and persist across sessions. Setting a key back to its default removes the override. Keys are dotted (`section.subsection.name`). -> **The Settings search box is currently a no-op** — it's a placeholder input-> with a `<!-- TODO: Implement settings search -->` in `SettingsDialog.svelte`.-> Typing in it filters nothing yet; scroll/scan the sections instead.- ## Sections, keys, and what each does  ### general@@ -56,7 +52,7 @@ override. Keys are dotted (`section.subsection.name`). | Key | Default | What it does | |---|---|---| | `desktop.show_console_on_startup` | `false` | Show the debug console window when Hydrogen starts (→ "show the console on startup") |-| `desktop.launch_on_boot` | `true` | Auto-launch Hydrogen when Windows starts (→ "make Hydrogen launch on boot" / "stop Hydrogen starting with Windows" = set false) |+| `desktop.launch_on_boot` | `true` | Auto-launch Hydrogen when the computer starts (→ "make Hydrogen launch on boot" / "stop Hydrogen starting at login" = set false) |  ### adom_desktop  *(the embedded Adom Bridge / ab that Hydrogen runs)* When Hydrogen is running it takes over ab, so ab's options live here. See

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

@@ -35,8 +35,3 @@ Publish it as an `adom-wiki` package, then add it as a **dependency** of the rig   for platform-specific — see **hydrogen-skill-loop** for the publish recipe). The hook's re-resolve delivers it fleet-wide within ~30 minutes of users prompting. -## The retired daemon (history)-`adom-workspace-updater` (a systemd timer converging a wiki manifest) previously delivered-tooling in-place. It was retired 2026-07-16 in favor of the registry updater; legacy distros are-migrated off it automatically by its final self-update. If you still see it:-`systemctl status adom-workspace-updater.timer` should be disabled/absent on a migrated workspace.

⋯ 1 unchanged line ⋯

@@ -34,9 +34,9 @@ workspace, next to their editor. Nothing else qualifies.  ## ⭐ URLs for YOUR OWN servers: direct port, NOT /proxy/<port>/ -Hydrogen Desktop runs the workspace in WSL2 with **mirrored networking ON by default**:-every port you bind inside the workspace is reachable DIRECTLY from Windows at-`http://localhost:<port>/`. So when you launch a web server on port 8850, the webview URL is:+Hydrogen Desktop makes every port you bind inside the workspace reachable DIRECTLY from the+host at `http://localhost:<port>/` (WSL2 mirrored networking on Windows, Lima port forwarding+on macOS). So when you launch a web server on port 8850, the webview URL is:  ``` http://localhost:8850/          ✅ the Hydrogen Desktop way@@ -47,7 +47,7 @@ The `/proxy/<port>/` route through code-server (what `VSCODE_PROXY_URI` points a Web Hydrogen parity and as the fallback when mirrored networking is off. On Hydrogen Desktop it costs you: an extra code-server hop, absolute-path assets (`/style.css`) break, and the page dies whenever the editor reloads. Use the direct port; if it does not answer, check-mirrored networking first (the `hydrogen-networking` skill) before reaching for /proxy.+the host port mapping first (the `hydrogen-networking` skill) before reaching for /proxy. (Opening a /proxy URL still works — the tab-open response will hint you back to the direct form.)  ## ✅ The exact command (idempotent — safe to re-run)@@ -128,14 +128,3 @@ POST http://127.0.0.1:{control}/workspace/tabs (`definitions` skill / wiki.adom.inc/adom/definitions) for the full surface vocabulary. -## hbw — Hydrogen's standalone browser window (the fourth surface)--Under Hydrogen there is one more surface: **hbw**, Hydrogen's standalone built-in-Tauri browser window (picker label "Hydrogen Browser Window", destination id-`webview-window`, window label `hbw-*`). It is a separate OS window Hydrogen manages-directly — bigger than a pane tab, still not a real browser. Open one first-class via-`POST /hbw/open {"url": ...}` on Hydrogen's control API (0.1.113+), or pick "Hydrogen Browser-Window" in the Browser Picker. The surface shortlist: **wv** (this skill's webview-panel; Hydrogen's pane tab inside Hydrogen), **extwv** (the real-browser pane tab for embed-blocked-sites, above), **pup**, **nb** (the user's native browser via abe), **hbw**. VS-Code's Simple Browser is NEVER one of them.

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯

⋯ 1 unchanged line ⋯