docs: update the reference topology diagram to the latest export

Swaps in the new export, which adds the diagram title and a key marking
the tool calling hot path and the arcade deploy path.

The file is JPEG data despite the .png name it arrived with, so it lands
as .jpg rather than lying about its format. Re-encoding it to real PNG
was the other option, but that doubles the file to 3.8MB and recovers no
detail, since the JPEG artifacts are already baked in.

Intrinsic dimensions go to 7800x4280. Same aspect ratio as before, so
the layout is unchanged. The alt text picks up the application and
worker plane split and the key.

~ 🎹 Evanescence, Evan's Agent

Author: evantahler

app/en/operate/deploy/architecture/page.mdx

@@ -31,18 +31,18 @@ The diagram below shows a complete deployment: the Kubernetes clusters that run
 <figure className="my-6">
   <a
     className="group block cursor-zoom-in overflow-hidden rounded-xl border border-neutral-300 bg-white p-4 shadow-sm ring-1 ring-black/5 transition hover:border-neutral-400 hover:shadow-md md:p-6 dark:bg-neutral-300"
-    href="/images/architecture/arcade-reference-topology.png"
+    href="/images/architecture/arcade-reference-topology.jpg"
     rel="noopener"
     target="_blank"
     title="Open the full-size topology diagram"
   >
     <Image
-      alt="Arcade reference topology diagram: agents and tool developers reach the ingress gateway, which fronts the Kubernetes clusters running the Engine, Coordinator, Experience API, dashboard, and workers; egress gateways reach identity providers, telemetry, and connected services; PostgreSQL, Redis, and blob storage sit in the data tier below"
+      alt="Arcade reference topology diagram: agents and tool developers reach the ingress gateway, which fronts the application plane Kubernetes cluster running the Coordinator, Engine, Usage, dashboard, Experience API, embedding and search services, and OpenFGA, alongside a worker plane cluster running Arcade workers and custom MCP servers; egress gateways reach identity providers, telemetry, container registries, and connected services; PostgreSQL, Redis, and blob storage sit in the data tier below. A key marks the tool calling hot path and the arcade deploy path"
       className="h-auto w-full dark:brightness-[0.83]"
-      height={5362}
+      height={4280}
       sizes="(max-width: 768px) 100vw, 800px"
-      src="/images/architecture/arcade-reference-topology.png"
-      width={9772}
+      src="/images/architecture/arcade-reference-topology.jpg"
+      width={7800}
     />
   </a>
   <figcaption className="mt-3 text-center text-neutral-600 text-sm dark:text-neutral-400">