Kaituo Huang

This commit provides a **documentation update** across the **`google.genai._interactions.types`** module, clarifying the usage of key identifiers. It updates docstrings for `id` and `call_id` fields within numerous `*CallContent`, `*ResultContent`, and `*Delta` classes, explicitly stating that these fields are **required**. This **maintenance** work enhances the clarity and correctness of the API specifications, improving developer understanding of mandatory identifiers for various interaction types, including code execution, file search, and function calls, by referencing their role in 'function call blocks'.

This commit performs **maintenance and documentation updates** within the `google.genai._interactions.types` module, which defines the data models for various interaction components. It primarily **clarifies the required status of numerous fields** across content types (e.g., `CodeExecutionCallContent`, `FunctionCallContent`), interaction events, and tool definitions by updating their docstrings. Additionally, minor **refactoring** was performed to adjust field optionality and reorder declarations in models like `DeltaFileSearchResult` and `GoogleMaps`, ensuring the type definitions accurately reflect the API contract. These changes enhance the **clarity and robustness of the `genai` library's type system**, providing more precise guidance for developers.

This commit performs a **maintenance and refactoring** pass on the **GenAI interactions type definitions** within `google/genai/_interactions/types/`. It significantly **improves documentation clarity** by updating comments for fields like `event_id` and `start_index` across various event and citation types. Concurrently, it **reorganizes and groups** related content, interaction, and tool types, enhancing the overall structure and readability of these core definitions. This work aims to improve code maintainability and understanding without introducing any functional changes.

This commit **refactors** the `google.genai._interactions.types.content_delta` module by renaming several **ContentDelta** classes and type aliases. The redundant 'Delta' suffix has been removed from these names to improve clarity and consistency within the **Interactions** subsystem. This is a **breaking change** for the `genai` library, requiring users to update their code to reflect the new, streamlined type names.

This commit performs **maintenance** and **refactoring** within the `google.genai._interactions` module, primarily to improve internal code consistency and documentation. It **standardizes type definitions** by refactoring type aliases and updating the type of the `result` field in various content types, including `FunctionResultContent` and `MCPServerToolResultContent`. Concurrently, the commit **enhances code clarity** by updating docstrings for key parameters like `input` and `agent_config` across interaction creation methods and type definitions. Minor structural adjustments, such as reordering `str` in the `Input` type alias and the `GoogleSearch` definition within `Tool` type aliases, further contribute to the **internal consistency** of the API's type system. These changes collectively improve the maintainability and understanding of the interaction-related types and resources.

This commit performs a **cleanup chore** by **removing all "Stainless" related HTTP headers and associated logic** from the `google.genai._interactions` client module. It eliminates the `x-stainless-retry-count` and `x-stainless-read-timeout` headers, along with the `retries_taken` parameter and `platform_headers` from the base client's request building process. Additionally, the `X-Stainless-Async` header is removed from the default headers in both synchronous and asynchronous client implementations. This **maintenance task** streamlines the client's request generation by removing deprecated or unused header mechanisms, simplifying the underlying HTTP interaction layer.

This commit performs a **documentation update** by clarifying the docstring for the `interaction` field within the `InteractionCompleteEvent` type, located in `google/genai/_interactions/types/interaction_complete_event.py`. This **maintenance** task aims to improve developer understanding of the field's content and usage within the **GenAI interactions module**. The change enhances code readability and usability for consumers of this event type, without introducing any functional modifications.

This commit introduces a **refactoring** within the **`google.genai._interactions` subsystem**, specifically altering how `mime_type` values are defined for various media content types. It **inlines literal `mime_type` values** directly into the definitions for audio, document, image, and video content, including their parameter and delta classes, and removes external type imports. This change, while a **breaking change for an experimental feature**, aims to standardize and simplify the `mime_type` handling across these interaction types. Consequently, developers utilizing the experimental `_interactions` API will need to update their code to align with the new inlined `mime_type` definitions.

This commit **enhances** the **`google.genai` library** by adding comprehensive support for **metadata in batch inlined responses**. It introduces an optional `metadata` field to the `InlinedResponse` type in `google/genai/types.py` and implements the necessary logic within `google/genai/batches.py`'s `_InlinedResponse_from_mldev` function to correctly populate this data from mldev objects. This **bug fix** ensures that users performing batch operations will now receive complete response data, including any associated metadata, directly within their `InlinedResponse` objects. Updated test cases validate the correct handling and inclusion of this new metadata, significantly improving the completeness and usability of batch results.

docs: Update docs to include interactions and file_search_stores module

