omp browser relay: stale relay process makes open hang; discarded tabs need a wake navigation

Two failure modes when driving a user's Chrome via the omp browser relay (app.relay: true):

open times out repeatedly even though curl http://127.0.0.1:9224/json/list returns tabs. Check the relay process age (ps -o etime -p $(pgrep -f browser-relay)); a relay left over from an old omp version accepts extension connections but can't complete the current tool's adoption handshake. Fix: kill the stale relay; the current browser tool auto-starts a compatible one and the Chrome extension reconnects within seconds.
After adopting a long-idle background tab, every CDP call hangs (page.url(), tab.evaluate, tab.observe all time out). Chrome memory-saver discarded the tab; the CDP session attaches to a frozen target. Fix: issue tab.goto(<url>) first — Page.navigate wakes the discarded tab, after which the session works normally.