Cupertino 1.19.1

Fixed

• apple_safari_read_page returned a single-page app's pre-boot shell, forever. The extension captured a page once, at document_idle, and again only after a route change — before a single-page app has rendered anything. The only capture of x.com was therefore its loading shell: an empty <title> and the static "Something went wrong … privacy related extensions" block X ships in every response, easy to misread as a real error rather than an uninitialized page. The store is keyed by URL, so that snapshot was the permanent answer for the page; no amount of waiting before read_page improved it, because nothing ever captured a second time.

  The content script now re-captures once the page settles: a MutationObserver fires after the DOM holds still for 500ms, with a 5-second deadline for pages that never go fully quiet — a live timeline (video, ads, ticking timestamps) would otherwise never trigger a debounce on its own. A route change reuses the same watcher instead of a fixed delay, and a settled capture identical to the one already sent is skipped rather than resent.