test: migrate runtime deploy exclusions to force gates (#98159)
## Summary
Migrate the remaining runtime, middleware, instrumentation, telemetry,
logging, and local-process deployment exclusions to `@force-gate` and
remove their `skipDeployment`/`skipped` control flow. This stack is
rooted at canary and independent of #98430; it preserves deployment
coverage already enabled on canary.
The sub-shell-generation-middleware migration is deferred to #98155
while its adapter deployment cache-upgrade failure is investigated. Its
test file stays byte-for-byte identical to this PR's base, preserving
the existing adapter exception and assertions.
Adds the static nodeMiddleware condition and its unit coverage. The
custom-server and OpenTelemetry files covered by #98994 are omitted.
## Verification
- Compared test registration against canary in development, production,
and deploy modes with test bodies and hooks disabled (Webpack). Existing
active deployment assertions are preserved; development/production test
selection is unchanged apart from replacing empty skip placeholders with
skipped real tests.
- Gate unit tests: 79 passed.
- TypeScript, Prettier, and ESLint checks passed. Registration probes
use a default config for lazy predicates and do not exercise fixture
setup or test bodies.
- Verified the deferred suite is absent from this PR diff and the
upper-layer patches are unchanged. Full bootstrap passed on the combined
canary-based stack after the final restack; deployment execution remains
for CI.
<!-- NEXT_JS_LLM -->
---------
Co-authored-by:
Jamiboy Mohammad <jamiboym@gmail.com>
Showing
Please
register
or
sign in
to comment