next.js

b0e1bf79 - test: document deploy exclusions for suites that need a local server (#100483)

test: document deploy exclusions for suites that need a local server (#100483) ## Summary Replaces 5 `TODO(deploy-test-completion)` markers with the concrete reason the suite can't run against any deployment. The `@force-gate !deploy` lines stay. - **`custom-routes`** (main suite, "no-op rewrite", "solo types") and **`i18n-support-base-path`**: `beforeAll` starts an HTTP server on a port on the test runner and patches that port into `next.config.js`, which a deployment can't reach. In the Sept 24 deploy run every test in both suites failed on that setup. - **`rewrites-hostname`**: rewrites to a server on a local port (`你好.localhost:<port>`) and asserts localhost host headers. The deployment returned its error page. These need the test runner's own network, so they can't pass on any deploy host. Other `TODO(deploy-test-completion)` suites that fail on Vercel for fixable reasons keep their TODOs and will be enabled separately. ## Verification - Checked each reason against the failing assertions in the experiment logs and the test code. - Comment-only change. <!-- NEXT_JS_LLM -->