chore(deploy): remove a2a

Author: icecrasher321

apps/docs/components/icons.tsx

@@ -5730,31 +5730,6 @@ export function McpIcon(props: SVGProps<SVGSVGElement>) {
   )
 }
 
-export function A2AIcon(props: SVGProps<SVGSVGElement>) {
-  return (
-    <svg {...props} viewBox='0 0 860 860' fill='none' xmlns='http://www.w3.org/2000/svg'>
-      <circle cx='544' cy='307' r='27' fill='currentColor' />
-      <circle cx='154' cy='307' r='27' fill='currentColor' />
-      <circle cx='706' cy='307' r='27' fill='currentColor' />
-      <circle cx='316' cy='307' r='27' fill='currentColor' />
-      <path
-        d='M336.5 191H162C97.66 191 45.5 243.16 45.5 307.5C45.5 371.84 97.64 424 161.99 424C206.55 424 256.29 424 296.5 424C487.5 424 374 191.01 569 191C613.89 191 658.97 191 698.03 191C762.37 191 814.5 243.16 814.5 307.5C814.5 371.84 762.34 424 698 424H523.5'
-        stroke='currentColor'
-        strokeWidth='48'
-        strokeLinecap='round'
-      />
-      <path
-        d='M256 510C270.36 510 282 521.64 282 536C282 550.36 270.36 562 256 562H148C133.64 562 122 550.36 122 536C122 521.64 133.64 510 148 510H256ZM712 510C726.36 510 738 521.64 738 536C738 550.36 726.36 562 712 562H360C345.64 562 334 550.36 334 536C334 521.64 345.64 510 360 510H712Z'
-        fill='currentColor'
-      />
-      <path
-        d='M444 628C458.36 628 470 639.64 470 654C470 668.36 458.36 680 444 680H100C85.64 680 74 668.36 74 654C74 639.64 85.64 628 100 628H444ZM548 628C562.36 628 574 639.64 574 654C574 668.36 562.36 680 548 680C533.64 680 522 668.36 522 654C522 639.64 533.64 628 548 628ZM760 628C774.36 628 786 639.64 786 654C786 668.36 774.36 680 760 680H652C637.64 680 626 668.36 626 654C626 639.64 637.64 628 652 628H760Z'
-        fill='currentColor'
-      />
-    </svg>
-  )
-}
-
 export function WordpressIcon(props: SVGProps<SVGSVGElement>) {
   return (
     <svg {...props} xmlns='http://www.w3.org/2000/svg' viewBox='0 0 25.93 25.93'>

apps/docs/content/docs/de/tools/a2a.mdx

@@ -29,7 +29,7 @@ Query workflow run logs in the current workspace with the full Logs-page filter
 | `workflowIds` | string | No | Comma-separated workflow IDs to filter by |
 | `folderIds` | string | No | Comma-separated folder IDs to filter by \(descendants included\) |
 | `level` | string | No | Comma-separated statuses: 'info', 'error', 'running', 'pending', 'cancelled'. Omit for all. |
-| `triggers` | string | No | Comma-separated trigger types \(api, webhook, schedule, manual, chat, mcp, a2a, workflow, sim, …\) |
+| `triggers` | string | No | Comma-separated trigger types \(api, webhook, schedule, manual, chat, mcp, workflow, sim, …\) |
 | `startDate` | string | No | ISO 8601 timestamp; only runs at or after this time |
 | `endDate` | string | No | ISO 8601 timestamp; only runs at or before this time |
 | `search` | string | No | Free-text search across log fields |

apps/docs/content/docs/en/integrations/logs.mdx

@@ -24,7 +24,7 @@ The **Logs page** lists every run across your workspace, one row per run. The [L
 
 ### The run
 
-Each row on the Logs page is one **run**. It records the **trigger** that started it (manual, api, schedule, chat, webhook, mcp, mothership, copilot, workflow, or a2a), a **status**, a **duration**, and the **cost** in credits. It also carries an **execution ID** that uniquely names the run.
+Each row on the Logs page is one **run**. It records the **trigger** that started it (manual, api, schedule, chat, webhook, mcp, mothership, copilot, or workflow), a **status**, a **duration**, and the **cost** in credits. It also carries an **execution ID** that uniquely names the run.
 
 The status shows the run's outcome at a glance, with failed runs badged **Error**. When you are hunting a failure, you filter the list to the errors and start there.
 

apps/docs/content/docs/en/logs-debugging/index.mdx

@@ -64,7 +64,7 @@ Controls which AI model providers members of this group can use.
 
 Controls which workflow blocks members can place and execute.
 
-<Image src="/static/enterprise/access-control-blocks.png" alt="Blocks tab showing Core Blocks (Agent, API, Condition, Function, Knowledge, etc.) and Tools (integrations like 1Password, A2A, Ahrefs, Airtable, and more) with checkboxes to allow or restrict each" width={900} height={500} /> Blocks are split into two sections: **Core Blocks** (Agent, API, Condition, Function, etc.) and **Tools** (all integration blocks).
+<Image src="/static/enterprise/access-control-blocks.png" alt="Blocks tab showing Core Blocks (Agent, API, Condition, Function, Knowledge, etc.) and Tools (integrations like 1Password, Ahrefs, Airtable, and more) with checkboxes to allow or restrict each" width={900} height={500} /> Blocks are split into two sections: **Core Blocks** (Agent, API, Condition, Function, etc.) and **Tools** (all integration blocks).
 
 - **All checked (default):** All blocks are allowed.
 - **Subset checked:** Only the selected blocks are allowed. Workflows that already contain a disallowed block will fail when run — they are not automatically modified.
@@ -116,7 +116,6 @@ Controls visibility of platform features and modules.
 |---------|-------------------|
 | API | Hides the API deployment tab |
 | MCP | Hides the MCP deployment tab |
-| A2A | Hides the A2A deployment tab |
 | Chat | Hides the Chat deployment tab |
 | Template | Hides the Template deployment tab |
 

apps/docs/content/docs/en/platform/enterprise/access-control.mdx

@@ -7,7 +7,7 @@ pageType: concept
 import { Callout } from 'fumadocs-ui/components/callout'
 import { Card, Cards } from 'fumadocs-ui/components/card'
 
-A deployment is a published version of a [workflow](/workflows) that outside callers can run. While you build, a workflow lives on your canvas as a draft only you can run. Deploying publishes a fixed copy of that draft and gives it an address: a REST endpoint, a chat page, a set of [MCP](/workflows/deployment/mcp) tools, or an [A2A](/workflows/deployment/api) agent. Each is a **surface**, a channel callers reach the same published workflow through.
+A deployment is a published version of a [workflow](/workflows) that outside callers can run. While you build, a workflow lives on your canvas as a draft only you can run. Deploying publishes a fixed copy of that draft and gives it an address: a REST endpoint, a chat page, or a set of [MCP](/workflows/deployment/mcp) tools. Each is a **surface**, a channel callers reach the same published workflow through.
 
 Like publishing a book, building and deploying are separate acts. You draft and revise freely on the canvas. When you click **Deploy**, Sim prints a fixed edition. Readers get that edition, not your latest draft, until you publish a new one. You can always go back to an earlier printing.
 
@@ -60,13 +60,12 @@ curl -X POST https://sim.ai/api/workflows/{workflow-id}/execute \
   -d '{ "input": "Refund request from customer #4821" }'
 ```
 
-{/* VISUAL: deploy modal tab bar. General · API · MCP · A2A · Chat. */}
+{/* VISUAL: deploy modal tab bar. General · API · MCP · Chat. */}
 
 <Cards>
   <Card title="API" href="/workflows/deployment/api" description="A REST endpoint any application can call, with sync, streaming, and async modes." />
   <Card title="Chat" href="/workflows/deployment/chat" description="A shareable conversational page that keeps conversation history." />
   <Card title="MCP" href="/workflows/deployment/mcp" description="Expose the workflow as tools an external AI assistant can call." />
-  <Card title="A2A" href="/workflows/deployment/api" description="Let other AI agents discover and call the workflow as a tool." />
 </Cards>
 
 ## Versioning in practice