Pup - the AI's own browser

@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.620",+  "version": "2.0.621",   "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": "A navigation no longer leaves a pup window on top of the user's work. Measured: a navigate makes the pup window ACTIVE, and Windows refuses to lower whatever is active, so every lower reported success while the window stayed in front. The order is forced: return the screen to the window the user was in, which makes the pup window ordinary again, and only then lower it. Either half alone does nothing."+  "changelog": "The extension lane follows placement rule R1 at last: every window is born off-screen at -32000,-32000 and moved on-screen within 50 ms, unconditionally, the way the CDP lane has since v2.0.276. Gone with it, per the doctrine: the hide-until-ready watcher (a strandable staging state), every focus handback (deleted in August for foregrounding the wrong window), the minimized birth, and the post-navigate attention clear, whose Bridge implementation raises the window (adom-bridge#199) and was the navigate-puts-it-on-top bug. tools/foreground-proof.sh is the gate: a pinned window, a cold lane, opens and navigates, zero samples with a pup window on top." }

@@ -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.620",+  "version": "2.0.621",   "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": "A navigation no longer leaves a pup window on top of the user's work. Measured: a navigate makes the pup window ACTIVE, and Windows refuses to lower whatever is active, so every lower reported success while the window stayed in front. The order is forced: return the screen to the window the user was in, which makes the pup window ordinary again, and only then lower it. Either half alone does nothing."+  "changelog": "The extension lane follows placement rule R1 at last: every window is born off-screen at -32000,-32000 and moved on-screen within 50 ms, unconditionally, the way the CDP lane has since v2.0.276. Gone with it, per the doctrine: the hide-until-ready watcher (a strandable staging state), every focus handback (deleted in August for foregrounding the wrong window), the minimized birth, and the post-navigate attention clear, whose Bridge implementation raises the window (adom-bridge#199) and was the navigate-puts-it-on-top bug. tools/foreground-proof.sh is the gate: a pinned window, a cold lane, opens and navigates, zero samples with a pup window on top." }\ No newline at end of file