typeBasePsets (the defining TYPE object's own property sets, as
getInheritedTypePsets in filter-evaluate.ts already resolves them —
the type-specific on-demand path, not ownPropertySetsFor, since a
type object walks a different relation than an occurrence) topped up
with the mutation view's edit of that TYPE, when it has one — an
edited pset replaces its base counterpart by name, an untouched one
passes through. Same overlay element-field-reader.ts's typeSetsFor
applies for the Elements chart's own field column (#4946 review).
typeBasePsets(the defining TYPE object's own property sets, asgetInheritedTypePsetsin filter-evaluate.ts already resolves them — the type-specific on-demand path, notownPropertySetsFor, since a type object walks a different relation than an occurrence) topped up with the mutation view's edit of that TYPE, when it has one — an edited pset replaces its base counterpart by name, an untouched one passes through. Same overlayelement-field-reader.ts'stypeSetsForapplies for the Elements chart's own field column (#4946 review).