test: migrate asset deploy exclusions to force gates (#98158)
## Summary
Migrate the remaining image, font, CSS, and other asset integration
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.
Shared image-optimizer exclusions are placed on the calling test suites
because gate pragmas are transformed only in test files. Existing
bundler guards in the shared helper are preserved.
## Verification
- Compared test registration against canary in development, production,
and deploy modes with test bodies and hooks disabled. Existing active
deployment assertions are preserved; development/production test
selection is unchanged apart from replacing empty skip placeholders with
skipped real tests. Checked both Webpack and Turbopack.
- TypeScript, Prettier, and ESLint checks passed. Registration probes
use a default config for lazy predicates and do not exercise fixture
setup or test bodies.
- Full bootstrap attempted, but the local native SWC build fails at
`cargo metadata` with `EPERM`; full integration/deployment execution
remains for CI.
<!-- NEXT_JS_LLM -->
---------
Co-authored-by:
Jamiboy Mohammad <jamiboym@gmail.com>
Showing
This diff is collapsed.
Please
register
or
sign in
to comment