Pup - the AI's own browser

@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.566",+  "version": "2.0.567",   "type": "app",   "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. 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 Desktop manages for you.",   "keywords": [@@ -148,5 +148,5 @@       "prompt": "Download the puppeteer-bridge zip from the wiki and walk me through server.js"     }   ],-  "changelog": "Extension-lane channel survives a service-worker restart. An MV3 worker can be torn down between taking a command and answering it (measured 2026-09-14: a second hello 31 s after the first, mid-command); the reply never came and the bridge waited out the full timeout, which on a cold open pushed pup_open_window past ab's 60 s and the AI saw a timeout while the window opened anyway. The bridge now remembers the command it handed out and re-issues it when a fresh hello arrives from the lane. Cold-open budgets also fit inside 60 s now (brands 6 s, tabs 10 s, birth navigate 30 s, badge eval 25 s). Carries 2.0.565 (ext eval matches the CDP result contract) and 2.0.564 (extension lane default, CDP opt-in, pup-lanes skill, dashboard on ext)."+  "changelog": "Extension-lane windows are branded BEFORE Chrome shows them, with the same birth watcher the CDP lane has had since 2.0.446 (now one function shared by both opens): the AUMID is registered ahead of time, a thread polls every top-level frame every millisecond from before the window exists, and the newborn is stamped natively while still invisible so the shell bakes pup's icon into the button at its first show. Until now the ext lane stamped only after the page had navigated, so every ext window was born on the stock Chrome icon (John, 2026-09-14, opening the all-engineering agenda). The ext lane's own 6 s bind loop is deleted; the watcher's hwnd is the window." }

@@ -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.566",+  "version": "2.0.567",   "tags": [     "skills",     "pup",@@ -168,5 +168,5 @@       "pup-bridge verbs are invoked through the adom-bridge CLI, not through a binary this package installs, so prefix rules cannot reach them."     ]   },-  "changelog": "Extension-lane channel survives a service-worker restart. An MV3 worker can be torn down between taking a command and answering it (measured 2026-09-14: a second hello 31 s after the first, mid-command); the reply never came and the bridge waited out the full timeout, which on a cold open pushed pup_open_window past ab's 60 s and the AI saw a timeout while the window opened anyway. The bridge now remembers the command it handed out and re-issues it when a fresh hello arrives from the lane. Cold-open budgets also fit inside 60 s now (brands 6 s, tabs 10 s, birth navigate 30 s, badge eval 25 s). Carries 2.0.565 (ext eval matches the CDP result contract) and 2.0.564 (extension lane default, CDP opt-in, pup-lanes skill, dashboard on ext)."+  "changelog": "Extension-lane windows are branded BEFORE Chrome shows them, with the same birth watcher the CDP lane has had since 2.0.446 (now one function shared by both opens): the AUMID is registered ahead of time, a thread polls every top-level frame every millisecond from before the window exists, and the newborn is stamped natively while still invisible so the shell bakes pup's icon into the button at its first show. Until now the ext lane stamped only after the page had navigated, so every ext window was born on the stock Chrome icon (John, 2026-09-14, opening the all-engineering agenda). The ext lane's own 6 s bind loop is deleted; the watcher's hwnd is the window." }\ No newline at end of file