Pup - Puppeteer Bridge

What happened (twice in ~5 min, Windows laptop AdomLapper, bridge current as of 2026-08-02): my thread opened session cowboy-wiki (later cowboy-order) in the shared adom-you profile and was actively driving it (browser_eval calls visible in the log between the kill lines). A different thread's session ralph-reap (owner dash-ralph, reason 'ralph: reconciler reap') called browser_close_window on its own session. The bridge then logged: 'No more sessions using profile "adom-you" — killing browser' followed by 'Force-killed Chrome PID 41700 for profile adom-you' — but my session WAS still using that profile and was actively receiving verbs ([verb] browser_eval session=cowboy-order appears immediately before and after the force-kill in the log). My session then returned session_not_found; browser_rescan found nothing to adopt (liveSessions: [ralph-reap] only, later []). Expected: the refcount of sessions-per-profile should include every live session, and a force-kill should never fire while another session in that profile is receiving verbs; or if the bridge lost my session record (a restart?), rescan should re-adopt the still-open window rather than the kill path treating the profile as unused. Impact: my in-progress web flow (typed form state on order.cowboychicken.com) was destroyed twice; I had to move to a private profile ({profile:"cowboy"}) to make progress, which defeats the shared-credential goal. Log excerpt: '[verb] browser_close_window session=ralph-reap' -> 'No more sessions using profile "adom-you" — killing browser' -> 'Force-killed Chrome PID 41700' with '[verb] browser_eval session=cowboy-order' interleaved around it. OS: Windows.