Pup - the AI's own browser

@@ -78,25 +78,6 @@ no gradients, no emoji):   AppUserModelID that **carries the category**: the only way Win11 allows a taskbar tile to change   live. Grouped mode instead keeps one stable, pinnable `Adom.Pup` identity. -## Recording and high-FPS windows--pup windows are backgrounded by design, and Chrome throttles a window that is occluded — so-recording one normally yields a **1-2 fps** video. pup can disable Chrome's power-saving to keep a-window painting at full rate, but a window in that mode can never idle down (three of them once-drained a laptop overnight, wiki issue #14).--So it is **opt-in and leased**:--- **Default** is Chrome's own power behaviour. Normal windows throttle when occluded and cost-  nothing in the background. Right for driving, scraping and screenshots.-- **`browser_open_window {highFps:true}`** renders at full rate while occluded, for background-  recording. It holds a lease (default 20 min), and **an active recording holds that lease open-  indefinitely, so a take is never cut off**. On lapse the window is *downgraded* back to normal-  power by relaunching with its tabs intact, never closed.-- **`browser_highfps_extend {sessionId, minutes}`** negotiates more time up front.--**Full details, defaults, activity signals, and rules of thumb: [RECORDING.md](RECORDING.md).**- ### Using pup's icons in your own tool (HD browser picker, launchers, menus)  If you are building a surface that offers "open a pup window" (a browser picker, a launcher tile, a@@ -203,6 +184,25 @@ cloud, with no HUD and no need to bring the window forward.  *Above: a GIF preview of a real `browser_record` capture (≈8.6 s, the tab navigating the Adom wiki, recorded in the background on a VM). The native capture is the WebM linked below — this GIF is just an inline preview.* +### High-FPS windows: recording something the user is not looking at++pup windows are backgrounded by design, and Chrome throttles a window that is occluded — so+recording one normally yields a **1-2 fps** video. pup can disable Chrome's power-saving to keep a+window painting at full rate, but a window in that mode can never idle down (three of them once+drained a laptop overnight, wiki issue #14).++So it is **opt-in and leased**:++- **Default** is Chrome's own power behaviour. Normal windows throttle when occluded and cost+  nothing in the background. Right for driving, scraping and screenshots.+- **`browser_open_window {highFps:true}`** renders at full rate while occluded, for background+  recording. It holds a lease (default 20 min), and **an active recording holds that lease open+  indefinitely, so a take is never cut off**. On lapse the window is *downgraded* back to normal+  power by relaunching with its tabs intact, never closed.+- **`browser_highfps_extend {sessionId, minutes}`** negotiates more time up front.++**Full details, defaults, activity signals, and rules of thumb: [RECORDING.md](RECORDING.md).**+ ### Two recorders — pick by what you're capturing  | Verb pair | Captures | How it works under the hood |