chore: update librarian to v0.26.0

analytics/examples/admin/apiv1alpha/snippet_metadata.google.analytics.admin.v1alpha.json

@@ -453,7 +453,7 @@
         "resultType": "*adminpb.DisplayVideo360AdvertiserLinkProposal",
         "shortName": "CancelDisplayVideo360AdvertiserLinkProposal"
       },
-      "description": "CancelDisplayVideo360AdvertiserLinkProposal cancels a DisplayVideo360AdvertiserLinkProposal.\nCancelling can mean either: \n- Declining a proposal initiated from Display \u0026 Video 360\n- Withdrawing a proposal initiated from Google Analytics\nAfter being cancelled, a proposal will eventually be deleted automatically.",
+      "description": "CancelDisplayVideo360AdvertiserLinkProposal cancels a DisplayVideo360AdvertiserLinkProposal.\nCancelling can mean either: \n- Declining a proposal initiated from Display & Video 360\n- Withdrawing a proposal initiated from Google Analytics\nAfter being cancelled, a proposal will eventually be deleted automatically.",
       "file": "AnalyticsAdminClient/CancelDisplayVideo360AdvertiserLinkProposal/main.go",
       "language": "GO",
       "origin": "API_DEFINITION",
@@ -959,7 +959,7 @@
         "resultType": "*adminpb.DisplayVideo360AdvertiserLink",
         "shortName": "CreateDisplayVideo360AdvertiserLink"
       },
-      "description": "CreateDisplayVideo360AdvertiserLink creates a DisplayVideo360AdvertiserLink.\nThis can only be utilized by users who have proper authorization both on\nthe Google Analytics property and on the Display \u0026 Video 360 advertiser.\nUsers who do not have access to the Display \u0026 Video 360 advertiser should\ninstead seek to create a DisplayVideo360LinkProposal.",
+      "description": "CreateDisplayVideo360AdvertiserLink creates a DisplayVideo360AdvertiserLink.\nThis can only be utilized by users who have proper authorization both on\nthe Google Analytics property and on the Display & Video 360 advertiser.\nUsers who do not have access to the Display & Video 360 advertiser should\ninstead seek to create a DisplayVideo360LinkProposal.",
       "file": "AnalyticsAdminClient/CreateDisplayVideo360AdvertiserLink/main.go",
       "language": "GO",
       "origin": "API_DEFINITION",
@@ -5720,7 +5720,7 @@
         "resultType": "*adminpb.RunAccessReportResponse",
         "shortName": "RunAccessReport"
       },
-      "description": "RunAccessReport returns a customized report of data access records. The report provides\nrecords of each time a user reads Google Analytics reporting data. Access\nrecords are retained for up to 2 years.\n\nData Access Reports can be requested for a property. Reports may be\nrequested for any property, but dimensions that aren't related to quota can\nonly be requested on Google Analytics 360 properties. This method is only\navailable to Administrators.\n\nThese data access records include GA UI Reporting, GA UI Explorations,\nGA Data API, and other products like Firebase \u0026 Admob that can retrieve\ndata from Google Analytics through a linkage. These records don't include\nproperty configuration changes like adding a stream or changing a\nproperty's time zone. For configuration change history, see\n[searchChangeHistoryEvents](https: //developers.google.com/analytics/devguides/config/admin/v1/rest/v1alpha/accounts/searchChangeHistoryEvents).\n\nTo give your feedback on this API, complete the [Google Analytics Access\nReports\nfeedback](https: //docs.google.com/forms/d/e/1FAIpQLSdmEBUrMzAEdiEKk5TV5dEHvDUZDRlgWYdQdAeSdtR4hVjEhw/viewform)\nform.",
+      "description": "RunAccessReport returns a customized report of data access records. The report provides\nrecords of each time a user reads Google Analytics reporting data. Access\nrecords are retained for up to 2 years.\n\nData Access Reports can be requested for a property. Reports may be\nrequested for any property, but dimensions that aren't related to quota can\nonly be requested on Google Analytics 360 properties. This method is only\navailable to Administrators.\n\nThese data access records include GA UI Reporting, GA UI Explorations,\nGA Data API, and other products like Firebase & Admob that can retrieve\ndata from Google Analytics through a linkage. These records don't include\nproperty configuration changes like adding a stream or changing a\nproperty's time zone. For configuration change history, see\n[searchChangeHistoryEvents](https: //developers.google.com/analytics/devguides/config/admin/v1/rest/v1alpha/accounts/searchChangeHistoryEvents).\n\nTo give your feedback on this API, complete the [Google Analytics Access\nReports\nfeedback](https: //docs.google.com/forms/d/e/1FAIpQLSdmEBUrMzAEdiEKk5TV5dEHvDUZDRlgWYdQdAeSdtR4hVjEhw/viewform)\nform.",
       "file": "AnalyticsAdminClient/RunAccessReport/main.go",
       "language": "GO",
       "origin": "API_DEFINITION",

