inertia-defer-default

To stop Inertia partial reloads from running heavy database queries, wrap expensive controller props like paginate, count, and eager-loaded aggregations with `Inertia::defer(fn () => ...)` so execution only happens when requested by the frontend.

Inertia pages experience full page loading during partial reloads because unnecessary backend SQL work and external HTTP calls execute synchronously. Deferring heavy controller props prevents this degraded UX by delaying execution until the frontend actually requests the data.

To render deferred Inertia props in React without undefined errors, use the `@inertiajs/react` `<Deferred>` component with skeleton fallbacks and mark the deferred props as optional (`?:`) to safely handle runtime states when data is not yet available.

You should not use Inertia defer for Laravel controller props when the data is immediately required for initial page render or falls under legitimate exceptions. Deferring critical data risks blank screens and breaks layout if frontend skeleton fallbacks are not properly configured.

Laravel controller props derived from paginate, count, eager-loads, aggregations, subqueries, service database calls, and external HTTP requests should be wrapped with Inertia defer to reduce unnecessary backend work during partial reloads.