← Commit history

v1.9.18: repaint the overlay after wiki auth state is recorded so the signed-in plate colour actually paints

John Lauer ·d27d88d6f1 ·3mo ago ·parent 3f9fdcf
5 files changed +21−7
CHANGELOG.md+9
@@ -1,5 +1,14 @@ # Changelog — Adom Desktop Puppeteer Bridge +## 1.9.18 — 2026-07-20 — Fix: the green plate never painted (overlay ran before auth was known)++The 1.9.16/1.9.17 plate colour was correct but never appeared. Ordering bug in browser_open_window:+applyAppOverlay paints the overlay EARLY, and `session._wikiAuthed` is only assigned a few lines+LATER from the auth probe - so the plate was always composited in the logged-out colour, even for a+window opened with wikiView:"authed". (The log tell: the per-session AUMID re-registers with+icon=auth AFTER the stamps, proving the state landed late.) Now the overlay is repainted once the+auth state is recorded.+ ## 1.9.17 — 2026-07-20 — Use the Adom brand green (#3fb950), not an ad-hoc one  John caught it: the signed-in green was #16a34a, which is Tailwind's green-600, not an Adom colour.
adom-bridge-puppeteer-manifest.json+5−5
@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.17",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.17/adom-bridge-puppeteer-v1.9.17.zip",-  "sha256": "0ffc811623de08e5c5597be4f1b647a8c5276741ec12c3cf55483b530cb5e894",-  "size": 236485,+  "version": "1.9.18",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.18/adom-bridge-puppeteer-v1.9.18.zip",+  "sha256": "a5e8553f6e7398eef66c7616fc7ac02796616d0d58562395116321c726be60bf",+  "size": 236631,   "verbPrefixes": [     "browser_",     "desktop_recorder_",@@ -12,5 +12,5 @@   ],   "healthEndpoint": "/status",   "statusVerb": "browser_readiness",-  "released_at": "2026-07-20T00:45:00Z"+  "released_at": "2026-07-20T01:00:00Z" }
src/BRIDGE_VERSION+1−1
@@ -1 +1 @@-1.9.17\ No newline at end of file+1.9.18\ No newline at end of file
src/bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.9.17",+  "version": "1.9.18",   "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. browser_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. browser_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.",   "homepage": "https://wiki.adom.inc/adom/adom-desktop",   "author": "Adom Inc.",
src/server.js+5
@@ -4646,6 +4646,11 @@ const server = http.createServer(async (req, res) => {             // v1.9.3: attach/clear the per-window wiki view-toggle jump list once the window's             // identity is stamped (registers the per-session AUMID if needed).             setTimeout(() => { updateWikiJumplist(session, sessionId).catch(() => {}); }, 900);+            // v1.9.18: REPAINT the overlay after session._wikiAuthed is set. The first+            // applyAppOverlay above runs BEFORE the wiki auth result is recorded a few lines+            // down, so it always composited the favicon on the logged-out (dark) plate even for+            // an authed window. This second pass paints the correct plate colour.+            setTimeout(() => { updateTabCountBadge(session, sessionId).catch(() => {}); }, 1200);           }           // Verbose browser report: which browser we actually drove, what else is available.           const brep = browserPickReport();