Merge branch 'latest' into W-21887816-new-params-for-OAuth-OBO-policy

Author: IsaacEldridge

CODEOWNERS

@@ -1,3 +1,3 @@
-#ECCN: EAR99
+#ECCN:Open Source
 #GUSINFO:MS CX Engineering, MS CX (DOCS)
 * @mulesoft/team-docs

modules/ROOT/nav.adoc

@@ -71,16 +71,17 @@
 * xref:des-designing-api-specs.adoc[]
 ** xref:des-create-api-specs.adoc[]
 ** xref:des-create-asyncapi-api-specs.adoc[]
+** xref:des-design-grpc-api-spec.adoc[]
 ** xref:des-create-api-fragments.adoc[]
 ** xref:des-publish-api-spec-to-exchange.adoc[]
+** xref:des-publish-grpc-api-to-exchange.adoc[]
 ** xref:des-govern-api.adoc[]
 ** xref:des-delete-api-projects.adoc[]
 
 // INTEGRATE
 * xref:int-developing-integrations.adoc[]
 ** xref:int-create-integrations.adoc[]
 ** xref:int-configure-components.adoc[]
-*** xref:int-work-with-code-snippets.adoc[]
 *** xref:int-configure-components-add.adoc[]
 *** xref:int-configure-dw-expressions.adoc[]
 *** xref:int-configure-components-check-connection.adoc[]
@@ -102,6 +103,7 @@
 * xref:imp-implementing-apis.adoc[]
 ** xref:imp-implement-api-specs.adoc[]
 ** xref:imp-asyncapi.adoc[]
+** xref:imp-implement-grpc-api-spec.adoc[]
 ** xref:imp-implement-local-apis.adoc[]
 ** xref:imp-filter-search-results.adoc[]
 

modules/ROOT/pages/_partials/acb-component-info.adoc

@@ -52,7 +52,7 @@ For reference documentation on specific connector and component configurations,
 
 //
 // tag::note-component-add-config[]
-When adding components, you can start from xref:int-work-with-code-snippets.adoc[code snippets], the canvas, or the configuration XML for your app.
+When adding components, you can start from the canvas or the configuration XML for your app.
 You can configure components from their configuration panels in the canvas or from the XML.
 // end::note-component-add-config[]
 //
@@ -97,11 +97,11 @@ To find information about more connectors, see xref:connectors::introduction/int
 
 Use the Connection Management Configuration Panel to easily configure connections to third-party systems directly from the UI. 
 
-In this panel, you can create, edit, delete, and test connections directly within the ACB interface, automatically populate connection fields using metadata provided by the connector, and save and manage connection configurations without switching to the XML view. 
+In this panel, you can create, edit, delete, and test connections directly within the IDE interface, automatically populate connection fields using metadata provided by the connector, and save and manage connection configurations without switching to the XML view. 
 
 To open the configuration panel: 
 
-* Click on an existing component, or add a new one.
+* Select an existing component, or add a new one.
 * Click the *+* icon.
 +
 This action displays the configuration panel, for example:
@@ -234,21 +234,11 @@ The configuration XML file now includes the XML for the HTTP Listener within the
 
 </flow>
 ----
-. Add another component, this time using the XML configuration menu.
+. Add another component, this time using the configuration XML.
 +
-For example, add the `<http:listener-config/>` component from a snippet.
+In the configuration XML, place your cursor before the opening `<flow>` tag. Ensure that the cursor is not inside the `<flow/>` element. Add the following code:
 +
-For more information about snippets, see xref:anypoint-code-builder::int-work-with-code-snippets.adoc[].
-+
-.. In the configuration XML, place your cursor before the opening `<flow>` tag, and type `http`.
-+
-Ensure that the cursor is not inside the `<flow/>` element.
-+
-.. Type `http`, and select the `http:listener-config` snippet:
-+
-image::anypoint-code-builder::add-http-config-snippet.png["http:listener-config snippet highlighted in the configuration XML menu"]
-+
-The snippet adds the following code:
+// image::anypoint-code-builder::add-http-config-snippet.png["http:listener-config highlighted in the configuration XML menu"]
 +
 [source,xml]
 ----

modules/ROOT/pages/_partials/acb-project-migration.adoc

@@ -29,9 +29,7 @@ Selecting *Attach Project Sources* flags the `-DattachMuleSources` parameter as
 // tag::import-mule-project-into-acb[]
 Import a shareable JAR file for a snapshot of a Mule project into the desktop IDE.
 
