Fix: Properly disable middleware to resolve MIDDLEWARE_INVOCATION_FAILED

- Replaced commented middleware with empty export to disable it completely
- Cleared .next build cache to remove stale middleware compilation
- Root cause: Next.js was still compiling and invoking commented middleware

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: vadim-vozmitsel-cascaide

src/middleware.ts

@@ -1,13 +1,6 @@
-// Middleware temporarily disabled for debugging
-// import { NextResponse } from 'next/server';
-// import type { NextRequest } from 'next/server';
+// This file is intentionally empty to disable middleware
+// Removing this file entirely or commenting it out doesn't work
+// because Next.js still tries to compile it if it exists.
+// This empty export prevents middleware from running.
 
-// export function middleware(request: NextRequest) {
-//   return NextResponse.next();
-// }
-
-// export const config = {
-//   matcher: [
-//     '/api/:path*'
-//   ],
-// };
+export {};