Pup - the AI's own browser

@@ -65,3 +65,25 @@ The toolbar: four icons is the extension lane, three is CDP (John's own spec for fixing ext lane to solve all use cases." Trusted input, HTTP auth, fetch, screenshots and recording all run on the extension lane; a feature that genuinely needs CDP is an extension-lane gap to file on adom/pup-bridge, not a reason to open a CDP window. `isolated:true` and `profile:"<name>"` run on the extension lane too (2.0.659): each profile gets its own lane browser, its own staged extension and queue, so an isolated window is a separate browser with an empty jar, and a throwaway one ends with its last window.++## Windows keep their profile and their record across restarts (2.0.669 to 2.0.671)++Each profile has its own extension-lane browser (adom-you, plus one per explicit `profile`). On+2026-09-21 John saw taskbar tiles with no favicon badge on his laptop, and the cause was two bugs:++- **A window still on screen was forgotten.** After an upgrade the recovery pass counted each 15 s+  "still on screen, extension not answering yet" check as a failed relaunch and deleted the window's+  record on the third. The window stayed up with no owner, no badge, and its thread opened a duplicate.+  Since 2.0.669 a window on screen is never counted as a failure; its record is kept until it is re-adopted.+- **A browser was adopted into the wrong profile.** At boot pup restored only the adom-you lane, and the+  first unknown lane browser to say hello became adom-you, whatever folder it ran. adom-you windows then+  opened inside the "services" browser, with that profile's cookies. Since 2.0.670/671: every profile's lane+  is restored at boot and trusted only when its processes really run that profile's folder; the extension+  reports its profile in every hello, and an unknown browser is adopted only into that profile's lane, only+  after the boot restore; each window is re-adopted on its own profile's lane; and a window found inside+  another profile's browser is closed there and reopened in its own profile, at its page, in the background.++Proven on CRR with an adom-you window plus a second-profile window through an upgrade and a plain restart+(both kept, each in its own profile's browser, same windows), and on AdomLapper, where the three misplaced+adom-you windows were moved back into the adom-you browser automatically.+