Complete Connector Query Affordances

The first connector semantic-affordance pass made message-like text searchable and added presentation roles, but the live audit still found useful query semantics left implicit: time fields without range or bucket declarations, owner-recognizable fields without search/facet affordances, and ambiguity between presentation event-time roles and query-time date affordances.

Connector manifests are the authoring point where a connector says what clients can safely do with already-granted fields. The system intentionally does not infer semantics from field names at read time. That keeps honesty strong, but it means missing manifest declarations become real product gaps.

First-party polyfill connector manifests SHALL declare query affordances for useful, granted, top-level fields that the connector author knows are safe and meaningful to retrieve by. A readable field SHALL NOT be treated as searchable, range-filterable, aggregatable, or facetable unless the manifest declares that affordance or the field appears on an explicit justified non-support list.