Does Nuxt Bridge share SSR cache keys between Nuxt 2 and Nuxt 3 routes?

When running a Nuxt 2 application under Nuxt Bridge, developers can gradually introduce Nuxt 3 features such as composables and server APIs on a per‑route basis. The bridge allows both webpack‑based Nuxt 2 pages and Vite‑powered Nuxt 3 pages to coexist, but the documentation does not clarify how the server‑side rendering cache treats requests that originate from the two different runtimes.

Uncertainty about whether SSR cache keys are shared or isolated between legacy and new routes raises the risk of serving stale or incorrectly varied content. Clarifying this behavior is essential for teams that rely on caching to maintain performance and correctness during incremental migration.

• Are SSR cache keys generated separately for Nuxt 2 and Nuxt 3 routes when using Nuxt Bridge?
• If the keys are shared, what inputs (e.g., URL, query, headers, runtime flag) compose the key?
• How can a project enforce isolation of cache entries between the two runtimes if shared keys cause conflicts?