## Summary
Restore `skipDeployment` and the early return in the shared Cache
Components error-test runner. The migration in #98154 replaced them with
a force-gate pragma, but the gate transformer only processes `.test.*`
files, so the pragma in `shared.util.ts` did not preserve the deployment
exclusion.
This is a temporary rollback to unblock deploy testing. Moving the test
definitions out of the helper and migrating them again will be evaluated
separately; this PR does not change the transformer or refactor the
tests.
## Verification
- Ran all 12 importing test files through Jest in deploy mode with
deployment setup mocked to throw before any fixture or deployment work.
Before the rollback, all 12 reached that guard and failed. After the
rollback, all 12 take the legacy exclusion path and no deployment setup
is attempted.
- `pnpm typescript --skipLibCheck` passes.
- Full type-check reports the existing nine Octokit dependency
declaration errors; no errors in the changed file.
<!-- NEXT_JS_LLM -->
## Summary
- migrate Cache Components, PPR, prefetching, prerendering,
revalidation, and SSG deployment exclusions to `@force-gate`
- remove the corresponding `skipDeployment` options and `skipped`
control flow while preserving each suite's rationale
This keeps caching-related exclusions together so their deployed
semantics can be reviewed by the same owners.
## Verification
- verified on the combined top-of-stack tree with `pnpm typescript`
- compared ordinary-mode collection before and after: all 4,670 existing
test names matched
- collected all 510 affected files in deploy mode: 4,578 skipped tests,
zero failures
<!-- NEXT_JS_LLM -->
See https://github.com/vercel/next.js/pull/95553 for an explanation of
why we want to split these up. TL;DR it makes CI faster and saves us
some money.
In CI we have to run tests at the suite/file granularity, so if a test
suite is too long it limits parallelism and if it has to be retried, we
have to retry the full suite.
Josh Story