This commit **updates the GenAI interaction model definitions** to officially recognize the new `gemini-3-flash-preview` model. It performs **maintenance** by adding `gemini-3-flash-preview` to the allowed model names within the `Model` and `ModelParam` type aliases in `google/genai/_interactions/types/model.py` and `google/genai/_interactions/types/model_param.py`. This change **enables support for the new model**, allowing it to be correctly specified and used in GenAI interactions. The update ensures that the **GenAI client library is compatible with the latest model offerings**, providing developers with access to the new preview model.

This commit provides a **documentation update** for the **`genai` library's interaction resources**. Specifically, the docstrings for the `cancel` methods in both `InteractionsResource` and `AsyncInteractionsResource` within `google/genai/_interactions/resources/interactions.py` have been updated. This change clarifies that the `cancel` functionality is exclusively applicable to **running background interactions**, ensuring developers have a precise understanding of its intended use and limitations. The update aims to prevent potential misuse by clearly defining the scope of interaction cancellation.

This commit **updates the documentation** for **code generation instructions** to reflect the availability and usage of new AI models. Specifically, the `codegen_instructions.md` file now guides users to leverage **Gemini 3 Pro** and **Nano Banana Pro** models. This **documentation update** includes revised code examples, particularly for **image generation**, ensuring developers have accurate and current guidance for integrating these advanced models. The change improves the relevance and utility of the developer guides by keeping them aligned with the latest model offerings.

This commit introduces a **new capability** by adding an optional `display_name` field to the **`FunctionResponseBlob`** and `FunctionResponseBlobDict` types within the **`google.genai.types`** module. This enhancement allows users to provide a human-readable label or name for function response blobs. The addition improves the clarity and identification of these data structures, making it easier to manage and understand their purpose within the GenAI framework.

This commit introduces a **bug fix** for the **`google.genai.documents`** module, resolving an issue where pagination failed due to the `parent` argument not being correctly passed to internal `Pager` and `AsyncPager` constructors. Specifically, the `list` methods in `documents.py` now properly initialize these pagers, ensuring complete retrieval of document lists. Additionally, this commit significantly enhances test coverage for the `documents` API by adding new **unit tests** for `list`, `get`, and `delete` operations. These new tests include specific validation for the now-fixed pagination functionality, ensuring reliable and complete data retrieval for users interacting with document stores.

This commit introduces a **new capability** to the `google.genai` library by adding the **`FileSearch` tool** and comprehensive **`FileSearchStore` management APIs**. It includes new modules like `google/genai/file_search_stores.py` and `google/genai/documents.py` for CRUD operations on stores and their contents, integrated into the main `Client` via `file_search_stores` and `async_file_search_stores` properties. This allows users to programmatically create, manage, and upload files to dedicated search stores, and utilize the `FileSearch` tool within generative AI models. Extensive type definitions in `google/genai/types.py` and conversion logic updates in `_converters.py` files support this significant expansion of the library's functionality. New tests validate the creation, deletion, retrieval, and file import/upload processes for these new resources.

This commit introduces a **new feature** to the **`google.genai` library**, specifically within the `_extra_utils.py` module. It enhances the **resumable upload** process by ensuring that the base file name is now passed to the backend when a file path is provided as input. The `prepare_resumable_upload` function is updated to include this file name in the `X-Goog-Upload-File-Name` header. This change improves backend visibility and identification of uploaded files, facilitating better management and processing on the server side.

This commit introduces **new utility methods** within the **`google.genai.types` module** to enhance the creation of `FunctionResponsePart` and `Part` objects. It adds `from_bytes` and `from_uri` class methods to `FunctionResponsePart`, enabling direct construction from raw data or external resources. Furthermore, the `Part.from_function_response` method is extended to support optional multi-modal parts, allowing for more comprehensive and flexible representation of function call results. This **feature enhancement** improves the library's capability to handle diverse data types in function responses, particularly for multi-modal scenarios, making the **function calling feature** more robust.

This commit introduces **new tests** for the `computer_use` tool within the `google.genai.tests.models` module, specifically in `test_generate_content_tools.py`. These additions enhance the **test coverage** for tool usage, validating multi-turn interactions and function override capabilities. This **maintenance** work ensures the robustness and correct behavior of the `computer_use` tool, improving the reliability of content generation with tool integration.

This commit **refactors** the **resumable upload preparation logic** by extracting it into a new, reusable utility method. Specifically, the `prepare_resumable_upload` function is introduced in `google/genai/_extra_utils.py` to encapsulate the determination of file size, MIME type, and the construction of HTTP options. The existing `upload_file` and `async_upload_file` methods within `google/genai/files.py` are updated to leverage this new utility. This change **centralizes common logic**, improving code maintainability and consistency for all resumable file uploads within the `genai` library.