ces/examples/apiv1/snippet_metadata.google.cloud.ces.v1.json

@@ -2513,7 +2513,7 @@
         "resultType": "cespb.SessionService_BidiRunSessionClient",
         "shortName": "BidiRunSession"
       },
-      "description": "BidiRunSession establishes a bidirectional streaming connection with the CES agent.\nThe agent processes continuous multimodal inputs (e.g., text, audio) and\ngenerates real-time multimodal output streams.\n\n--- Client Request Stream ---\nThe client streams requests in the following order: \n\n1.  Initialization: \nThe first message must contain\n[SessionConfig][google.cloud.ces.v1.BidiSessionClientMessage.config].\nFor audio sessions, this should also include\n[InputAudioConfig][google.cloud.ces.v1.SessionConfig.input_audio_config]\nand\n[OutputAudioConfig][google.cloud.ces.v1.SessionConfig.output_audio_config]\nto define audio processing and synthesis parameters.\n\n2.  Interaction: \nSubsequent messages stream\n[SessionInput][google.cloud.ces.v1.BidiSessionClientMessage.realtime_input]\ncontaining real-time user input data.\n\n3.  Termination: \nThe client should half-close the stream when there is no more user\ninput. It should also half-close upon receiving\n[EndSession][google.cloud.ces.v1.BidiSessionServerMessage.end_session]\nor [GoAway][google.cloud.ces.v1.BidiSessionServerMessage.go_away] from\nthe agent.\n\n--- Server Response Stream ---\nFor each interaction turn, the agent streams messages in the following\nsequence: \n\n1.  Speech Recognition (First N messages): \nContains\n[RecognitionResult][google.cloud.ces.v1.BidiSessionServerMessage.recognition_result]\nrepresenting the concatenated user speech segments captured so far.\nThis is only populated for audio sessions.\n\n2.  Response (Next M messages): \nContains\n[SessionOutput][google.cloud.ces.v1.BidiSessionServerMessage.session_output]\ndelivering the agent's response in various modalities (e.g., text,\naudio).\n\n3.  Turn Completion (Final message of the turn): \nContains\n[SessionOutput][google.cloud.ces.v1.BidiSessionServerMessage.session_output]\nwith [turn_completed][google.cloud.ces.v1.SessionOutput.turn_completed]\nset to true. This signals the end of the current turn and includes\n[DiagnosticInfo][google.cloud.ces.v1.SessionOutput.diagnostic_info]\nwith execution details.\n\n--- Audio Best Practices ---\n1.  Streaming: \nStream [audio data][google.cloud.ces.v1.SessionInput.audio]\n**CONTINUOUSLY**, even during silence. Recommended chunk size: 40-120ms\n(balances latency vs. efficiency).\n\n2.  Playback \u0026 Interruption: \nPlay [audio responses][google.cloud.ces.v1.SessionOutput.audio] upon\nreceipt. Stop playback immediately if an\n[InterruptionSignal][google.cloud.ces.v1.BidiSessionServerMessage.interruption_signal]\nis received (e.g., user barge-in or new agent response).\n\n\nThis method is not supported for the REST transport.",
+      "description": "BidiRunSession establishes a bidirectional streaming connection with the CES agent.\nThe agent processes continuous multimodal inputs (e.g., text, audio) and\ngenerates real-time multimodal output streams.\n\n--- Client Request Stream ---\nThe client streams requests in the following order: \n\n1.  Initialization: \nThe first message must contain\n[SessionConfig][google.cloud.ces.v1.BidiSessionClientMessage.config].\nFor audio sessions, this should also include\n[InputAudioConfig][google.cloud.ces.v1.SessionConfig.input_audio_config]\nand\n[OutputAudioConfig][google.cloud.ces.v1.SessionConfig.output_audio_config]\nto define audio processing and synthesis parameters.\n\n2.  Interaction: \nSubsequent messages stream\n[SessionInput][google.cloud.ces.v1.BidiSessionClientMessage.realtime_input]\ncontaining real-time user input data.\n\n3.  Termination: \nThe client should half-close the stream when there is no more user\ninput. It should also half-close upon receiving\n[EndSession][google.cloud.ces.v1.BidiSessionServerMessage.end_session]\nor [GoAway][google.cloud.ces.v1.BidiSessionServerMessage.go_away] from\nthe agent.\n\n--- Server Response Stream ---\nFor each interaction turn, the agent streams messages in the following\nsequence: \n\n1.  Speech Recognition (First N messages): \nContains\n[RecognitionResult][google.cloud.ces.v1.BidiSessionServerMessage.recognition_result]\nrepresenting the concatenated user speech segments captured so far.\nThis is only populated for audio sessions.\n\n2.  Response (Next M messages): \nContains\n[SessionOutput][google.cloud.ces.v1.BidiSessionServerMessage.session_output]\ndelivering the agent's response in various modalities (e.g., text,\naudio).\n\n3.  Turn Completion (Final message of the turn): \nContains\n[SessionOutput][google.cloud.ces.v1.BidiSessionServerMessage.session_output]\nwith [turn_completed][google.cloud.ces.v1.SessionOutput.turn_completed]\nset to true. This signals the end of the current turn and includes\n[DiagnosticInfo][google.cloud.ces.v1.SessionOutput.diagnostic_info]\nwith execution details.\n\n--- Audio Best Practices ---\n1.  Streaming: \nStream [audio data][google.cloud.ces.v1.SessionInput.audio]\n**CONTINUOUSLY**, even during silence. Recommended chunk size: 40-120ms\n(balances latency vs. efficiency).\n\n2.  Playback & Interruption: \nPlay [audio responses][google.cloud.ces.v1.SessionOutput.audio] upon\nreceipt. Stop playback immediately if an\n[InterruptionSignal][google.cloud.ces.v1.BidiSessionServerMessage.interruption_signal]\nis received (e.g., user barge-in or new agent response).\n\n\nThis method is not supported for the REST transport.",
       "file": "SessionClient/BidiRunSession/main.go",
       "language": "GO",
       "origin": "API_DEFINITION",

