Enhanced Feedback & Tool Visibility Controls

Developers can now provide richer positive feedback on search results or generated content using new enum values in GoogleCloudDiscoveryengineV1betaFeedback.reasons: RELEVANT, COMPREHENSIVE, GOOD_CITATION, and ACCURATE. A new optional field, modelArmorDisputeInfo, has been added to GoogleCloudDiscoveryengineV1betaFeedback. This field, backed by the new GoogleCloudDiscoveryengineV1betaFeedbackModelArmorDisputeInfo schema, allows users to submit detailed information when disputing Model Armor's BLOCK or FLAG verdicts, including expectedLabel, sanitizationResultJson, and templateName. This is crucial for refining AI safety models. Additionally, new schemas ApiservingMcpMcpToolVisibility and ApiservingMcpMcpToolVisibilityFieldVisibility have been introduced, laying groundwork for defining and enforcing visibility restrictions on 'MCP tools' and their fields, though the visibilityEnforcementStrategy is explicitly marked as 'DO NOT USE' for now. Finally, GoogleCloudDiscoveryengineV1betaProvisionProjectRequest now includes an optional idpConfig field, enabling the specification of an Identity Provider configuration during project provisioning to streamline AclConfig setup.