-To create a shareable JAR file, see xref:int-export-mule-project.adoc#shareable[Export to a Shareable JAR File].
-The contents are lightweight because they don't include dependencies.
-The IDE generates the dependencies configured in the `pom.xml` for the project. 
+To create a shareable JAR, see xref:int-export-mule-project.adoc#export-mule-project[Export Mule Project].
 
 To import a shareable JAR file in your desktop IDE:
 

modules/ROOT/pages/_partials/acb-reusable-steps.adoc

@@ -509,7 +509,7 @@ When the AsyncAPI feature is available for your organization, the Anypoint Code
 
 //
 // tag::start-implementation[]
-. From *Quick Actions*, click *Implement an API*:
+. From *Create*, click *Implement an API*:
 +
 image:anypoint-code-builder::implement-api-option-mat.png["*Implement an API* link highlighted in the *Getting Started* section"]
 . Complete the *Implement an API Specification* form:
@@ -531,7 +531,7 @@ See xref:start-add-folders.adoc[].
 
 include::partial$acb-reusable-steps.adoc[tags="proj-directory-warn"]
 
-| *Search an API Specification from Exchange* |Name of the specification in Exchange. Activate *Show filters* to narrow your search results. See xref:imp-filter-search-results.adoc[] for more information.
+| *Search an API Specification from Exchange* | Name of the specification in Exchange. Search results can include OAS, RAML, AsyncAPI, and GraphQL specifications. Activate *Show filters* to narrow your search results. See xref:imp-filter-search-results.adoc[] for more information. To implement a gRPC API spec, see xref:imp-implement-grpc-api-spec.adoc[].
 | *Mule runtime* |Mule runtime version to use for your project. 
 | *Java Version* |Java version to use for Mule. 
 |===

modules/ROOT/pages/_partials/acb-start-desktop.adoc

@@ -73,7 +73,7 @@ Ensure this option is checked.
 [[acb-menu]]
 image::anypoint-code-builder-view.png["MuleSoft icon for Anypoint Code Builder in the activity bar"]
 
-. Check that the IDE loads the <<acb-menu, Anypoint Code Builder menu>> with *Quick Actions* and *Documentation* links.
+. Check that the IDE loads the <<acb-menu, Anypoint Code Builder menu>>.
 
 . If you have an Anypoint Platform account running in the EU cloud, change the *Mule: Control Plane* setting to *EU cloud*. 
 +

modules/ROOT/pages/_partials/af-shared.adoc

@@ -30,8 +30,8 @@ a|
 |Anypoint Code Builder
 a|
 
-* Anypoint Code Builder 
-* Developer Mule Developer Generative AI User
+* Anypoint Code Builder
+* Mule Developer Generative AI User
 
 |Anypoint Design Center
 |Design Center Developer
@@ -48,7 +48,7 @@ a|
 |Usage
 |Usage Viewer
 
-|CloudHub 2.0 or Runtime Fabric (limited availability)
+|CloudHub 2.0 or Runtime Fabric
 |xref:runtime-fabric::limitations-self.adoc[Runtime Fabric permissions] xref:cloudhub-2::ps-assign-permissions.adoc[CloudHub 2.0 permissions]
 |===
 
@@ -67,7 +67,7 @@ Allowlist Anypoint Code Builder URLs. For more information, see xref:anypoint-co
 
 === MuleSoft Vibes Requirements (Optional)
 
-If you plan to use MuleSoft Vibes to create agent network projects, make sure meet xref:anypoint-code-builder::mulesoft-vibes.adoc#before-you-begin[the requirements].
+If you plan to use MuleSoft Vibes to create agent network projects, make sure you meet xref:anypoint-code-builder::mulesoft-vibes.adoc#before-you-begin[the requirements].
 
 [[cli-requirements]]
 === CLI Requirements (Optional)
@@ -121,7 +121,7 @@ Build and publish your agent network project as Anypoint Exchange assets. When y
 [[step-5-deploy]]
 === Step 5: Deploy Your Agent Network Instances
 
-Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 private space or to a Runtime Fabric (limited availability).
+Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 private space or to a Runtime Fabric.
 
 * xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-dev-agent[Deploy Your Network Using MuleSoft Vibes]
 * xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-acb[Deploy Your Network Using Anypoint Code Builder]

modules/ROOT/pages/af-agent-networks.adoc

@@ -2,9 +2,9 @@
 
 An agent network is a coordinated group of agents, brokers, LLMs, and MCP servers that acts as a central hub for defining, validating, and executing agentic processes across your enterprise.
 
-An agent network provides the building blocks of your agentic deployment while MuleSoft Agent Fabric helps you maximize the potential of every AI agent with centralized discovery, orchestration across agents and tools, cross-ecosystem governance, and full transparency into agentic interactions. 
+An agent network provides the building blocks of your agentic deployment while MuleSoft Agent Fabric helps you maximize the potential of every AI agent with centralized discovery, orchestration across agents and tools, cross-ecosystem governance, and full transparency into agentic interactions.
 
