LayoutLibraryItemUsageDetail
WHICH assets depend on one Library node, for the Where Used dialog — the rows behind the count
LayoutLibraryItemUsage returns.
A SECOND FIELD rather than buckets on that type, because a @field resolver computes its whole
payload whatever the client selected: folding these in would make the padlock and the palette
restriction — both of which want counts only, on every builder request — pay for up to four extra
asset queries they never read.
Buckets, not one list, because that is the shared ObjectUsageDialog contract: it renders one
accordion per non-empty bucket and already knows these four keys. Every entry is an asset in THIS
product holding a live reference; trashed assets are omitted, so this can list fewer than total
until the index is reconciled on delete (see LibraryNodeUsageScanner).
type LayoutLibraryItemUsageDetail {
emails: [ObjectUsageNode!]!
forms: [ObjectUsageNode!]!
landing_pages: [ObjectUsageNode!]!
ctas: [ObjectUsageNode!]!
}


