Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.173",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.173/adom-bridge-puppeteer-v2.0.173.zip",-  "sha256": "5999ed4413d0f1ecb35d217f76ab041dc37dbe22ea3e7cb34a736f21be498653",-  "size": 916478,+  "version": "2.0.174",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.174/adom-bridge-puppeteer-v2.0.174.zip",+  "sha256": "32e3fb8e345ab50729812894991b14ce934e4b6b1262d5d3b595d2c38437ec04",+  "size": 916568,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-2.0.173+2.0.174

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "2.0.173",+  "version": "2.0.174",   "description": "Drives a browser ALREADY on the machine \u2014 installed Chrome, else Microsoft Edge (every Windows PC ships with Edge) \u2014 launched with a FRESH isolated profile, so the common case has NO ~150 MB Chrome-for-Testing download and it never touches the user's real tabs/logins. Binds its local server to LOOPBACK (127.0.0.1) only, so no Windows Firewall 'allow Node through the firewall' prompt ever pops. Chrome for Testing is fetched only as a LAST RESORT if the machine has no Chromium browser at all. SPAWN-VERIFIED fallback: pup tries each detected browser (Chrome \u2192 Edge \u2192 CfT) and actually launches it, falling through to the next if one won't start (and handling browsers like Edge that relaunch onto another PID), so a corrupt/partial install never hard-fails an open. The browser that launches is cached as the default (persisted across restarts) so it isn't re-probed each time. On spawn the bridge SELF-WARMS: detects browsers + disk, and only if the box has no Chrome/Edge and no cached CfT does it background-fetch CfT so the first open is instant. pup_use pins a specific browser (chrome | edge | cft | auto); {browser:'chrome',install:true} downloads & installs REAL Google Chrome (user-scoped, no admin) on an Edge-only box. pup_readiness (READ-ONLY) reports which browser will be used + the full candidate list + the default + free disk. Every failure returns a specific errorCode + _hint (chrome_install_no_disk, chrome_download_network, chrome_install_permission, chrome_stable_not_detected, \u2026). Launches with FULL browser permissions by default for full debug (strictPermissions:true opts out). Headful automation: open/close windows+tabs, navigate, screenshot, eval JS, record. pup is a GENERIC, non-profile browser only \u2014 every session is a fresh isolated Chrome/Edge process, never the user's real signed-in browser; profile defaults to sessionId. To drive the user's REAL Chrome/Edge (their profile, cookies, SSO), use the Adom browser EXTENSION's nbrowser_* verbs \u2014 a separate bridge, not pup's job. macOS (v1.9.74+): full parity with mac-native mechanics \u2014 background-by-default is the app-level hide (windows stay drivable/screenshottable while hidden), raise/lower map to unhide+activate/hide, pup_alert_window posts a native toast whose click focuses the window, pup_use {browser:'chrome',install:true} installs Chrome from the official dmg, and taskbar identity/badging remains Windows-only.",   "homepage": "https://wiki.adom.inc/adom/adom-bridge",   "author": "Adom Inc.",

