← Commit history

Publish 2.0.565

John Lauer ·2045219815 ·1mo ago ·parent 6edca43
2 files changed +4−4
package.json+2−2
@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.564",+  "version": "2.0.565",   "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": "Same as 2.0.563 (extension lane is the default; CDP only on explicit lane:cdp; pup-lanes skill) plus: pup_dashboard opens like every other pup window, on the extension lane on adom-you, with no profile and nothing from CDP (John, 2026-09-14: why does pup_dashboard even need cdp). The Node-era pup-dashboard profile is retired. ab-smoke on 2.0.563 had caught the dashboard being refused by the new cdp_lane_required rule."+  "changelog": "pup_eval on the extension lane now returns exactly what the CDP lane returns: a string result stays a string even when its text is JSON (JSON.stringify(...) expressions came back as objects on this lane, which broke any caller written against the CDP contract, ab-smoke's dashboard check first). The worker tags the result type; the bridge reconstructs it. Carries 2.0.564 (extension lane default, CDP only on explicit lane:cdp, pup-lanes skill, dashboard on the extension lane)." }
page.json+2−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.564",+  "version": "2.0.565",   "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": "Same as 2.0.563 (extension lane is the default; CDP only on explicit lane:cdp; pup-lanes skill) plus: pup_dashboard opens like every other pup window, on the extension lane on adom-you, with no profile and nothing from CDP (John, 2026-09-14: why does pup_dashboard even need cdp). The Node-era pup-dashboard profile is retired. ab-smoke on 2.0.563 had caught the dashboard being refused by the new cdp_lane_required rule."+  "changelog": "pup_eval on the extension lane now returns exactly what the CDP lane returns: a string result stays a string even when its text is JSON (JSON.stringify(...) expressions came back as objects on this lane, which broke any caller written against the CDP contract, ab-smoke's dashboard check first). The worker tags the result type; the bridge reconstructs it. Carries 2.0.564 (extension lane default, CDP only on explicit lane:cdp, pup-lanes skill, dashboard on the extension lane)." }\ No newline at end of file