← Commit history

Publish 2.0.129

John Lauer ·a46ded9410 ·2mo ago ·parent b944b1d
4 files changed +15−8
install.sh+3−2
@@ -25,8 +25,9 @@ deploy_into() {   install_skill pup-screenshots-recording  skills/pup-screenshots-recording/SKILL.md   install_skill pup-browsers-and-chrome    skills/pup-browsers-and-chrome/SKILL.md   install_skill pup-adom-wiki              skills/pup-adom-wiki/SKILL.md-  install_skill pup-vendor-login          skills/pup-vendor-login/SKILL.md-  echo "  -> $BASE (pup + 4 sub-skills)"+  install_skill pup-vendor-login           skills/pup-vendor-login/SKILL.md+  install_skill pup-settings               skills/pup-settings/SKILL.md+  echo "  -> $BASE (pup + 5 sub-skills)" }  echo "Installing adom-desktop-puppeteer-bridge skills:"
package.json+3−2
@@ -1,8 +1,8 @@ {   "slug": "pup-bridge",-  "version": "2.0.18",+  "version": "2.0.129",   "type": "app",-  "description": "The pup SKILL PACK — 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 — 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.",+  "description": "The pup SKILL PACK — 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 — 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. The pkg version is kept in lockstep with the Release version so the page's max version row always carries BOTH a pkg tarball (skills) and a runtime zip (bridge) — a skills-only or runtime-only bump on the top row breaks constraint installs. TL;DR: pkg install = the skills for your AI; the bridge = the Release zip, which Adom Desktop manages for you.",   "keywords": [     "pup",     "puppeteer",@@ -28,6 +28,7 @@     "skills/pup-browsers-and-chrome/SKILL.md",     "skills/pup-adom-wiki/SKILL.md",     "skills/pup-vendor-login/SKILL.md",+    "skills/pup-settings/SKILL.md",     "install.sh",     "uninstall.sh",     "README.md",
page.json+3−2
@@ -4,7 +4,7 @@   "slug": "pup-bridge",   "title": "Pup - Puppeteer Bridge",   "brief": "pup is the AI's own browser: a real, full Chrome on the user's desktop that the AI fully controls (a sandbox, not the user's signed-in browser). Rides Bridge; pup_* verbs open windows and tabs, navigate, screenshot, and eval JS.",-  "version": "2.0.18",+  "version": "2.0.129",   "tags": [     "skills",     "pup",@@ -100,7 +100,7 @@   "created_at": "2026-05-28T05:28:43.991Z",   "skills": [],   "author_name": "John Lauer",-  "description": "The pup SKILL PACK — 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 — 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.",+  "description": "The pup SKILL PACK — 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 — 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. The pkg version is kept in lockstep with the Release version so the page's max version row always carries BOTH a pkg tarball (skills) and a runtime zip (bridge) — a skills-only or runtime-only bump on the top row breaks constraint installs. TL;DR: pkg install = the skills for your AI; the bridge = the Release zip, which Adom Desktop manages for you.",   "keywords": [     "pup",     "puppeteer",@@ -117,6 +117,7 @@     "skills/pup-browsers-and-chrome/SKILL.md",     "skills/pup-adom-wiki/SKILL.md",     "skills/pup-vendor-login/SKILL.md",+    "skills/pup-settings/SKILL.md",     "install.sh",     "uninstall.sh",     "README.md",
uninstall.sh+6−2
@@ -6,8 +6,12 @@ remove_from() {   local BASE="$1"   rm -rf "$BASE/pup" \          "$BASE/adom-desktop-puppeteer-bridge" \-         "$BASE/pup-windows-sessions-tabs" "$BASE/pup-screenshots-recording" "$BASE/pup-browsers-and-chrome" "$BASE/pup-adom-wiki" \-  rm -rf "$BASE/pup-vendor-login"+         "$BASE/pup-windows-sessions-tabs" \+         "$BASE/pup-screenshots-recording" \+         "$BASE/pup-browsers-and-chrome" \+         "$BASE/pup-adom-wiki" \+         "$BASE/pup-vendor-login" \+         "$BASE/pup-settings" \          "$BASE/pup-bridge-dev" "$BASE/pup-bridge-publish"   echo "  <- $BASE" }