fix: unwrap reactive component definitions with toRaw at the render boundary

The admin resolver (useDataResolver) and ResourceManager's selected tab pass a
component definition that lives in a reactive ref straight to h()/`<component :is>`.
Vue warns ("received a Component that was made a reactive object") and pays
needless Proxy overhead. toRaw the definition at the point of render — the
containing ref stays fully reactive, only the component handed to the renderer
is raw. No behaviour change; removes the warnings + overhead.

Author: silverbackdan

src/runtime/templates/components/core/useDataResolver.ts

@@ -3,6 +3,7 @@ import {
   defineComponent,
   h, onBeforeUnmount, onMounted,
   ref,
+  toRaw,
   watch,
   render,
 } from 'vue'
@@ -25,10 +26,14 @@ export const useDataResolver = <T extends object>(allMeta: Ref<(T | null)[]>, op
     (props: { component: ManagerTab, cProps: any }, { expose }) => {
       const metadata = ref<T | null>(null)
       const resolved = ref(false)
+      // `props.component` arrives as a reactive proxy (it lives in the reactive `components` ref of
+      // the caller). A component definition needs no reactivity, and handing a reactive object to
+      // `h()` triggers a Vue perf warning — so unwrap to the raw definition. The caller's ref stays
+      // fully reactive; only the component object passed to the renderer is raw.
       const possibleAsyncDefinition: ReturnType<typeof defineAsyncComponent> | undefined
         = typeof props.component === 'string'
           ? globalComponents[props.component]
-          : props.component
+          : toRaw(props.component)
 
       if (possibleAsyncDefinition === undefined) {
         throw new Error('Cannot load metadata for component')

src/runtime/templates/components/main/admin/resource-manager/ResourceManager.vue

@@ -1,5 +1,5 @@
 <script lang="ts" setup>
-import { computed, nextTick, onBeforeUnmount, onMounted, ref, useTemplateRef, watch } from 'vue'
+import { computed, nextTick, onBeforeUnmount, onMounted, ref, toRaw, useTemplateRef, watch } from 'vue'
 import ResourceLoadingIndicator
   from '../_common/ResourceLoadingIndicator.vue'
 import ManagerTabs from './_parts/ManagerTabs.vue'
@@ -103,7 +103,11 @@ const showSpacer = computed(() => {
 })
 
 const selectedTab = computed(() => {
-  return currentStackItem.value?.managerTabs?.[selectedIndex.value]
+  // the tab component lives in the reactive `currentStackItem`; hand `<component :is>` the raw
+  // definition so Vue doesn't render (and warn about) a reactive component object. No reactivity
+  // change — the stack item stays reactive, only the rendered component reference is raw.
+  const tab = currentStackItem.value?.managerTabs?.[selectedIndex.value]
+  return tab ? toRaw(tab) : tab
 })
 
 watch([spacer, managerHolder, currentStackItem, selectedIndex, allTabsMeta], () => {