E defaults to {}, so every existing MetadataQueryEntry<T> keeps meaning
exactly what it meant — the extra-fields form is opt-in at the type level.
path and meta are applied AFTER the record's own fields, so a query cannot
shadow them with something else.
One match from MetadataQueryFunction: the file path paired with its frontmatter, plus any extra fields the query returned as a MetadataQueryRecord.
Edefaults to{}, so every existingMetadataQueryEntry<T>keeps meaning exactly what it meant — the extra-fields form is opt-in at the type level.pathandmetaare applied AFTER the record's own fields, so a query cannot shadow them with something else.