Pup - the AI's own browser

@@ -349,8 +349,9 @@ sequential load, not as a solved site, and do not quote a clean score you have n Nothing here needed nb. Conditions that matter:  1. **Drive the site through pup, not a hand-rolled Chrome.** Re-measured 2026-09-14 with screenshots:-   analog.com rendered fully in pup on CfT 152 on the warm adom-you profile AND on a brand-new isolated-   jar, so neither the cookie jar nor accumulated profile state is what gets you in. An earlier version+   analog.com rendered fully in pup on CfT 152 on the adom-you profile. A second arm meant to be a+   fresh jar was NOT one: `isolated:true` does not create a separate profile (pup-bridge#112), so that+   run used adom-you twice. Whether profile state matters is UNTESTED, not ruled out. An earlier version    of this skill claimed the CfT 148 to 152 bump was the fix. That claim came from comparing pup against    raw `shell_execute` Chrome launches that lacked pup's flag set (no `--disable-infobars`, different    feature disables, no identity shim), which is not a valid comparison. What makes these sites load is

@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.554",+  "version": "2.0.555",   "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": "Skills updated with what today actually established, replacing what it only appeared to. (1) The 20-of-20 vendor-site score is corrected to 19 of 20: analog.com was denied as the 7th of 20 sequential loads having rendered fine on a single visit minutes earlier, and the clean run did not reproduce. analog.com is documented as intermittent under sequential load rather than solved. (2) New measurement-hygiene section in pup-browser-detection covering the five mistakes that produced four wrong causal stories in one day: comparing pup against a hand-rolled Chrome launch, reading window titles instead of screenshots, poisoning your own egress reputation by repeated probing, promoting a single passing run to documentation, and leaving orphaned Chrome processes holding profiles. Carries forward 2.0.553's ack_external fix for the external-extension Action required bubble, pup_close_all_windows, and the em-dash sweep."+  "changelog": "Corrects a claim 2.0.552 through 2.0.554 shipped, and labels an unproven fix honestly. (1) WITHDRAWN: the statement that neither profile state nor cookie history is the discriminator for Akamai vendor sites. That rested on a warm-versus-fresh profile comparison, but isolated:true does not create a separate profile (it forces the CDP lane and the anonymous tile while the jar stays adom-you, filed as pup-bridge#112), so the comparison ran adom-you twice. Profile state is now documented as UNTESTED rather than excluded, across the root skill, pup-why-cft and pup-bot-walls. (2) The ack_external seeding added in 2.0.553 for the external-extension Action required bubble is retained but is UNVERIFIED: repeated readings of the same profile disagreed and extensions.settings read back empty, so there is no evidence it suppresses the dialog. Do not describe the bubble as fixed. (3) Carries forward 2.0.554's corrected 19-of-20 vendor-site score with analog.com intermittent, the measurement-hygiene section, pup_close_all_windows, and the em-dash sweep." }

@@ -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.554",+  "version": "2.0.555",   "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": "Skills updated with what today actually established, replacing what it only appeared to. (1) The 20-of-20 vendor-site score is corrected to 19 of 20: analog.com was denied as the 7th of 20 sequential loads having rendered fine on a single visit minutes earlier, and the clean run did not reproduce. analog.com is documented as intermittent under sequential load rather than solved. (2) New measurement-hygiene section in pup-browser-detection covering the five mistakes that produced four wrong causal stories in one day: comparing pup against a hand-rolled Chrome launch, reading window titles instead of screenshots, poisoning your own egress reputation by repeated probing, promoting a single passing run to documentation, and leaving orphaned Chrome processes holding profiles. Carries forward 2.0.553's ack_external fix for the external-extension Action required bubble, pup_close_all_windows, and the em-dash sweep."+  "changelog": "Corrects a claim 2.0.552 through 2.0.554 shipped, and labels an unproven fix honestly. (1) WITHDRAWN: the statement that neither profile state nor cookie history is the discriminator for Akamai vendor sites. That rested on a warm-versus-fresh profile comparison, but isolated:true does not create a separate profile (it forces the CDP lane and the anonymous tile while the jar stays adom-you, filed as pup-bridge#112), so the comparison ran adom-you twice. Profile state is now documented as UNTESTED rather than excluded, across the root skill, pup-why-cft and pup-bot-walls. (2) The ack_external seeding added in 2.0.553 for the external-extension Action required bubble is retained but is UNVERIFIED: repeated readings of the same profile disagreed and extensions.settings read back empty, so there is no evidence it suppresses the dialog. Do not describe the bubble as fixed. (3) Carries forward 2.0.554's corrected 19-of-20 vendor-site score with analog.com intermittent, the measurement-hygiene section, pup_close_all_windows, and the em-dash sweep." }\ No newline at end of file

@@ -52,8 +52,9 @@ CfT 152. `shell_execute` Chrome launches carrying a hand-copied flag list; the CfT 152 result came from pup itself. Those two differ in far more than the build number (pup passes `--disable-infobars`, a different feature-disable set and the identity shim; the raw launches visibly showed the automation-infobar). Re-measured with screenshots on 2026-09-14, analog.com rendered fine in pup on CfT 152 on-BOTH the warm adom-you profile and a brand-new isolated jar.+infobar). Re-measured with screenshots on 2026-09-14, analog.com rendered fine in pup on CfT 152 on the+adom-you profile. The intended fresh-jar arm was not fresh: `isolated:true` keeps the adom-you+profile (pup-bridge#112), so profile state remains UNTESTED.  **What is actually established:** sites in this class load when driven through pup's own launch path. Which element of that launch is decisive has NOT been isolated, and it has NOT been shown to be the