Update DO isolation docs: ctx.exports works without binding, add verification guide

Author: yomna-shousha

src/assets/images/workers/previews/do-isolation-v2.svg

@@ -0,0 +1,40 @@
+---
+title: Domain management just got easier — do it from your Worker, without leaving your Worker
+description: A new Domains tab in the Cloudflare dashboard lets you purchase a new domain or add an existing one and connect it to your Worker, alongside everything else you need to manage routing.
+products:
+  - workers
+date: 2026-05-12
+---
+
+import { DashButton } from "~/components";
+
+The new **Domains** tab in your Worker's dashboard brings every routing surface into one place — and for the first time, lets you [purchase a new domain](/registrar/) through Cloudflare Registrar and automatically connect it to the Worker you bought it for.
+
+{/* TODO: add screenshot at ~/assets/images/workers/changelog/domains-tab.png */}
+{/* ![Screenshot of the new Domains tab in the Workers dashboard](~/assets/images/workers/changelog/domains-tab.png) */}
+
+## Two paths to a custom domain
+
+**Need a new one?** Click **Purchase Domain** to register a domain through [Cloudflare Registrar](/registrar/) without leaving your Worker. When the purchase completes, the domain is connected to the Worker automatically — no copying hostnames between products, no separate DNS step.
+
+**Already own a domain?** Click **Connect Domain** to attach an existing zone on your account. The same flow supports both [custom domains](/workers/configuration/routing/custom-domains/) and [route patterns](/workers/configuration/routing/routes/), so you can pick the routing model that fits your Worker.
+
+## Everything else routing-related, in one tab
+
+The Domains tab is also the new home for the rest of your Worker's routing configuration, so you don't have to dig through Settings:
+
+- [Custom domains](/workers/configuration/routing/custom-domains/) and [routes](/workers/configuration/routing/routes/)
+- Your [`workers.dev`](/workers/configuration/routing/workers-dev/) subdomain
+- [Preview URLs](/workers/configuration/previews/)
+- [Cloudflare Access](/cloudflare-one/access-controls/) controls for securing each route
+
+## Try it out
+
+1. In the Cloudflare dashboard, go to **Workers & Pages**.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select a Worker.
+3. Open the new **Domains** tab.
+
+For more on routing options for Workers, refer to [Routing](/workers/configuration/routing/).

src/assets/images/workers/previews/do-isolation-v3.svg

@@ -97,7 +97,7 @@ Concretely, this means:
 
 This isolation applies only when the class is defined in the same Worker. If you set `script_name` on a Durable Object or Workflow binding, the binding points at another Worker's production instance and this isolation does not apply.
 
-For Durable Objects and Workflows defined in the same Worker, you can also access them via [`ctx.exports`](/workers/runtime-apis/context/#exports), but the binding must still be declared in the `previews` block or dashboard defaults. Refer to [Durable Object isolation](/workers/previews/guides/durable-object-isolation/) for a full walkthrough.
+For Durable Objects and Workflows defined in the same Worker, you can also access them via [`ctx.exports`](/workers/runtime-apis/context/#exports) without declaring a binding — isolation works with just the migration. If you prefer the `env` binding pattern, declare the binding in the `previews` block or dashboard defaults. Refer to [Durable Object isolation](/workers/previews/guides/durable-object-isolation/) for a full walkthrough.
 
 ### Shared across Previews