← Commit history

README + pkg description: lead with a crisp 'Install (skills) vs Download (runtime)' explainer incl. why the two version numbers differ; refresh the stale pkg description to the current model. pkg 1.8.28

John Lauer ·1ad66744d1 · ·parent 9ead250
2 files changed +16−9
README.md+14−7
@@ -12,15 +12,22 @@ Chromium browser at all. Windows open in the **background by default** so pup ne  Canonical page: **https://wiki.adom.inc/adom/adom-desktop-puppeteer-bridge** -## Three artifacts — know which is which+## Install vs Download — which is which (and why the version numbers differ) -| Artifact | Where | What it is |-|---|---|---|-| **pkg** (Packages tab) | `adom-wiki pkg install adom/adom-desktop-puppeteer-bridge` | the **container-side `pup` skill** (drops into `~/.claude/skills` + `~/.codex/skills`). No runtime. |-| **release zip** (Releases tab) | `https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/<ver>/adom-bridge-puppeteer-v<ver>.zip` | the **bridge runtime** (Node + the installed-browser detection / Chrome-for-Testing last-resort self-heal) that Adom Desktop streams into its bridges-cache |-| **bundled seed** | inside the Adom Desktop installer | the same runtime, shipped for first-run/offline; superseded by a newer cache copy via `updateManifestUrl` |+The page header shows **two** things, for two different places. Most people need only the first. -**TL;DR:** `pkg install` = the pup skill for the container; the bridge itself = the Release zip + bundled in Adom Desktop.+| On the page | What it is | Who runs it | You usually… |+|---|---|---|---|+| **Install** — `adom-wiki pkg install …` | The **AI skill pack** — the `pup` skills that teach a cloud/container AI how to drive the bridge. Docs only, no runtime; drops into `~/.claude/skills` + `~/.codex/skills`. | your **container / cloud AI** | **run this** (or it arrives via `sync_skills`) |+| **Download for your machine** — `adom-bridge-puppeteer-v<ver>.zip` | The **bridge runtime** — the actual Node program (browser detection + driving) that runs on the desktop. | **Adom Desktop**, on the user's PC | **do nothing** — Adom Desktop **auto-installs & auto-updates** it; the manual download is only for offline/manual installs |++**Why two different version numbers?** They're independent artifacts. The **Install (pkg)** version bumps+whenever the *skills/docs* change (often). The **Download (runtime)** version bumps only when the *bridge+code* changes (rarely). So it's normal to see e.g. Install `v1.8.27` and Download `v1.8.20` — nothing is+out of sync; they just version on their own clocks.++*(There's also a third copy — the runtime is **bundled inside the Adom Desktop installer** as a first-run+seed, superseded by a newer cache copy via `updateManifestUrl`. You never touch it directly.)*  ## Use it 
package.json+2−2
@@ -1,8 +1,8 @@ {   "slug": "adom-desktop-puppeteer-bridge",-  "version": "1.8.27",+  "version": "1.8.28",   "type": "app",-  "description": "CONTAINER-SIDE install \u2014 the pup skill pack in the wiki skillpack layout: the everyday `pup` user skill PLUS two bundled developer sub-skills (pup-bridge-dev, pup-bridge-publish; user-invocable:false, DEVELOPER-only descriptions so they never trigger for everyday users), all dropped into ~/.claude/skills/ AND ~/.codex/skills/ by an explicit install.sh list. It does NOT contain the bridge runtime: the bridge (Node + browser driving) lives on the DESKTOP \u2014 bundled inside Adom Desktop and published on the Releases tab as adom-bridge-puppeteer-v<ver>.zip, which Adom Desktop streams into its bridges-cache. TL;DR: pkg install = the skill pack; the bridge = the Release zip + bundled in Adom Desktop.",+  "description": "The pup SKILL PACK \u2014 the AI skills that teach a cloud/container AI how to drive the Adom Desktop Puppeteer (pup) bridge (browser_* verbs): the everyday `pup` skill plus focused sub-skills for windows/sessions/tabs, screenshots+recording, browsers+Chrome install, and driving the Adom wiki. Installs into ~/.claude/skills + ~/.codex/skills. DOCS ONLY \u2014 this is NOT the bridge runtime. The bridge itself (the Node program that drives the browser) runs on the DESKTOP: Adom Desktop bundles it and auto-installs/updates it, and it's published separately on the Releases tab as adom-bridge-puppeteer-v<ver>.zip. So the pkg version (skills, bumps often) and the Release version (runtime, bumps rarely) differ on purpose. TL;DR: pkg install = the skills for your AI; the bridge = the Release zip, which Adom Desktop manages for you.",   "keywords": [     "pup",     "puppeteer",