const assets = await prisma.asset.findMany({
  where: {
    AND: [
      { date: { not: null } },
      { date: { gte: "2024-01-01", lte: "2024-12-31" } }
    ]
  },
  include: { items: true }
})

// Before: assets[0].items would show TypeScript error
// After: assets[0].items is correctly typed

## Root Cause
The `GetFindResult` type was using `Equals<A, any> extends 1` which was too broad and caught cases where TypeScript inferred complex types as `any` due to complexity, causing fallback to `DefaultSelection` (base model without includes).

## Solution
Replaced the type check with a more precise one that only falls back to `DefaultSelection` when the type is explicitly `any`, not when it's complex: