Pup - the AI's own browser

@@ -49,6 +49,11 @@ See `PUBLISHING.md` for the full recipe. Short form: edit `src/` → bump `src/B `adom-desktop bridge_install {"manifestUrl": ".../files/adom-bridge-puppeteer-manifest.json","force":true}` to test → verify in pup. Wiki = canonical. +**ALWAYS show wiki changes in pup (standing rule from John):** after ANY publish/edit to this wiki+page (release, repo push, pkg, page.json), refresh the LIVE page in a pup window the user can see+(cache-bust with `?v=<ver>`), screenshot it, and surface the link — never just say "published."+Reuse one window (`sessionId: cft` or `pup-wiki`) instead of spawning new ones; keep test windows open.+ ## Hard rules  - **The `.zip` is a RELEASE asset, never a git file.** `*.zip` is gitignored and `repo push --files X.zip`

@@ -211,3 +211,9 @@ bespoke `start_browser_bridge` npm-installs only the BUNDLED copy; the cache cop - The real fix is AD-side (give cache-installed node bridges their node_modules — `npm install` the cache   or reuse the bundled node_modules). Tracked in `HANDOFF-TO-ADOM-DESKTOP.md`. Once it ships, normal   wiki-streaming + `updateManifestUrl` auto-update works for pup like the other bridges.++## Final step of EVERY publish — show it in pup (standing rule)++After any release/repo-push/pkg-publish, refresh the LIVE wiki page in a pup window the user can+see (`browser_navigate` the existing session to `https://wiki.adom.inc/adom/adom-desktop-puppeteer-bridge?v=<ver>`,+cache-busted), screenshot it, and hand over the link. Never report "published" without showing it.