-You define your agent network in a simple, human-readable YAML file in Anypoint Code Builder. This approach abstracts away the underlying technical complexities, allowing you to focus on the business constraints and context of your process without needing to understand the inner workings of the orchestration engine. 
+You define your agent network in a simple, human-readable YAML file in Anypoint Code Builder. This approach abstracts away the underlying technical complexities, allowing you to focus on the business constraints and context of your process without needing to understand the inner workings of the orchestration engine.
 
 At the start of a new agent network project, we provide a YAML template to give you a head start. You can use MuleSoft Vibes to configure your network, publish the assets to Anypoint Exchange, and deploy your agent network instance.
 
@@ -18,10 +18,10 @@ Create robust, automated agent networks with these key benefits.
 Define your agent processes in an intentional way using a simple YAML file, which is easier and faster than writing complex code.
 * Safety and Governance
 +
-Ensure control and compliance across every agent and tool interaction with enterprise-grade governance. 
+Ensure control and compliance across every agent and tool interaction with enterprise-grade governance.
 * Observability
 +
-Gain insight into agent actions with a visual trace of their decision-making. 
+Gain insight into agent actions with a visual trace of their decision-making.
 * Flexibility
 +
 Coordinate any type of agent and tool, regardless of where it’s built and deployed so you can build a diverse network of agents.
@@ -48,7 +48,7 @@ Flex Gateway enforces authentication, least‑privilege access, and guardrails.
 * Observe
 +
 Monitoring and traces (beta) give end‑to‑end visibility into progress, failures, and latency. Visualization shows which agents interacted and where bottlenecks occurred.
-Reuse
+* Reuse
 +
 The onboarding definition (YAML) is versioned and shareable, enabling rapid adaptation for roles, regions, or subsidiaries without rebuilding flows.
 * Trust and Compliance
@@ -85,7 +85,7 @@ Your agent network can use both locally defined and externally defined MCP serve
 [[agent-networks-code-builder]]
 === Agent Networks in Anypoint Code Builder
 
-When you create agent networks, the Anypoint Code Builder canvas shows the brokers, agent, and MCP servers you've configured. 
+When you create agent networks, the Anypoint Code Builder canvas shows the brokers, agents, and MCP servers you've configured.
 
 image::af-agent-network-canvas.png["Anypoint Code Builder canvas showing brokers, agents, and MCP servers"]
 
