Adom Bridge

@@ -62,7 +62,7 @@ One desktop can connect to many containers, many desktops can share one containe  ## Running under Adom Hydrogen -When Adom Hydrogen is present it runs Adom Desktop embedded: hidden window, HD-owned permission prompts, and a distinct taskbar tile. If HD ever goes away, Adom Desktop comes back standalone so your machine stays reachable. Deep dive: [how AD interacts with Adom Hydrogen](docs/adom-hydrogen.md).+When Adom Hydrogen is present it runs Adom Desktop embedded: hidden window, HD-owned permission prompts, and a distinct taskbar tile. If Hydrogen ever goes away, Adom Desktop comes back standalone so your machine stays reachable. Deep dive: [how AD interacts with Adom Hydrogen](docs/adom-hydrogen.md).  ## The laptop GUI @@ -96,7 +96,7 @@ Adom Desktop polls the wiki manifest on launch and every 4 hours. Every release  You set your preference once in **Settings, Updates**: Prompt (default), Auto, or Off. A normal release carries no priority; the emergency tier is a deliberate, per-incident action. -**When a normal update actually installs.** Adom Desktop lives in the tray and can run for weeks without a restart, so a Prompt-mode update you never click would never install. The restart schedule closes that: once an update is downloaded AND you have been away from the keyboard for about 15 minutes AND AD is not mid-task, it installs and relaunches quietly. It is idle-based, not a fixed clock, so it never interrupts active work or an overnight job, and restarting Adom Desktop has no effect on your other apps (it reconnects in seconds). Turn it off in Settings, Updates, "Restart when idle to finish updates," and a Prompt-mode update simply waits for your click. Auto installs immediately; Off never auto-installs (except an Emergency release). Embedded in Adom Hydrogen, HD owns the restart timing.+**When a normal update actually installs.** Adom Desktop lives in the tray and can run for weeks without a restart, so a Prompt-mode update you never click would never install. The restart schedule closes that: once an update is downloaded AND you have been away from the keyboard for about 15 minutes AND AD is not mid-task, it installs and relaunches quietly. It is idle-based, not a fixed clock, so it never interrupts active work or an overnight job, and restarting Adom Desktop has no effect on your other apps (it reconnects in seconds). Turn it off in Settings, Updates, "Restart when idle to finish updates," and a Prompt-mode update simply waits for your click. Auto installs immediately; Off never auto-installs (except an Emergency release). Embedded in Adom Hydrogen, Hydrogen owns the restart timing.  Deep dive on every update lane (app, bridges, container package, skills) and the network-traffic math: [how updates work](docs/updates.md). @@ -150,7 +150,7 @@ Headless Python scripting and renders.  ![Adom Hydrogen bridge card](docs/bridge-card-hd.png) -The local dev-environment app AD can embed into; AD relays HD's runtime state and drives its lifecycle.+The local dev-environment app AD can embed into; AD relays Hydrogen's runtime state and drives its lifecycle.  Install a third-party bridge by pasting its manifest URL, or `bridge_install {"manifestUrl":"..."}`. Build one with the [Bridge SDK](https://wiki.adom.inc/adom/adom-desktop-bridges). @@ -163,9 +163,9 @@ AD's window carries a mode-specific app identity, so the taskbar button swaps it | Icon | Mode | Taskbar name | Meaning | |:---:|:---|:---|:---| | <img src="docs/taskbar-standalone.png" alt="Standalone: muted Adom tile" width="88"> | **Standalone** | Adom Desktop | AD running on its own. The default for a normal install. |-| <img src="docs/taskbar-embedded.png" alt="Embedded: vivid Adom tile" width="88"> | **Embedded** | Adom Desktop HD Embedded | Adom Hydrogen launched AD and drives its lifecycle. |+| <img src="docs/taskbar-embedded.png" alt="Embedded: vivid Adom tile" width="88"> | **Embedded** | Adom Desktop Hydrogen Embedded | Adom Hydrogen launched AD and drives its lifecycle. | -Muted "Adom Desktop" = AD by itself; vivid "Adom Desktop HD Embedded" = HD has the helm. Each mode is a registered Windows app identity, and flipping the window between them makes the shell rebuild the button with the other identity's icon and name. Because the modes are distinct identities, a taskbar pin made in one mode shows the running window as a separate button while AD is in the other mode.+Muted "Adom Desktop" = AD by itself; vivid "Adom Desktop Hydrogen Embedded" = Hydrogen has the helm. Each mode is a registered Windows app identity, and flipping the window between them makes the shell rebuild the button with the other identity's icon and name. Because the modes are distinct identities, a taskbar pin made in one mode shows the running window as a separate button while AD is in the other mode.  ## Window identity (branding a window the AI drives) @@ -182,7 +182,7 @@ These verbs inspect any icon you pass and return an `iconCheck` that explains, i  ![Settings](docs/settings.png) -Auto-connect behavior, the update channel (**prompt** / auto / off) and *restart when idle to finish updates*, the shell-approval preference, Adom Hydrogen integration (including *exit when HD exits*), and runtime prewarming. While embedded in HD, HD-owned preferences show as *managed by Adom Hydrogen*.+Auto-connect behavior, the update channel (**prompt** / auto / off) and *restart when idle to finish updates*, the shell-approval preference, Adom Hydrogen integration (including *exit when Hydrogen exits*), and runtime prewarming. While embedded in Hydrogen, HD-owned preferences show as *managed by Adom Hydrogen*.  ## Security and the approval gate @@ -190,7 +190,7 @@ Auto-connect behavior, the update channel (**prompt** / auto / off) and *restart  **The trust boundary is install-consent plus the localhost bind.** Installing the app (and each bridge) is you granting permission for the AI to drive your machine; if you do not want that, uninstall. And the app plus every bridge binds `127.0.0.1` **only, never `0.0.0.0`**, so a caller must already be a program you installed on your own machine to reach it. No network attack surface by construction. -On top of that, the **remote cloud-AI path is approval-gated.** Verbs that run code or change the machine (`shell_execute`, `run_script`, `launch_process`, `write_file`, `registry_*`, `process_kill`, and so on) require a human grant when they arrive over the *relay*: **+1hr / +24hr** (time-boxed), **Bypass** (indefinite), or **Revoke**. The grant is human-only; local callers (your CLI, HD, bridges) are trusted by transport and never prompt; read-only verbs are never gated.+On top of that, the **remote cloud-AI path is approval-gated.** Verbs that run code or change the machine (`shell_execute`, `run_script`, `launch_process`, `write_file`, `registry_*`, `process_kill`, and so on) require a human grant when they arrive over the *relay*: **+1hr / +24hr** (time-boxed), **Bypass** (indefinite), or **Revoke**. The grant is human-only; local callers (your CLI, Hydrogen, bridges) are trusted by transport and never prompt; read-only verbs are never gated.  Deep dive: [permissions](docs/permissions.md) (what each Approve choice means, and how to revoke).