ces/examples/apiv1beta/snippet_metadata.google.cloud.ces.v1beta.json

@@ -4530,7 +4530,7 @@
         "resultType": "cespb.SessionService_BidiRunSessionClient",
         "shortName": "BidiRunSession"
       },
-      "description": "BidiRunSession establishes a bidirectional streaming connection with the CES agent.\nThe agent processes continuous multimodal inputs (e.g., text, audio) and\ngenerates real-time multimodal output streams.\n\n--- Client Request Stream ---\nThe client streams requests in the following order: \n\n1.  Initialization: \nThe first message must contain\n[SessionConfig][google.cloud.ces.v1beta.BidiSessionClientMessage.config].\nFor audio sessions, this should also include\n[InputAudioConfig][google.cloud.ces.v1beta.SessionConfig.input_audio_config]\nand\n[OutputAudioConfig][google.cloud.ces.v1beta.SessionConfig.output_audio_config]\nto define audio processing and synthesis parameters.\n\n2.  Interaction: \nSubsequent messages stream\n[SessionInput][google.cloud.ces.v1beta.BidiSessionClientMessage.realtime_input]\ncontaining real-time user input data.\n\n3.  Termination: \nThe client should half-close the stream when there is no more user\ninput. It should also half-close upon receiving\n[EndSession][google.cloud.ces.v1beta.BidiSessionServerMessage.end_session]\nor [GoAway][google.cloud.ces.v1beta.BidiSessionServerMessage.go_away]\nfrom the agent.\n\n--- Server Response Stream ---\nFor each interaction turn, the agent streams messages in the following\nsequence: \n\n1.  Speech Recognition (First N messages): \nContains\n[RecognitionResult][google.cloud.ces.v1beta.BidiSessionServerMessage.recognition_result]\nrepresenting the concatenated user speech segments captured so far.\nThis is only populated for audio sessions.\n\n2.  Response (Next M messages): \nContains\n[SessionOutput][google.cloud.ces.v1beta.BidiSessionServerMessage.session_output]\ndelivering the agent's response in various modalities (e.g., text,\naudio).\n\n3.  Turn Completion (Final message of the turn): \nContains\n[SessionOutput][google.cloud.ces.v1beta.BidiSessionServerMessage.session_output]\nwith\n[turn_completed][google.cloud.ces.v1beta.SessionOutput.turn_completed]\nset to true. This signals the end of the current turn and includes\n[DiagnosticInfo][google.cloud.ces.v1beta.SessionOutput.diagnostic_info]\nwith execution details.\n\n--- Audio Best Practices ---\n1.  Streaming: \nStream [audio data][google.cloud.ces.v1beta.SessionInput.audio]\n**CONTINUOUSLY**, even during silence. Recommended chunk size: 40-120ms\n(balances latency vs. efficiency).\n\n2.  Playback \u0026 Interruption: \nPlay [audio responses][google.cloud.ces.v1beta.SessionOutput.audio]\nupon receipt. Stop playback immediately if an\n[InterruptionSignal][google.cloud.ces.v1beta.BidiSessionServerMessage.interruption_signal]\nis received (e.g., user barge-in or new agent response).\n\n\nThis method is not supported for the REST transport.",
+      "description": "BidiRunSession establishes a bidirectional streaming connection with the CES agent.\nThe agent processes continuous multimodal inputs (e.g., text, audio) and\ngenerates real-time multimodal output streams.\n\n--- Client Request Stream ---\nThe client streams requests in the following order: \n\n1.  Initialization: \nThe first message must contain\n[SessionConfig][google.cloud.ces.v1beta.BidiSessionClientMessage.config].\nFor audio sessions, this should also include\n[InputAudioConfig][google.cloud.ces.v1beta.SessionConfig.input_audio_config]\nand\n[OutputAudioConfig][google.cloud.ces.v1beta.SessionConfig.output_audio_config]\nto define audio processing and synthesis parameters.\n\n2.  Interaction: \nSubsequent messages stream\n[SessionInput][google.cloud.ces.v1beta.BidiSessionClientMessage.realtime_input]\ncontaining real-time user input data.\n\n3.  Termination: \nThe client should half-close the stream when there is no more user\ninput. It should also half-close upon receiving\n[EndSession][google.cloud.ces.v1beta.BidiSessionServerMessage.end_session]\nor [GoAway][google.cloud.ces.v1beta.BidiSessionServerMessage.go_away]\nfrom the agent.\n\n--- Server Response Stream ---\nFor each interaction turn, the agent streams messages in the following\nsequence: \n\n1.  Speech Recognition (First N messages): \nContains\n[RecognitionResult][google.cloud.ces.v1beta.BidiSessionServerMessage.recognition_result]\nrepresenting the concatenated user speech segments captured so far.\nThis is only populated for audio sessions.\n\n2.  Response (Next M messages): \nContains\n[SessionOutput][google.cloud.ces.v1beta.BidiSessionServerMessage.session_output]\ndelivering the agent's response in various modalities (e.g., text,\naudio).\n\n3.  Turn Completion (Final message of the turn): \nContains\n[SessionOutput][google.cloud.ces.v1beta.BidiSessionServerMessage.session_output]\nwith\n[turn_completed][google.cloud.ces.v1beta.SessionOutput.turn_completed]\nset to true. This signals the end of the current turn and includes\n[DiagnosticInfo][google.cloud.ces.v1beta.SessionOutput.diagnostic_info]\nwith execution details.\n\n--- Audio Best Practices ---\n1.  Streaming: \nStream [audio data][google.cloud.ces.v1beta.SessionInput.audio]\n**CONTINUOUSLY**, even during silence. Recommended chunk size: 40-120ms\n(balances latency vs. efficiency).\n\n2.  Playback & Interruption: \nPlay [audio responses][google.cloud.ces.v1beta.SessionOutput.audio]\nupon receipt. Stop playback immediately if an\n[InterruptionSignal][google.cloud.ces.v1beta.BidiSessionServerMessage.interruption_signal]\nis received (e.g., user barge-in or new agent response).\n\n\nThis method is not supported for the REST transport.",
       "file": "SessionClient/BidiRunSession/main.go",
       "language": "GO",
       "origin": "API_DEFINITION",

