Document Next.js proxy matcher exclusion instructions

Author: TooTallNate

docs/content/docs/getting-started/next.mdx

@@ -201,7 +201,40 @@ Workflows can be triggered from API routes, Server Actions, or any server-side c
 
 <Step>
 
-## Run in Development
+## Configure Proxy Handler (if applicable)
+
+If your Next.js app has a [proxy handler](https://nextjs.org/docs/app/api-reference/file-conventions/proxy)
+(formerly known as "middleware"), you'll need to update the matcher pattern to exclude Workflow's
+internal paths to prevent the proxy handler from running on them.
+
+Add `.well-known/workflow/*` to your middleware's exclusion list:
+
+```typescript title="proxy.ts" lineNumbers
+import { NextResponse } from 'next/server';
+import type { NextRequest } from 'next/server';
+
+export function proxy(request: NextRequest) {
+  // Your middleware logic
+  return NextResponse.next();
+}
+
+export const config = {
+  matcher: [
+    // ... your existing matchers
+    {
+      source: '/((?!_next/static|_next/image|favicon.ico|.well-known/workflow/.*)', // [!code highlight]
+    },
+  ],
+};
+```
+
+This ensures that internal Workflow paths are not intercepted by your middleware, which could interfere with workflow execution and resumption.
+
+</Step>
+
+</Steps>
+
+## Run in development
 
 To start your development server, run the following command in your terminal in the Next.js root directory:
 
@@ -224,10 +257,6 @@ npx workflow inspect runs
 # or add '--web' for an interactive Web based UI
 ```
 
-</Step>
-
-</Steps>
-
 ---
 
 ## Deploying to production

docs/content/docs/getting-started/nitro.mdx

@@ -196,7 +196,7 @@ This Route Handler creates a `POST` request endpoint at `/api/signup` that will
 
 <Step>
 
-## Run in Development
+## Run in development
 
 To start your development server, run the following command in your terminal in the Nitro root directory: