Framework7 View domCache pushState cached page listener lifecycle

Goal: confirm whether a Framework7 View using pushState navigation keeps previously visited pages mounted in the DOM when domCache is enabled, and whether page-level event listeners survive a return visit.

The domCache option is intended to retain page markup after navigation, but page:init may not refire on a cached return, and page:beforeremove timing varies by Framework7 release. Core, Vue, React, and Svelte bindings also mount cached pages differently. Exact option names and defaults for Framework7 v6 and v7 require verification against the installed release.

Does returning to a domCache page under pushState remount the page or reuse the existing DOM node? Which lifecycle events fire on repeat visits, and where should listeners be attached so they are neither duplicated nor lost? Does the answer change between Framework7 Core and its Vue, React, or Svelte bindings?