Pup - the AI's own browser

@@ -61,6 +61,13 @@ with a screenshot — the user must never look at a window running yesterday's c shared adom-you Chrome only truly relaunches when NO thread has live windows on it; when other threads hold it warm, say so instead of claiming the extensions updated. +**ALWAYS show the dashboard Settings after ANY settings change (standing rule from John, 2026-08-16):**+after fixing/changing anything in the Settings dialog (rows, examples, toggles, the taskbar-identity+matrix), open the pup dashboard, click the gear so the SETTINGS DIALOG is open and scrolled to the+changed section, and BRING IT TO THE FOREGROUND (his explicit standing request = the+foregroundReason). He wants to SEE the settings, not read that they changed. Reuse one window+(sessionId: cn-dash); close it when he's done with the review, never leave it stale.+ **ALWAYS show wiki changes in pup (standing rule from John):** after ANY publish/edit to this wiki page (release, repo push, pkg, page.json), refresh the LIVE page in a pup window the user can see (cache-bust with `?v=<ver>`), screenshot it, and surface the link — never just say "published."

@@ -43,6 +43,14 @@ Also run before/after risky work: `tools/churn-ralph.sh` (the #46 destructive-ki 5. **Jump list**: right-click menu must show the task rows, not bare Pin/Close. Automated proxy:    T6 log lines; the real gate is the menu itself. +## After any Settings change (standing rule, John 2026-08-16)++Open the dashboard, gear-click Settings open, scroll to the changed section, and FOREGROUND it+(`pup_raise_os_window` with foregroundReason citing this standing request). He reviews every+settings change visually — showing it is part of shipping it. Also assert at walk-end that the+box is restored to the default state (tiles + overlay): a walk that leaves plain mode behind is+a failed walk.+ ## Capture mechanics that keep biting  - Tray hwnd (`Shell_TrayWnd`) GOES STALE when Explorer restarts — re-resolve every session.