Pup - Puppeteer Bridge

Windows survive an upgrade AND the user's close is final. pup relaunches a missing window only when it knows the browser died for this pass (it ended it for an upgrade or restart, it crashed, or it was already dead at boot); any other missing window was closed and is forgotten. Closing a window during a relaunch queue cancels the queued relaunches of that thread (its taskbar icon). 2.0.681 dropped every window after the first on an upgrade; 2.0.680 and earlier reopened windows the user closed while pup restarted (John, AdomLapper, 2026-09-23). Promoted to public on 2026-09-23.

Windows survive an upgrade AND the user's close is final. pup relaunches a missing window only when it knows the browser died for this pass (it ended it for an upgrade or restart, it crashed, or it was already dead at boot); any other missing window was closed and is forgotten. Closing a window during a relaunch queue cancels the queued relaunches of that thread (its taskbar icon). 2.0.681 dropped every window after the first on an upgrade; 2.0.680 and earlier reopened windows the user closed while pup restarted (John, AdomLapper, 2026-09-23).

The user's close is final during a restore too: closing a window while an upgrade relaunches a thread's windows cancels every queued relaunch of that thread (the same taskbar icon), and each relaunch first picks up closes reported since the last one. Before, closing a thread's icon mid-queue brought its next window back 13-28 s later (John, AdomLapper, 2026-09-23). Plus 2.0.681: a window is restored only when its browser is gone.

A window is restored only when its browser is GONE (crash, sleep, upgrade). If the browser is alive and does not have the window, the window was CLOSED and pup forgets it. Before, any missing window read as a crash to repair, so windows the user closed while pup was restarting came back at the next boot (John, AdomLapper, 2026-09-23).

The cache prune never races a browser install: it refuses while one is in flight (the boot pass waits for it) and never touches a folder written in the last 5 minutes, so a first install unpacking into .partial cannot be deleted under it. Plus everything in 2.0.679.

pup accepts only plain-version folders as a usable browser build, so a half-unpacked .partial folder or a renamed copy is never launched (found while testing ab 2.1.153's prewarm of pup, which works end to end: ab calls pup_prewarm, pup downloads and unpacks the pinned build in the background, ab records ok). Plus everything in 2.0.678.

pup-bridge#126: bridge.json declares prewarm.verb pup_prewarm (timeout 900 s), so ab 2.1.153+ asks pup to fetch its browser in the background once per installed version instead of the first window paying for it. Plus everything in 2.0.677.

pup-bridge#125: pup prunes its browser download cache a minute after every boot and on demand (pup_cache_prune, with dryRun): superseded builds, the Node-era headless-shell builds and partial downloads go; the pinned build, the newest complete build when the pinned one is missing, and anything a running process or the default browser uses are kept. Plus everything in 2.0.676.

pup-bridge#124 (one verb surface, image fullPath/safePath, ok and output fields on every reply) plus two recovery fixes for multi-tab windows after an upgrade: a new extension-lane tab opens only in the window pup names (the extension refuses rather than guess; tabs had landed in another thread's window), and reopened tabs are de-duplicated by exact URL (stripping the query had dropped different pages on one path).

pup-bridge#124 (one verb surface, image fullPath/safePath, ok and output fields on every reply) plus: a new tab on the extension lane opens only in the window pup names (a live tab of it, or its Chrome window id); the extension refuses rather than guess. After an upgrade, recovery used to reopen a window's extra tabs into another thread's window (AdomLapper, 2026-09-22).

pup-bridge#124: one verb surface (bridge.json and pup_describe generated from the same 96 routed verbs; the build stops if one lacks a catalog entry; pup_describe carries verbCount and its notes). Every image reply carries ab's fullPath and safePath so ab auto-pulls the picture. pup now lifts its output fields onto every reply and always states ok true/false itself, because ab 2.1.14x stopped doing both: ok had vanished from error replies and pup_record_stop reported the call time as the recording's duration.

pup-bridge#124: one verb surface (bridge.json and pup_describe generated from the same 96 routed verbs; the build stops if one lacks a catalog entry; pup_describe carries verbCount and its notes). Every image reply carries ab's fullPath and safePath so ab auto-pulls the picture. And pup now lifts the fields of its output block onto every reply itself, because ab 2.1.14x stopped doing it: 'ok' had vanished from error replies and pup_record_stop reported the call time as the recording's duration.

pup-bridge#124: one verb surface. bridge.json's verb list and pup_describe are generated from the same list of routed verbs (96 each; they said 55 and 85), the build stops if a routed verb has no catalog entry, and pup_describe carries verbCount and its advisory notes separately. Every image reply (pup_screenshot and friends) now carries ab's fullPath and safePath, so ab's CLI auto-pulls the picture to the caller.

Every profile's lane survives a restart in its own jar: pup restores each profile's lane browser at boot (validated by the folder its processes run), adopts an unknown lane browser only into the profile it reports and only after that restore, re-adopts each window on its own profile's lane, and relaunches any window it finds inside another profile's browser. Before, the first unknown browser after an upgrade became the adom-you lane, so adom-you windows ran with another profile's cookies, and windows on a second profile were never re-adopted (AdomLapper and CRR, 2026-09-21). Promoted to public on 2026-09-21.

Every profile's lane survives a restart in its own jar: pup restores each profile's lane browser at boot (validated by the folder its processes run), adopts an unknown lane browser only into the profile it reports, and relaunches any window it finds inside another profile's browser. Before, after an upgrade the first unknown browser became the adom-you lane, so adom-you windows ran with another profile's cookies (AdomLapper, 2026-09-21).

Windows survive an upgrade: recovery no longer counts a window that is still on screen (waiting for the extension to reconnect) as a failed relaunch, so it never deletes a live window's record. Before, three quiet checks after a restart forgot the window, leaving it ownerless with no taskbar badge and making its thread open a duplicate. The identity audit also reads ab's nested reply now instead of reporting every window as unstamped.

No more taskbar-identity residue: a window's AUMID is unregistered when it closes; a sweep a minute after boot (and pup_sweep_identities on demand) unregisters every thread, per-window and category identity no live window holds, deletes dead shortcuts in pup's Start Menu folder and stale tile/icon generations. arav-rog had 116 dead keys and 20 dead shortcuts (John, 2026-09-20). Promoted to public on 2026-09-21.

No more taskbar-identity residue: a window's AUMID is unregistered when it closes; a sweep a minute after boot (and pup_sweep_identities on demand) unregisters every thread, per-window and category identity no live window holds, removes its Start Menu anchor and deletes stale tile/icon generations. arav-rog had 116 dead keys (John, 2026-09-20).

No more taskbar-identity residue: a window's AUMID is unregistered when it closes, a sweep a minute after boot (and pup_sweep_identities on demand) unregisters every thread/category identity no live window holds, removes its Start Menu anchor and deletes stale tile/icon generations. arav-rog had 116 dead keys.

No toast when a human raises a pup window: the jump list's relaunch command (pup_focus_window as user-taskbar-menu) used to warn the user about their own click. The foreground gate now judges by pup browser PID so a user's own Chrome can no longer fail it. Promoted to public on 2026-09-20.