@@ -121,90 +121,88 @@ image::agent-fabric-architecture.png[Agent Fabric showing agents and MCP servers
 [calloutlist]
 . Publish the agentic assets to Anypoint Exchange for discovery and reuse after you define the agent network (brokers, agents, MCP servers) in the agent network YAML in Anypoint Code Builder.
 . Deploy the agentic assets to CloudHub 2.0 (managed in Runtime Manager).
-. Enforce policies on incoming traffic to the network with an ingress Flex Gateway, which sits in front of broker and API endpoints.
+. Enforce policies on incoming traffic to the network with an ingress Flex Gateway, which sits in front of brokers and API endpoints.
 . Enforce policies, manage connections, and emit telemetry data with an egress Flex Gateway, which sits on outbound paths from brokers and agents to external agents and services.
 . Collect logs, metrics, and traces from Flex Gateway and runtimes in Anypoint Monitoring.
 
 [[llm-support]]
 == Large Language Models
 
-Agent network brokers support the latest Gemini and OpenAI models. 
+Agent network brokers support the latest Gemini and OpenAI models.
 
-* Azure OpenAI and OpenAI API: 
+* Azure OpenAI and OpenAI API:
 +
 ** GPT-5.2
 ** GPT-5.2 Pro
 ** GPT-5-mini
 ** GPT-5 nano
-** GPT-5.2 Pro
 ** GPT-5
 +
 * Gemini API:
 +
 ** Gemini 2.5 Pro
 ** Gemini 2.5 Flash-Lite
 ** Gemini 2.5 Flash
-** Gemini 3 Flash 
+** Gemini 3 Flash
 ** Gemini 3 Pro
 
-For more information about these models, see the https://developers.openai.com/api/docs/models[OpenAI] and https://ai.google.dev/gemini-api/docs/models[Gemini] documentation. 
+For more information about these models, see the https://developers.openai.com/api/docs/models[OpenAI] and https://ai.google.dev/gemini-api/docs/models[Gemini] documentation.
 
-The following table details the requirements and recommended models. 
+This table details the requirements and recommended models.
 
 |===
 |*Model Provider* |*Required Endpoint* |*Required Capabilities* |*Suggested Models*
 
 |OpenAI |`/responses` a|
-* Reasoning 
-* Native structured output 
-* Function and Custom tool calling 
+* Reasoning
+* Native structured output
+* Function and custom tool calling
 a|
-* For lower latency: GPT-5-mini 
+* For lower latency: GPT-5-mini
 * For complex reasoning: Evaluate models
 
 |Gemini |`/generateContent` (Native API) a|
-* Native Thinking (via thinkingBudget and thinkingLevel) 
-* Native structured output (responseSchema) 
-* Function and custom tool calling 
+* Native Thinking (via thinkingBudget and thinkingLevel)
+* Native structured output (responseSchema)
+* Function and custom tool calling
 a|
-* For lower latency: Gemini 2.5 Flash, Gemini 2.5 Flash-Lite 
+* For lower latency: Gemini 2.5 Flash, Gemini 2.5 Flash-Lite
 * For complex reasoning: Gemini 3 Pro (Deep Think capabilities)
-|=== 
+|===
 
-Agent network supports text-based prompts and responses. Image and binary message types aren't supported.
+Agent networks support text-based prompts and responses. Image and binary message types aren't supported.
 
 [[a2a-protocol]]
-== A2A Protocol 
+== A2A Protocol
 
 The Agent2Agent (A2A) Protocol governs agent-to-agent communication. This protocol powers orchestration, observability, and governance features in agent networks. MuleSoft supports v0.3.0 of the A2A Protocol Specification.
 
 === Context and Task ID Scoping in Agent Networks
 
 In MuleSoft agent networks, the brokers receiving a request always generate a `contextId` and `taskId`. These IDs define the state and scope of a specific conversation between two agents. A `taskId` is always matched to a `contextId`, but a `contextId` can exist without a `taskId`.
 
-In a multi-agent network, a client sends a request to Broker_1 and Broker_1 generates the necessary IDs for that request. When Broker_1 sends a new request to the next broker or non-broker agent in line, that broker or non-broker agent establishes a unique `contextID` and `taskID` for the new request. 
+In a multi-agent network, a client sends a request to Broker_1 and Broker_1 generates the necessary IDs for that request. When Broker_1 sends a new request to the next broker or non-broker agent in line, that broker or non-broker agent establishes a unique `contextId` and `taskId` for the new request.
 
 NOTE: It is not mandatory for non-broker agents to generate a `contextId` and `taskId` when receiving requests from a client.
 
 Consider a network with a client and two brokers (1 and 2).
 
 * The IDs used between the client and Broker_1 are independent of the IDs used between Broker_1 and Broker_2.
-* When Broker_1 delegates a task to Broker_2, Broker 2 (acting as a server) generates its own `contextId` and `taskId`.
-*  Broker_1 is responsible for maintaining a mapping between its own upstream `taskId` (used to respond to its client) and the downstream `taskId` it's tracking with Broker_2.
+* When Broker_1 delegates a task to Broker_2, Broker_2 (acting as a server) generates its own `contextId` and `taskId`.
+* Broker_1 is responsible for maintaining a mapping between its own upstream `taskId` (used to respond to its client) and the downstream `taskId` it's tracking with Broker_2.
 * If Broker_2 requires more information (if it returns `status: input-required`), it provides a `contextId` and `taskId` to Broker_1. Broker_1 uses these IDs to provide the requested input to Broker_2. The client never sees Broker_2's internal IDs.
 
 [cols="1,1,1", options="header"]
 |===
-| Relationship | Role |  Logic
-| Client -> Broker_1 | Broker_1 is server | Generates `contextID_1` and `taskID_1` for the client.
-| Agent A -> Broker_2 | Broker_2 is server | Generates `contextID_2` and `taskID_2` for Broker_1.
-| Network broker | Broker_1 | Broker_1 maps `contextID_1` and `taskID_1` to `contextID_2` and `taskID_2`.
+| Relationship | Role | Logic
+| Client -> Broker_1 | Broker_1 is server | Generates `contextId_1` and `taskId_1` for the client.
+| Agent A -> Broker_2 | Broker_2 is server | Generates `contextId_2` and `taskId_2` for Broker_1.
+| Network broker | Broker_1 | Broker_1 maps `contextId_1` and `taskId_1` to `contextId_2` and `taskId_2`.
 |===
 
 For more information, see https://a2a-protocol.org/v0.3.0/topics/life-of-a-task/#group-related-interactions[Life of a Task - Group Related Interactions].
 
-NOTE: Agent network doesn't support streaming with Server-Sent Events (SSE).
-
+NOTE: Agent networks don't support streaming with Server-Sent Events (SSE).
 
 == See Also