fix: production stabilization (middleware routing + docker paths)

apps/web/src/middleware.ts

@@ -0,0 +1,53 @@
+import { NextResponse } from 'next/server';
+import type { NextRequest } from 'next/server';
+
+/**
+ * PRODUCTION STABILIZATION MIDDLEWARE
+ * This middleware handles legacy asset routing for the KLZ showcase,
+ * ensuring assets are correctly mapped regardless of Next.js config wrapper behavior.
+ */
+export function middleware(request: NextRequest) {
+  const { pathname } = request.nextUrl;
+
+  // 1. Diagnostic Rewrite
+  if (pathname === '/robots-test') {
+    return NextResponse.rewrite(new URL('/robots.txt', request.url));
+  }
+
+  // 2. Legacy Showcase Asset Mapping
+  // Matches: /wp-content/*, /wp-includes/*, /assets/*, and their relative subpaths
+  const showcaseAssetPattern = /^\/(?:wp-content|wp-includes|assets|(?:case-studies|work|blog)\/(?:wp-content|wp-includes|assets))\/(.*)/;
+  const match = pathname.match(showcaseAssetPattern);
+
+  if (match) {
+    const assetPath = match[0];
+    
+    // Normalize path by stripping the case-studies/work/blog prefix if present
+    const normalizedPath = assetPath.replace(/^\/(?:case-studies|work|blog)/, '');
+    
+    // Map to the literal directory in public/
+    // Destination: /showcase/klz-cables.com/...
+    return NextResponse.rewrite(new URL(`/showcase/klz-cables.com${normalizedPath}`, request.url));
+  }
+
+  return NextResponse.next();
+}
+
+// Optimization: Only run middleware for legacy asset paths to minimize overhead
+export const config = {
+  matcher: [
+    '/robots-test',
+    '/wp-content/:path*',
+    '/wp-includes/:path*',
+    '/assets/:path*',
+    '/case-studies/wp-content/:path*',
+    '/case-studies/wp-includes/:path*',
+    '/case-studies/assets/:path*',
+    '/work/wp-content/:path*',
+    '/work/wp-includes/:path*',
+    '/work/assets/:path*',
+    '/blog/wp-content/:path*',
+    '/blog/wp-includes/:path*',
+    '/blog/assets/:path*',
+  ],
+};