Pup - the AI's own browser

@@ -253,6 +253,44 @@ What we learned and baked into the code:   reading the third saw pre-update text. When auditing against a doc, verify the EXACT file you read; when   publishing multi-copy docs, push and verify every copy. +## Cross-repo issues — file an AD-core bug on adom/adom-desktop, NOT on your own page (John, 2026-07-24)++You depend MASSIVELY on AD-core (it spawns you, provisions your Node runtime, relays your verbs, installs+you), so you will hit AD bugs constantly during pup dev. This is common enough that getting the+DESTINATION right is its own discipline. The rule, verified with a live mistake:++**An issue lives on the issue list of the repo that OWNS the code that must change.**++- A pup bug (a `browser_*` verb, a hint, the CfT self-heal, the status chip) is YOURS: fix it here, or+  track it on the pup page (`adom/adom-desktop-puppeteer-bridge`).+- An AD-CORE gap (a lifecycle verb, spawn / provision / bind behavior, `preserve_client_deps`, the relay+  dropping a response field, the stdout capture, `bridge_log_read`, a manifest field AD must honor) goes+  on **`adom/adom-desktop`'s issue list**, NOT the pup page. The AD-core thread watches its OWN page and+  does NOT read pup's issues. An AD ask on the pup page is a note to yourself that nobody who can fix it+  will ever see.+- A wiki or CLI bug goes on `adom/wiki`. A sibling bridge bug goes on that bridge's page.++**The live mistake (2026-07-24):** three AD-core lifecycle asks (npm-install-on-lockfile-change,+stdout log rotation, `bridge_log_read` interleaving) were filed as pup issue #18 (a self-note), then+moved to `adom/adom-desktop#28`. The Bridge-SDK template ask went to `adom/adom-desktop#29`. Precedent+that adom/adom-desktop IS the right home for pup->AD asks: AD #26/#27 (CfT), #16 (window-verb+interception), #3/#20/#21 (Bridge SDK).++**How:**+```bash+adom-wiki issue list   adom/adom-desktop            # FIRST: skim for a dup, comment instead of re-filing+adom-wiki issue create adom/adom-desktop \+  --title "<verb or subsystem>: <the gap in one line>" \+  --category bug-report \+  --body "$(cat writeup.md)"                         # what you hit live + date + AD version + root cause + ask+# close/comment take the GLOBAL discussion id (the "id" field), NOT the per-page "number":+#   adom-wiki issue close <globalId> --comment "moved to adom/adom-desktop#N"+```+Separate what is AD-core's from what is yours IN the body, so the two are never conflated. After+filing, read the AD-core reply on that thread (it may change your plan, e.g. "fixed in AD X.Y, bump+your pin"): that issue is the cross-repo channel, keep the loop closed there. See the CLAUDE.md+"You vs adom-desktop (AD) core" boundary for capability-vs-policy calls.+ ## Background-by-default without stealing focus — THE SOLVED PLAYBOOK (do NOT re-derive this)  This is the single hardest problem in the bridge and it has been solved TWICE from scratch. If you are