App Router: `proxy-nfc-traced` route redirect produces empty content

This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext main vs Next.js v16.2.6, 2026-05-22).

Problem

A page that should be reachable via a proxy/redirect ends up rendering empty content. Root cause is unclear from the error alone (Expected: "hello world" / Received: ""); likely related to middleware proxy rewrite or NFT-traced module loading not finding the target page module after the redirect.

Expected: "hello world" Received: ""

Estimated Impact

~1 test failures across the deploy suite.

Affected Test Suites

• test/e2e/app-dir/proxy-nfc-traced/proxy-nfc-traced.test.ts

Recommendation

1. Reproduce first in vinext's own test suite. Run the proxy-nfc-traced fixture and capture the underlying error or empty response.

2. Investigate NFT module tracing and proxy rewrites. The empty content likely means the production server cannot resolve the target page module after the rewrite. Add logging in the route dispatcher.

---

Part of #1328.