Ordering of query definitions changing Model vs. not Model determination?

I'm encountering an issue where _the order in which queries are defined_ is determining whether or not a type (`Recording`, below) is correctly interpreted as a `Model` (so, just the `id` field included), vs. incorrectly interpreted (keeping all fields of nested `Recording` objects, not just the `id`).

I'm using Sofa (0.10.2), and constructing queries using `nexus-prisma` v0.35.0 (see below).

Anyone encountering behavior like this?

```
export const recordingQueries = extendType({
type: 'Query',
definition(t) {

t.field('recording', {
type: Recording.$name,
args: { id: idArg() },
resolve(_, args, ctx) {
return ctx.prisma.recording.findUnique({ where: { id: args.id ?? undefined }})
}
}),

//If this resolver definition is ABOVE the 'recordings' resolver, behavior is as expected;
//nested recording objects are limited to the id field.
//if this is BELOW the 'recordings' resolver, the behavior is unexpected;
//full nested Recording object are shown by other resolvers.
//=================
t.nonNull.list.nonNull.field('resolverForDebugging', {
type: Recording.$name,
args: { bob: stringArg() },
resolve(_, args, ctx) { return ctx.prisma.recording.findMany() }
}),
//=================

t.nonNull.list.nonNull.field('recordings', {
type: Recording.$name,
resolve(_, __, ctx) { return ctx.prisma.recording.findMany() }
})
}
})
```