Pup - the AI's own browser

@@ -4,6 +4,19 @@  ### Shipped skills asserted Windows-only facts the macOS port made false +**Second pass — my own first pass was incomplete, in the way this class always is.** After fixing+the Edge claim in `SKILL.md`'s BODY I left the identical claim in the same file's FRONTMATTER+`description`, 19 lines above. That is the worst place to leave it: the description is what the+skill loader surfaces and what an AI reads to decide whether pup is even relevant, so it outranks+the body it contradicted. Also scoped the README's AUMID/Alt-Tab/Win11-taskbar paragraph, which+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+— 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.+ Three places in the **shipped** pkg told the consumer AI something untrue on a Mac. None of them is a path, so no sweep this fleet built could see them — they are flat platform *assertions*, the class KICAD found in their README.

@@ -75,9 +75,11 @@ no gradients, no emoji):   window/tab counters instead. - The **tab title** carries the same login signal in text: a solid dot (`●   Logged in`) or hollow dot   (`○   Public`) leads the title of every Adom wiki tab.-- Under the hood, each window's identity (icon, name, Alt-Tab entry) rides a per-session Windows+- Under the hood **on Windows**, each window's identity (icon, name, Alt-Tab entry) rides a per-session   AppUserModelID that **carries the category**: the only way Win11 allows a taskbar tile to change-  live. Grouped mode instead keeps one stable, pinnable `Adom.Pup` identity.+  live. Grouped mode instead keeps one stable, pinnable `Adom.Pup` identity. **On macOS there is no+  AUMID and no taskbar** — window identity is whatever the launched browser bundle provides, the+  category signal is carried by the tab title above, and `taskbarGrouping` is stored but inert.  ### Using pup's icons in your own tool (HD browser picker, launchers, menus) 

@@ -1,7 +1,7 @@ --- name: pup user-invocable: true-description: "Drive a browser on the user's desktop from the cloud — the Puppeteer 'pup' bridge (browser_* verbs via the adom-desktop CLI). pup launches a FRESH, isolated process of the browser ALREADY on the machine (installed Chrome, else Microsoft Edge — every Windows PC has Edge), driven over CDP, in the BACKGROUND so it never disturbs the user; NOT the user's real signed-in profile (that's the Adom extension's nbrowser_* verbs), NOT headless (a real rendered window, so screenshots/recording are true-to-life). Chrome for Testing only as a last resort. Open/close windows + tabs, navigate, screenshot, eval JS, record. This is the START-HERE skill: the mental model + when-to-use + the skill map; deeper topics route to the sub-skills. For 'is it ready' use browser_readiness (not browser_status). Trigger words: pup, puppeteer, browser window, open in pup, open my app in pup, browser screenshot, browser eval, browser reload, visual debug, headful chrome, browser_open_window, browser_screenshot, browser_readiness, browser_prewarm, chrome for testing, open in browser."+description: "Drive a browser on the user's desktop from the cloud — the Puppeteer 'pup' bridge (browser_* verbs via the adom-desktop CLI). pup launches a FRESH, isolated process of the browser ALREADY on the machine (installed Chrome, else Microsoft Edge — on Windows every PC has Edge, on macOS neither is guaranteed so a download may be needed), driven over CDP, in the BACKGROUND so it never disturbs the user; NOT the user's real signed-in profile (that's the Adom extension's nbrowser_* verbs), NOT headless (a real rendered window, so screenshots/recording are true-to-life). Chrome for Testing only as a last resort. Open/close windows + tabs, navigate, screenshot, eval JS, record. This is the START-HERE skill: the mental model + when-to-use + the skill map; deeper topics route to the sub-skills. For 'is it ready' use browser_readiness (not browser_status). Trigger words: pup, puppeteer, browser window, open in pup, open my app in pup, browser screenshot, browser eval, browser reload, visual debug, headful chrome, browser_open_window, browser_screenshot, browser_readiness, browser_prewarm, chrome for testing, open in browser." ---  # Pup — browser control on the user's desktop (start here)