Pup - the AI's own browser

@@ -106,7 +106,7 @@ the body it contradicted. Also scoped the README's AUMID/Alt-Tab/Win11-taskbar p presented Windows window-identity as "under the hood" universal; macOS has no AUMID and no taskbar, so it now says what carries the signal there instead. -Found by redoing the sweep HD's way — enumerate every line mentioning the platform and READ them+Found by redoing the sweep Hydrogen's way — enumerate every line mentioning the platform and READ them — instead of my first method, a grep with an exclusion filter. The filter excluded lines containing "window", and pup is a browser-WINDOW bridge, so it had been hiding most of the file from me. A clean result in this class is easy to fake.@@ -241,9 +241,9 @@ zips built from the repo silently dropped them).   1. VERIFIED AD BASE. KICAD's env-injection finding (confirmed from hd-control source):-   an HD-spawned bridge gets ADOM_DIRECT_API_URL pointed at HD's control API (:47084),+   an HD-spawned bridge gets ADOM_DIRECT_API_URL pointed at Hydrogen's control API (:47084),    which serves no notify verbs — so pup's alert toast would silently post to the wrong-   API under HD hosting. adCommand now resolves a VERIFIED base: probe each candidate's+   API under Hydrogen hosting. adCommand now resolves a VERIFIED base: probe each candidate's    GET /commands for the verb surface pup needs (notify_user), in trust order env →    ~/.adom/direct-api-port → default :47200, and use the first that answers. Live-tested:    with a bogus env pointing at a dead port, ping still reaches the real AD via the port@@ -909,7 +909,7 @@ so the user can verify publish visibility ("did private source leak to the publi ## 1.8.92 — 2026-07-19 — App-favicon overlay: a pup window WEARS the app that drives it  John's standard: every Adom app already serves a favicon (<link rel="icon">, monochrome white-mark per adom-ui-design; the canonical webview identity per hd-tab-icons) — so pup now+mark per adom-ui-design; the canonical webview identity per hydrogen-tab-icons) — so pup now auto-fetches the loaded page's favicon and wears it in the taskbar overlay, composited onto a dark rounded plate (white marks need dark backing). "That pup window with the shotlog icon IS my shotlog thread." Explicit overrides: browser_open_window {appIconB64, appName}. An app-looking@@ -1471,7 +1471,7 @@ Consolidated summary of the arc since 1.1.0 (per-release detail lives in the wik  ## 1.1.0 — 2026-06-29 — Cold-start self-heal + ownership extraction -**Why:** On a fresh PC (Hydrogen Desktop bundles Adom Desktop; the installer pre-installs neither+**Why:** On a fresh PC (Adom Hydrogen bundles Adom Desktop; the installer pre-installs neither Node nor Chrome for Testing), the first "open … in pup" failed with a generic "Failed to launch Chrome after 3 attempts" + a developer-only string ("run npx puppeteer browsers install chrome") — no `errorCode`, no auto-install, no actionable hint. The AI couldn't recover.