chat/examples/apiv1/snippet_metadata.google.chat.v1.json

@@ -2200,7 +2200,7 @@
         "resultType": "*chatpb.UploadAttachmentResponse",
         "shortName": "UploadAttachment"
       },
-      "description": "UploadAttachment uploads an attachment. For an example, see\n[Upload media as a file\nattachment](https: //developers.google.com/workspace/chat/upload-media-attachments).\n\nRequires user\n[authentication](https: //developers.google.com/workspace/chat/authenticate-authorize-chat-user)\nwith one of the following [authorization\nscopes](https: //developers.google.com/workspace/chat/authenticate-authorize#chat-api-scopes): \n\n- `https: //www.googleapis.com/auth/chat.messages.create`\n- `https: //www.googleapis.com/auth/chat.messages`\n- `https: //www.googleapis.com/auth/chat.import` (import mode spaces only)\n\nYou can upload attachments up to 200 MB. Certain file types aren't\nsupported. For details, see [File types blocked by Google\nChat](https: //support.google.com/chat/answer/7651457?\u0026co=GENIE.Platform%3DDesktop#File%20types%20blocked%20in%20Google%20Chat).",
+      "description": "UploadAttachment uploads an attachment. For an example, see\n[Upload media as a file\nattachment](https: //developers.google.com/workspace/chat/upload-media-attachments).\n\nRequires user\n[authentication](https: //developers.google.com/workspace/chat/authenticate-authorize-chat-user)\nwith one of the following [authorization\nscopes](https: //developers.google.com/workspace/chat/authenticate-authorize#chat-api-scopes): \n\n- `https: //www.googleapis.com/auth/chat.messages.create`\n- `https: //www.googleapis.com/auth/chat.messages`\n- `https: //www.googleapis.com/auth/chat.import` (import mode spaces only)\n\nYou can upload attachments up to 200 MB. Certain file types aren't\nsupported. For details, see [File types blocked by Google\nChat](https: //support.google.com/chat/answer/7651457?&co=GENIE.Platform%3DDesktop#File%20types%20blocked%20in%20Google%20Chat).",
       "file": "Client/UploadAttachment/main.go",
       "language": "GO",
       "origin": "API_DEFINITION",

