← Commit history

Publish 2.0.725

John Lauer ·49b12775af ·24d ago ·parent c931f9c
2 files changed +4−4
package.json+2−2
@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.724",+  "version": "2.0.725",   "type": "app",   "description": "The pup SKILL PACK: the AI skills that teach a cloud/container AI how to drive the Bridge Puppeteer (pup) bridge (pup_* 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 Bridge 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) \u2014 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 Bridge manages for you.",   "keywords": [@@ -148,5 +148,5 @@       "prompt": "Download the puppeteer-bridge zip from the wiki and walk me through server.js"     }   ],-  "changelog": "A pup window can no longer sit on the taskbar titled PUPBIRTH-... A new window starts on pup's birth page and is then sent to its address; when that step failed, the failure was swallowed and the window stayed on the birth page for good (John's laptop, 2026-10-17). The open now retries the navigate once, and the health check sends any window still on its birth page 20 s after birth to the address its session recorded (up to 3 tries). Includes 2.0.723."+  "changelog": "A pup window stuck on its birth page now gets sent to its address. Testing 2.0.724 on ConfRoomROG showed the gap behind John's PUPBIRTH window: when the navigate after birth answered but the tab never left the birth page, pup recorded the birth page as the window's address, so nothing could ever send it on. The birth page is now never recorded over a real address (live tab sync, tab refresh, both open paths, and re-adoption after a restart), the open logs it, and the health check sends the window on. Includes 2.0.724." }
page.json+2−2
@@ -4,7 +4,7 @@   "slug": "pup-bridge",   "title": "Pup - the AI's own browser",   "brief": "pup gives your AI a real browser on your desktop that it drives completely, in the background, signed in as you: windows that never jump in front of your work, one shared profile that learns your logins, and every window labeled on the taskbar with its AI thread's name.",-  "version": "2.0.724",+  "version": "2.0.725",   "tags": [     "skills",     "pup",@@ -168,5 +168,5 @@     "Kyle Bergstedt <[email protected]>",     "Colby Knox"   ],-  "changelog": "A pup window can no longer sit on the taskbar titled PUPBIRTH-... A new window starts on pup's birth page and is then sent to its address; when that step failed, the failure was swallowed and the window stayed on the birth page for good (John's laptop, 2026-10-17). The open now retries the navigate once, and the health check sends any window still on its birth page 20 s after birth to the address its session recorded (up to 3 tries). Includes 2.0.723."+  "changelog": "A pup window stuck on its birth page now gets sent to its address. Testing 2.0.724 on ConfRoomROG showed the gap behind John's PUPBIRTH window: when the navigate after birth answered but the tab never left the birth page, pup recorded the birth page as the window's address, so nothing could ever send it on. The birth page is now never recorded over a real address (live tab sync, tab refresh, both open paths, and re-adoption after a restart), the open logs it, and the health check sends the window on. Includes 2.0.724." }\ No newline at end of file