Complete Connector Semantic Affordances

Several first-party connector manifests expose owner-visible natural-language fields as readable schema fields without declaring the retrieval and presentation affordances clients need to use them well. The concrete trigger was WhatsApp messages.content: it was granted/readable but not advertised as lexical or semantic searchable. The same pattern existed in other supported connectors.

PDPP intentionally separates readable fields from searchable fields. A field in schema.properties is not automatically indexed; a connector must declare query.search.lexicalfields or query.search.semanticfields. That is the right minimization boundary, but it creates an authoring obligation: supported connectors must not expose useful owner-visible text while failing to declare how clients can retrieve it.

The reference implementation SHALL require supported connector manifests to declare search affordances for owner-visible top-level natural-language string fields.