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.64",+  "version": "0.5.65",   "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": [@@ -43,6 +43,9 @@     "ai toolbar button missing",     "no duplicate cli",     "agent harness design",-    "auth oracle"+    "auth oracle",+    "install grok",+    "grok bot",+    "connect grok"   ] }

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.5.64",+  "version": "0.5.65",   "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": [@@ -59,6 +59,9 @@     "ai toolbar button missing",     "no duplicate cli",     "agent harness design",-    "auth oracle"+    "auth oracle",+    "install grok",+    "grok bot",+    "connect grok"   ] }\ No newline at end of file

@@ -59,6 +59,18 @@ account the user may not have.   bytes, data dirs, and a `dupes` list) and the dialog's "?" tooltip shows it, so a   regression is visible to the user without anyone reading logs. +## Desktop apps: the host_app kind (Grok Bot)++`Provider.host_app` names an Adom Bridge verb prefix (`grok`). Such a provider has no CLI+and no extension in the container: `host_app_record` asks the bridge on THIS desktop+(`<prefix>_readiness` for installed and running, `<prefix>_status.webhookBound` for+"connected"), and the routes map onto bridge verbs (`_open`, `_webhook_ensure`, `_login`,+`_logout`) while Install is the dock's own launch for the same id (`dock_command launch`),+so the Grok Bot dashboard does the guiding. Two lessons: send bridge verbs with+`ad::send_verb_timeout` (no `app` field; with `app:"desktop"` ab turned `grok_readiness`+into `desktop_grok_readiness`), and treat ab's "Unknown verb" as "bridge not installed"+(Install), never as "Adom Bridge down". adom-vscode draws nothing for a host app.+ ## Sign-in: detection (the oracles)  Each Provider has an `oracle_cmd`, a shell command run in the container whose stdout decides

@@ -32,7 +32,13 @@ tell the user to open Hydrogen rather than improvising an install. | `kimi` | Kimi Code | moonshot-ai.kimi-code (user installs) | `kimi` 2.x, standalone (the extension ships no CLI) | yes, `~/.kimi-code/credentials` | | `antigravity` | Antigravity | google.google-antigravity (user installs) | `agy`, the copy the extension downloads to `~/.gemini/bin/agy` | yes, by Hydrogen: it copies the Google token between `~/.gemini/jetski-standalone-oauth-token` (extension) and `~/.gemini/antigravity-cli/antigravity-oauth-token` (CLI) | -`grok` is listed as coming soon and has no install or sign-in yet.+`grok` is **Grok Bot**, a desktop app on the user's computer reached through Adom Bridge's+`grok_*` verbs, not an extension or a CLI. For it, `installed` means Grok Bot.exe is on this+desktop (`grok_readiness`), `authed` means the Adom Bridge webhook is bound (`grok_status`),+`/agents/install` opens the dock's Grok Bot dashboard (which installs the grok-bridge package+and walks the rest), `/agents/login` starts the app and binds the webhook (opening its+sign-in if the human still has to act), `/agents/open-panel` launches the app. Its account+sign-in happens inside the app; the bridge never types passwords. No toolbar button.  ## What each call does