Pup - the AI's own browser

@@ -13,8 +13,20 @@   Testing in 769 ms and had a background window with a resolved handle, parked at the bottom and   loaded, in 1,750 ms; pup_eval, pup_navigate, pup_screenshot (2012x1117 resized to 1568x871,   228 KB, a correct render) and pup_close_window (Chrome gone) all answered in the Node shapes.-  The Node build on the same box was untouched throughout. Not yet: identity stamping, tabs,-  input, recovery, dashboard page, everything in Phases 2 and 3.+  The Node build on the same box was untouched throughout.+- Phase 2 (2026-09-05, evening): 48 verbs native. Tabs, trusted input (click, type, press_key,+  hover, scroll, fill, wait), history, reload, viewport pin, dialogs, console errors (one event+  pump per browser), render_html, fetch_url, maximize; raise gated on a reason with caption + toast,+  lower, alert, taskbar progress; configure / use / quit_idle / rescan; session recovery after a+  bridge kill (measured: the window, its handle and its page came back and answered eval and+  screenshot), the 15 s health loop; taskbar identity through ab (thread tile rendered by the+  browser's own canvas from the embedded font, AUMID register + stamp, jump list, favicon overlay+  badge); the dashboard page embedded with its SSE snapshot, action and image routes, /api/status,+  /identity; the four MV3 extensions embedded and loaded on Chrome for Testing with pinned prefs.+  Measured on winvm, all through the hand-launched exe on a spare port. Not yet in Phase 2: fg-watch+  re-park, the 5-minute identity read-back audit (waits on adom-bridge#147), screenshot_element /+  full_res, download, the highFps lease. Phase 3 (vault, wiki, annotate, recording, Send-to-AI)+  not started.  Commissioned by John: "make a version of pup next that is a rust binary like we've recently done for fusion and for altium ... make sure that you did not reimplement anything in ab already does for you