Adom Hydrogen (platform base)

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.5.50",+  "version": "0.5.51",   "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": [@@ -33,4 +33,4 @@     "hydrogen editor configuration",     "where do hydrogen skills come from"   ]-}+}\ No newline at end of file

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.5.50",+  "version": "0.5.51",   "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": [

@@ -1,7 +1,7 @@ --- name: hydrogen-widget description: "Build, list, open and drive Hydrogen Widgets: small live panels in Hydrogen Desktop's Title Bar (Claude usage, Codex usage, a clock, or your own), each served by a binary inside the workspace and mounted in a sandboxed slot. Covers the hydrogen-widget.json facet a wiki repo carries (alone, or next to its dock manifest and project workspace), the per-widget page the pulldown links to, the launch contract (HYDROGEN_WIDGET_ID / _PORT / _SLOT / HYDROGEN_PROXY_PORT, the health URL, the explicit takeover, stop-first relaunch), the tall and compact layouts, vendor marks, private repos (read with the user's session), the curated list on adom/hydrogen-bootstrap, the Hydrogen Widgets pulldown, and the control API (GET /widgets, POST /widgets/open|close|navigate|refresh|menu, GET /widgets/status) so an AI can do all of it with no mouse. Trigger words: hydrogen widget, hydrogen-widget, title bar widget, widgets pulldown, widget slot, claude usage widget, codex usage widget, tokens left widget, usage meter in the title bar, hydrogen-widget.json, /widgets/open, make a widget, add a widget to hydrogen, private widget, widget SDK."-version: 1.5.1+version: 1.5.2 ---  # hydrogen-widget: small live panels in Hydrogen Desktop's Title Bar@@ -64,8 +64,13 @@ reason so the user can see it, and `/widgets/close` removes it. The launch log i    came from the checkout, with `HYDROGEN_WIDGET_ID`, `HYDROGEN_WIDGET_PORT`,    `HYDROGEN_WIDGET_SLOT` and `HYDROGEN_PROXY_PORT` in its environment plus the workspace env    every login shell has (`ADOM_HD_CONTROL_URL`, `ADOM_HYDROGEN_URL`).-5. Hydrogen polls `http://<port>.localhost:<proxy>/<health.url>` (its subdomain port proxy)-   until it answers, up to `health.timeout_seconds`, then navigates the slot to that page.+5. Hydrogen asks for `http://127.0.0.1:<port>/<health.url>` from inside the workspace until it+   answers 2xx or 3xx, up to `health.timeout_seconds`, then navigates the slot to+   `http://<port>.localhost:<proxy>/` (its subdomain port proxy). The probe runs in the+   workspace on purpose: the proxy's own error page while the distro boots is not an answer.+   Before any of this, if the workspace is not running yet (a full quit and relaunch boots the+   distro for a minute or more), the slot says "Waiting for the workspace" and waits, up to+   ten minutes; nothing is installed or launched until it is up. 6. Your page owns the slot from then on: poll your own JSON, redraw, push whatever you want.    Explicit takeover, when you want the slot before health is up or want another page:    `POST $ADOM_HD_CONTROL_URL/widgets/navigate {"id": $HYDROGEN_WIDGET_ID, "url": "..."}`.