Pup - the AI's own browser

@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.541",+  "version": "2.0.542",   "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": [@@ -147,5 +147,5 @@       "prompt": "Download the puppeteer-bridge zip from the wiki and walk me through server.js"     }   ],-  "changelog": "Apply the consumer brand rewrite at the session birth (2.0.540 hooked it into dress_window, which the session-based birth never calls, so it never ran). setBrands now reports whether Chrome accepted the declarativeNetRequest rule and how many dynamic rules are live, so a silently ignored header shows in the log instead of being guessed at."+  "changelog": "A lane browser that outlives a pup update no longer runs the old extension unnoticed. The hello now carries the worker's versioned filename; pup_status.extensionLane reports workerVersion and stale, with a hint; and the health tick cycles a stale lane the moment no extension-lane window is open, so the next open stages the current extension (measured: worker.2-0-539 kept serving under pup 2.0.541, and the brand rewrite shipped in .540 never ran until the lane was cycled by hand). Also pup_clear_site_data {origin|origins}: cache, cookies, storage and service workers for an origin, through chrome.browsingData on the lane and Storage.clearDataForOrigin over CDP." }

@@ -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.541",+  "version": "2.0.542",   "tags": [     "skills",     "pup",@@ -167,5 +167,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": "Apply the consumer brand rewrite at the session birth (2.0.540 hooked it into dress_window, which the session-based birth never calls, so it never ran). setBrands now reports whether Chrome accepted the declarativeNetRequest rule and how many dynamic rules are live, so a silently ignored header shows in the log instead of being guessed at."+  "changelog": "A lane browser that outlives a pup update no longer runs the old extension unnoticed. The hello now carries the worker's versioned filename; pup_status.extensionLane reports workerVersion and stale, with a hint; and the health tick cycles a stale lane the moment no extension-lane window is open, so the next open stages the current extension (measured: worker.2-0-539 kept serving under pup 2.0.541, and the brand rewrite shipped in .540 never ran until the lane was cycled by hand). Also pup_clear_site_data {origin|origins}: cache, cookies, storage and service workers for an origin, through chrome.browsingData on the lane and Storage.clearDataForOrigin over CDP." }\ No newline at end of file