@@ -3481,9 +3481,12 @@ function pupSettings() {               aumidIconStyle: 'category', taskbarGrouping: 'split',               // v2.0.152 THREAD TILES (John): group every pup window/tab of one ai-thread under ONE               // taskbar button whose icon is that thread's NAME rendered on the teal tile (Familjen-              // Grotesk, auto-fit). Off by default; when on it overrides the grouping so a thread's+              // Grotesk, auto-fit + truncate). It overrides the grouping/style modes so a thread's               // whole pup estate lives under a single named tile ("oh, that's my shotlog thread").-              threadTiles: 'off' };+              // v2.0.174 (John: "put thread tiles at top of settings since its the DEFAULT and my+              // favorite"): now ON by default, and the first row in the Settings dialog. _chosen+              // tracking means this only moves users who never set the key themselves.+              threadTiles: 'on' };   D.openFlash = 'on';   // v1.9.262 (John: "why did you default it to off when its defaulted to on")   if (_pupSettings.openFlash === 'off' && !_pupSettings._openFlashChosen) _pupSettings.openFlash = 'on';   // v1.9.268 (John on autoFlash: "this should be on by default")@@ -11457,10 +11460,10 @@ let SEENTOAST=0; // v1.9.259: the settings dialog. Rows defined once; state comes from SNAP.bridge.settings; every // change POSTs set-setting and answers back with a toast. const SETTINGS_DEF=[+ {k:'threadTiles',l:'Thread Tiles',info:'Every AI thread you work in (the --ai-thread name: "kicad", "ah build", "shotlog") gets ONE taskbar button, and the icon for that button is the thread NAME itself, drawn in the Adom font on the Adom teal tile. All windows and tabs that thread owns collapse onto it, so a glance at the taskbar tells you which of your threads have windows open and where each one is. The name is rendered bottom-left so the little favicon badge in the top-right corner (which shows what the active tab is) covers as little of it as possible. Short names print big; longer ones wrap to two lines. Takes precedence over AUMID grouping and icon style; windows with no owning thread fall back to those normal modes.',d:'Group every window of one AI thread under ONE taskbar button whose icon is the thread NAME on the Adom teal tile. Examples below are live-rendered by the same code that draws the real icons.',dep:'aumidIcons',threadex:1},  {k:'aumidIcons',l:'AUMID taskbar icons',info:'AUMID = Application User Model ID, a feature built into Windows itself. Every taskbar button is really a GROUP: Windows collects windows that share the same ID onto one button. Normally all windows of one app share the app ID, which is why 5 Chrome windows stack under one Chrome button. But the ID can be set PER WINDOW: pup writes a unique ID onto each pup window using the Windows property system (the same mechanism apps like Office use), and Windows then gives that window its own taskbar button with its own icon. The catch, and why this is an experiment: whenever a window ID changes, Windows destroys and recreates its taskbar button, and that churn is a suspect in the Chrome crashes. pup stamps each window exactly once, at creation, to minimize it.',d:'EXPERIMENT: give every pup window its OWN taskbar icon by stamping a per-window identity. Toggle on/off to test whether AUMID stamping is what crashes Chrome. Off = all windows share one Chrome button (current mode). Already-stamped windows keep their icon until closed.',img:'aumid'},  {k:'taskbarGrouping',l:'AUMID grouping',d:'Only applies when AUMID icons are on. split = one taskbar button per window. grouped = windows grouped BY CATEGORY when icon-style is "category" (up to 5 buttons: signed-in wiki, public wiki, open web, Adom app, plain — e.g. all your signed-in-wiki windows collapse under the one padlock button); with icon-style "standard" grouped collapses everything under a single Adom Pup button.',sel:['split','grouped'],dep:'aumidIcons',imgBy:{split:'groupsplit',grouped:'groupgrouped'}},  {k:'aumidIconStyle',l:'AUMID icon style',d:'Only applies when AUMID icons are on: standard = one pup tile for every window; category = the custom set (wiki signed-out, wiki signed-in padlock, world icon for the open web, adom app icon, mixed).',sel:['standard','category'],dep:'aumidIcons',imgBy:{standard:'iconstylestd',category:'iconstylecat'}},- {k:'threadTiles',l:'Thread Tiles',info:'Every AI thread you work in (the --ai-thread name: "kicad", "ah build", "shotlog") gets ONE taskbar button, and the icon for that button is the thread NAME itself, drawn in the Adom font on the Adom teal tile. All windows and tabs that thread owns collapse onto it, so a glance at the taskbar tells you which of your threads have windows open and where each one is. The name is rendered bottom-left so the little favicon badge in the top-right corner (which shows what the active tab is) covers as little of it as possible. Short names print big; longer ones wrap to two lines. Takes precedence over AUMID grouping and icon style; windows with no owning thread fall back to those normal modes.',d:'Group every window of one AI thread under ONE taskbar button whose icon is the thread NAME on the Adom teal tile. Examples below are live-rendered by the same code that draws the real icons.',dep:'aumidIcons',threadex:1},  {k:'jumpLists',l:'Jump lists',d:'The menu Windows shows when you right-click a pup taskbar icon (real screenshot below, captured on this machine). Requires AUMID icons on. Off by default. Quirk: the FIRST right-click can blip the menu closed — right-click again ~1s later and it holds (a Windows shell timing race, not a pup bug).',img:'jumplist'},  {k:'jlViewTasks',l:'',d:'Wiki view tasks: Switch to logged-in view / Switch to public view on every wiki window.',dep:'jumpLists',subtgl:1,img:'jlviewtasks'},  {k:'jlCloseAll',l:'',d:'The Close all pup windows task on every pup icon.',dep:'jumpLists',subtgl:1,img:'jlcloseall'},