cloudcontrolspartner/examples/apiv1/snippet_metadata.google.cloud.cloudcontrolspartner.v1.json

@@ -594,7 +594,7 @@
         "resultType": "ViolationIterator",
         "shortName": "ListViolations"
       },
-      "description": "ListViolations lists Violations for a workload\nCallers may also choose to read across multiple Customers or for a single\ncustomer as per\n[AIP-159](https: //google.aip.dev/159) by using '-' (the hyphen or dash\ncharacter) as a wildcard character instead of {customer} \u0026 {workload}.\nFormat: \n`organizations/{organization}/locations/{location}/customers/{customer}/workloads/{workload}`",
+      "description": "ListViolations lists Violations for a workload\nCallers may also choose to read across multiple Customers or for a single\ncustomer as per\n[AIP-159](https: //google.aip.dev/159) by using '-' (the hyphen or dash\ncharacter) as a wildcard character instead of {customer} & {workload}.\nFormat: \n`organizations/{organization}/locations/{location}/customers/{customer}/workloads/{workload}`",
       "file": "CloudControlsPartnerMonitoringClient/ListViolations/main.go",
       "language": "GO",
       "origin": "API_DEFINITION",

cloudcontrolspartner/examples/apiv1beta/snippet_metadata.google.cloud.cloudcontrolspartner.v1beta.json

@@ -594,7 +594,7 @@
         "resultType": "ViolationIterator",
         "shortName": "ListViolations"
       },
-      "description": "ListViolations lists Violations for a workload\nCallers may also choose to read across multiple Customers or for a single\ncustomer as per\n[AIP-159](https: //google.aip.dev/159) by using '-' (the hyphen or dash\ncharacter) as a wildcard character instead of {customer} \u0026 {workload}.\nFormat: \n`organizations/{organization}/locations/{location}/customers/{customer}/workloads/{workload}`",
+      "description": "ListViolations lists Violations for a workload\nCallers may also choose to read across multiple Customers or for a single\ncustomer as per\n[AIP-159](https: //google.aip.dev/159) by using '-' (the hyphen or dash\ncharacter) as a wildcard character instead of {customer} & {workload}.\nFormat: \n`organizations/{organization}/locations/{location}/customers/{customer}/workloads/{workload}`",
       "file": "CloudControlsPartnerMonitoringClient/ListViolations/main.go",
       "language": "GO",
       "origin": "API_DEFINITION",