Merge pull request #616 from mulesoft/W-22034718-Run-super-agent-on-af---files

W-22034718 run super agent on af-*  files

Author: IsaacEldridge

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

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
 

modules/ROOT/pages/af-build-agent-networks-in-a-ci-cd-environment.adoc

@@ -1,18 +1,20 @@
 = Build Agent Networks in a CI/CD Environment
 
-If you run operations within a CI/CD environment, you can use Anypoint CLI's Agent Fabric plugin to set up, create, build, publish, and deploy agent networks. For more information, see link:https://www.npmjs.com/package/anypoint-cli-agent-fabric-plugin[Anypoint CLI Agent Fabric Plugin].
+Use the Anypoint CLI Agent Fabric plugin in CI/CD pipelines to configure agent network gateways, create and build projects, and publish and deploy networks from the command line, matching the lifecycle you can drive from Anypoint Code Builder. Automating these steps keeps environments aligned, lets you embed approvals, secrets, and quality gates in the pipeline, and avoids one-off scripts when you promote from development to staging and production.
+
+For installation, package updates, and release details, see https://www.npmjs.com/package/mulesoft-anypoint-cli-agent-fabric-plugin[Anypoint CLI Agent Fabric Plugin on npm].
 
 == Before You Begin
 
-Make sure you meet the prerequisites for this task. For prerequisites, see xref:af-get-started.adoc[].
+Make sure you meet the xref:af-get-started.adoc#before-you-begin[prerequisites] for this task.
 
 Install the Anypoint CLI Agent Fabric plugin by running this command in a terminal window:
 
 `npm i mulesoft-anypoint-cli-agent-fabric-plugin`
 
 [NOTE]
 ====
-The installation package has been renamed from `anypoint-cli-agent-fabric-plugin` to `mulesoft-anypoint-cli-agent-fabric-plugin`. 
+The installation package has been renamed from `anypoint-cli-agent-fabric-plugin` to `mulesoft-anypoint-cli-agent-fabric-plugin`.
 
 If you have the previous version installed, you may encounter an `npm error EXIST: file already exists` error when updating your installation. This occurs because both versions share the same command alias. To resolve this, use the `--force` flag to overwrite the alias and point it to the new package: `npm i mulesoft-anypoint-cli-agent-fabric-plugin --force`.
 ====
@@ -41,7 +43,7 @@ For more information, see xref:anypoint-cli::auth.adoc[].
 
 To deploy an agent network, you need a private space on CloudHub 2.0 or a deployment target on Anypoint Runtime Fabric. See xref:af-get-started.adoc#setup-space[Set Up the Private Space or Deployment Target for Your Environment].
 
-After you create a target space, and haven't already done so, set up the ingress and egress gateways for deployment. See xref:af-get-started.adoc#setup-gateways[Set Up Agent Network Gateways for the Private Space or Deployment Target].
+After you create a target space, set up the ingress and egress gateways for deployment if you haven't already done so. See xref:af-get-started.adoc#setup-gateways[Set Up Agent Network Gateways for the Private Space or Deployment Target].
 
 == CLI for Agent Fabric Plugin Reference
 

modules/ROOT/pages/af-create-agent-network.adoc

@@ -4,7 +4,7 @@
 Whether you want to use MuleSoft Vibes or the UI, Anypoint Code Builder includes all the agent network functionality you need to get started.
 
 [[before-you-begin]]
-== Before You Begin 
+== Before You Begin
 
 Make sure you review the xref:af-get-started.adoc#before-you-begin[prerequisites].
 
@@ -16,7 +16,7 @@ MuleSoft Vibes can help you create your project. For more information, see xref:
 . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18].
 . Describe your agent network, including the brokers, agents, MCP servers, and LLMs you want to connect. MuleSoft Vibes does the rest.
 
-To get started try one of these suggested prompts.
+To get started, try one of these suggested prompts.
 
 * Create a new agent network project called "Employee Onboarding." Add HR agent and CRM agent.
 * Build a travel planner broker that plans multi-city trips and generate a new agent network.
@@ -26,7 +26,7 @@ To get started try one of these suggested prompts.
 == Create a Network Using Anypoint Code Builder
 
 . If you're not logged in, log in to your Anypoint Platform account.
-. In Anypoint Code Builder choose on of the following:
+. In Anypoint Code Builder, choose one of the following:
   * In Create, select *Create an Agent Network*.
   * From the Command Palette, run this command: *MuleSoft: Create an Agent Network Project*.
 . Enter a name for the project and select the location to create the project.
@@ -40,7 +40,7 @@ Anypoint Code Builder creates these files as part of your agent network project.
 Specifies brokers, agents, MCP servers, LLMs, policies, and authentication in your agent network.
 * `exchange.json`
 +
-Specifies Anypoint Exchange assets that are referenced in your agent network, as well as the variables to use in your agent network. Each asset has an asset ID that you use in the agent-network.yaml file.
+Specifies Anypoint Exchange assets that are referenced in your agent network, as well as the variables to use in your agent network. Each asset has an asset ID that you use in the `agent-network.yaml` file.
 
 The canvas shows a visual, read-only representation of your YAML file. Select any component to show the associated code in the code editor.