Next.js 16 Middleware: authorization patterns that scale and the ones that cause race conditions

I tested 4 authorization patterns in Next.js 16 Middleware with edge runtime. One causes silent race conditions, another gives you unexpected latency, and only one scales without compromises. Here's the honest tradeoff analysis of each.