Adds draft docs for connecting to remote resources during local dev (hybrid dev)

public/__redirects

@@ -1527,6 +1527,11 @@
 /workers/about/tips/debugging/ /workers/observability/ 301
 /workers/testing/debugging-tools/ /workers/observability/dev-tools/ 301
 /workers/testing/local-development/ /workers/local-development/ 301
+/workers/local-development/ /workers/development-testing/#local-development 301
+/workers/local-development/bindings-per-env/ /workers/development-testing/bindings-per-env/ 301
+/workers/local-development/environment-variables/ /workers/development-testing/environment-variables/ 301
+/workers/local-development/local-data/ /workers/development-testing/local-data/ 301
+/workers/local-development/remote-data/ /workers/development-testing/#remote-bindings 301
 /workers/about/using-cache/ /workers/reference/how-the-cache-works/ 301
 /workers/learning/how-the-cache-works/ /workers/reference/how-the-cache-works/ 301
 /workers/api/ /api/resources/workers/subresources/scripts/methods/list/ 301

src/content/docs/cloudflare-for-platforms/workers-for-platforms/get-started/developing-with-wrangler.mdx

@@ -199,3 +199,25 @@ curl http://localhost:8600
 ```sh output
 # -> user worker got "intercepted a request for customer-1 by the outbound" from fetch
 ```
+
+## Remote dispatch namespaces
+
+You can configure dispatch namespace bindings to connect to remote dispatch namespaces during local development by setting [`experimental_remote = true`](/workers/development-testing/#remote-bindings):
+
+<WranglerConfig>
+```jsonc title="wrangler.jsonc"
+{
+  "dispatch_namespaces": [
+    {
+      "binding": "DISPATCH_NAMESPACE",
+      "namespace": "testing",
+      "experimental_remote": true
+		}
+  ]
+}
+```
+</WranglerConfig>
+
+This allows you to run your [dynamic dispatch Worker](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#dynamic-dispatch-worker) locally, while connecting it to your remote dispatch namespace binding. You can then test changes to your core dispatching logic against real, deployed [user Workers](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#user-workers).
+
+For more information about remote bindings during local development, refer to [remote bindings documentation](/workers/development-testing/#remote-bindings).

src/content/docs/d1/observability/debug-d1.mdx

@@ -94,4 +94,4 @@ You should include as much of the following in any bug report:
 
 * Learn [how to debug Workers](/workers/observability/).
 * Understand how to [access logs](/workers/observability/logs/) generated from your Worker and D1.
-* Use [`wrangler dev`](/workers/wrangler/commands/#dev) to run your Worker and D1 locally and [debug issues before deploying](/workers/local-development/).
+* Use [`wrangler dev`](/workers/wrangler/commands/#dev) to run your Worker and D1 locally and [debug issues before deploying](/workers/development-testing/).

src/content/docs/durable-objects/reference/environments.mdx

@@ -73,7 +73,7 @@ Local development sessions create a standalone, local-only environment that mirr
 
 An existing Durable Object binding of `DB` would be available to your Worker when running locally.
 
-Refer to Workers [Local development](/workers/local-development/#supported-resource-bindings-in-different-environments).
+Refer to Workers [Local development](/workers/development-testing/bindings-per-env/).
 
 ## Remote development
 

src/content/docs/pages/functions/bindings.mdx

@@ -201,7 +201,7 @@ You can interact with your R2 bucket bindings locally in one of two ways:
 
 :::note
 
-By default, Wrangler automatically persists data to local storage. For more information, refer to [Local development](/workers/local-development/).
+By default, Wrangler automatically persists data to local storage. For more information, refer to [Local development](/workers/development-testing/).
 
 :::
 
@@ -282,7 +282,7 @@ Interact with this binding by using `context.env` (for example, `context.env.NOR
 
 :::note
 
-By default, Wrangler automatically persists data to local storage. For more information, refer to [Local development](/workers/local-development/).
+By default, Wrangler automatically persists data to local storage. For more information, refer to [Local development](/workers/development-testing/).
 
 :::
 

src/content/docs/pages/functions/wrangler-configuration.mdx

@@ -433,7 +433,7 @@ A [binding](/pages/functions/bindings/) enables your Pages Functions to interact
 
 :::note
 
-When using Wrangler in the default local development mode, files will be written to local storage instead of the preview or production database. Refer to [Local development](/workers/local-development/) for more details.
+When using Wrangler in the default local development mode, files will be written to local storage instead of the preview or production database. Refer to [Local development](/workers/development-testing/) for more details.
 
 :::
 
@@ -475,7 +475,7 @@ Workers, the `script_name` key is optional.
 
 :::note
 
-When using Wrangler in the default local development mode, files will be written to local storage instead of the preview or production namespace. Refer to [Local development](/workers/local-development/) for more details.
+When using Wrangler in the default local development mode, files will be written to local storage instead of the preview or production namespace. Refer to [Local development](/workers/development-testing/) for more details.
 
 :::
 
@@ -501,7 +501,7 @@ You cannot currently configure a [queues consumer](/queues/reference/how-queues-
 
 :::note
 
-When using Wrangler in the default local development mode, files will be written to local storage instead of the preview or production bucket. Refer to [Local development](/workers/local-development/) for more details.
+When using Wrangler in the default local development mode, files will be written to local storage instead of the preview or production bucket. Refer to [Local development](/workers/development-testing/) for more details.
 
 :::
 

src/content/docs/workers/local-development/bindings-per-env.mdx → src/content/docs/workers/development-testing/bindings-per-env.mdx

@@ -1,10 +1,10 @@
 ---
 pcx_content_type: navigation
-title: Supported bindings in local and remote dev
+title: Supported bindings per development mode
 sidebar:
   order: 4
 head: []
-description: Supported bindings in local and remote development
+description: Supported bindings per development mode
 ---
 
 import { Render } from "~/components";