Adom Bridge

@@ -56,7 +56,7 @@ container registers itself, using a one-line command that writes the connection into your account. After that, the flow on your side is just:  1. Install Adom Bridge on Windows (from-   `https://wiki.adom.inc/adom/adom-desktop`).+   `https://wiki.adom.inc/adom/adom-bridge`). 2. Sign in with your Adom account. 3. The container appears in your Connections list and connects automatically. 

@@ -112,6 +112,6 @@ copy refreshes when skills are synced. That is normal, and usually invisible. ## For bridge authors  If you are publishing a bridge rather than using one, the Bridge SDK on the-`adom-desktop-bridges` wiki page has the publishing detail: what belongs in each artifact,+`adom-bridge` wiki page has the publishing detail: what belongs in each artifact, how to declare `docs` so the skill package name resolves, and how to ship both halves together.

@@ -120,14 +120,14 @@ This page covers the lifecycle: how bridges run, install, and update. How to act USE a bridge (its verbs, workflows, and recipes) is documented by the bridge itself, on its own wiki page, which is also where its skill package for AI callers ships from: -- Puppeteer: wiki.adom.inc, the `adom-desktop-puppeteer-bridge` page-- KiCad: the `adom-desktop-kicad-bridge` page-- Fusion 360: the `adom-desktop-fusion-bridge` page+- Puppeteer: wiki.adom.inc, the `pup-bridge` page+- KiCad: the `kicad-bridge` page+- Fusion 360: the `fusion-bridge` page - Blender: the `adom-desktop-blender-bridge` page - Native Browser: the `adom-browser-extension` page  Each card's wiki link takes you straight there. To build a bridge of your own, start-with the Bridge SDK on the `adom-desktop-bridges` wiki page.+with the Bridge SDK on the `adom-bridge` wiki page.  ## Private bridges 

@@ -11,7 +11,7 @@ container, a local script, you at a terminal) asks it to do that work. There are two homes for the same CLI:  - **Cloud Linux container**: installed by the package, `adom-wiki pkg install-  adom/adom-desktop`, which lays down the `adom-bridge` binary and the Claude skill+  adom/adom-bridge`, which lays down the `adom-bridge-cli` binary and the Claude skill   set. The container also runs the relay server the desktop connects to. - **Windows, next to the GUI**: the Adom Bridge installer bundles   `adom-bridge-cli.exe` into `%LOCALAPPDATA%\Adom Bridge\` and adds that directory to

@@ -30,7 +30,7 @@ already knows what Adom Bridge can do and how to call it. ## How the skill auto-link works  Each skill Adom Bridge installs lives in its own folder, for example-`~/.claude/skills/adom-desktop/`, and contains a small marker file named+`~/.claude/skills/adom-bridge/`, and contains a small marker file named `.adom-managed`. The marker means "Adom Bridge owns this folder":  - On every Adom Bridge launch, each managed skill is refreshed if the bundled copy@@ -94,7 +94,7 @@ it by full path:  **The skills did not appear in my agent.** They are linked when Adom Bridge launches, so start (or restart) Adom Bridge, then check for folders like-`~/.claude/skills/adom-desktop/`. If you set `ADOM_SKILLS_LINK=0`, the link+`~/.claude/skills/adom-bridge/`. If you set `ADOM_SKILLS_LINK=0`, the link is disabled.  ## Related docs

@@ -36,4 +36,4 @@ Check the Action Center (Win+N). Windows Focus Assist or Do Not Disturb can rout  ## For the AI -The full contract (the `notify_user` verb, `focus` targets, `wait`, polling `notify_events`, sticky scenarios, progress updates) lives in the `adom-desktop-notify` skill, which installs automatically with the package and with the Windows app.+The full contract (the `notify_user` verb, `focus` targets, `wait`, polling `notify_events`, sticky scenarios, progress updates) lives in the `adom-bridge-notify` skill, which installs automatically with the package and with the Windows app.

@@ -24,7 +24,7 @@ Each bridge updates independently from its own wiki page. Adom Bridge polls ever  ## Lane 3: the container CLI and skills package -Cloud containers install `adom/adom-desktop` with `adom-wiki pkg update`, which fetches the package tarball (about 4 MB) only when the published version is newer. The CLI also runs a once-per-day background sync in containers that installs each connected bridge's own skill package, so a container's skills track whatever bridges the desktop actually has. If the container runs the relay under `serve --supervise`, the watchdog notices a newer CLI binary on disk (a local check, no network) and restarts the relay into it, so an updated CLI takes effect without anyone remembering to restart.+Cloud containers install `adom/adom-bridge` with `adom-wiki pkg update`, which fetches the package tarball (about 4 MB) only when the published version is newer. The CLI also runs a once-per-day background sync in containers that installs each connected bridge's own skill package, so a container's skills track whatever bridges the desktop actually has. If the container runs the relay under `serve --supervise`, the watchdog notices a newer CLI binary on disk (a local check, no network) and restarts the relay into it, so an updated CLI takes effect without anyone remembering to restart.  ## Lane 4: skills for local AIs