The filter used `/^v2[2-9]/.test(process.version)`, which only matches
Node v22–v29 and silently skips the case on Node 30 and later. Replace
it with a numeric `major >= 22` check, matching the sibling
`json-import-attributes` filter for the same `with` syntax.

`isColorSupported()` probed the environment with the `in` operator
(`"FORCE_COLOR" in env`, `"CI" in env`, …). Deno's and Bun's
`process.env` shims honor property access but not the `in`/`has` trap,
so those signals were missed and the CLI emitted no colors. Read the
values directly instead — identical on Node, and works on Deno and Bun.

With detection fixed, the "colors by default" test no longer needs a
runtime skip on Deno and Bun.

The malformed-JSON tests asserted V8's exact SyntaxError wording and
positions, so they were skipped on Bun (JavaScriptCore emits different
text). Assert the exact wording only on V8 (Node, Deno) and check the
engine-agnostic JSONParseError contract (name, systemError, numeric
position, non-empty message) on every runtime, and drop the Bun skip.

Both were skipped on Bun for engine-specific error text: MultiItemCache
asserted V8's exact "not a function" TypeError wording, and
AbstractMethodError asserted a caller name parsed out of V8's
Error.stack format. Assert the engine-agnostic contract instead — the
error type for MultiItemCache, and the base message on Bun with the
exact caller-info message kept on V8 (Node, Deno) — and drop the skips.

Add cases for `--color` and `--no-color` in process.argv, the two
branches of the color detection that no test exercised.

The parser handler ran `require("../../package.json")` lazily, so the
async resolver-cache tail could trigger it after a test tore down the
module registry (the "require after environment torn down" crash that
forced HotTestCases to be skipped on Deno). Load the version once at
module scope, like DefaultStatsFactoryPlugin already does.

With the import.meta version require hoisted out of the parser handler,
the async resolver-cache tail no longer requires a module after Jest
teardown, so the HotTestCases suites can run on Deno again. Drop them
from the Deno job's ignore list.

GitHub Actions always sets `GITHUB_ACTIONS`, which short-circuits the
`isCI` OR before the GITLAB_CI/CIRCLECI checks, so those branches were
never executed (or covered) in CI. Clear the CI provider vars in
beforeEach so each provider test exercises its own branch.

Drop the engine-dependent stack field from Errors.test.js snapshots (JSC
renders Error.prototype.stack non-deterministically) and canonicalize the
JSON.parse SyntaxError wording, so the suite runs on Bun without skips.

Remove the now-dead Bun branch from the issue-11673 filter (the minimize+eval
combo never occurs in the test matrix) and the lazy-compilation/https filter
(the case passes on Bun).

The case-insensitive-filesystem branch is skipped on Linux, so the -u that
regenerated the other snapshots left its stack line in place; remove it to
match cleanError dropping stack on macOS/Windows.

…f skipping Bun

Under load the dynamic import's HTTPS activation request can reach the
lazy-compilation backend after the first manual recompile, leaving the module
a proxy so the rebuild reports "No update available" (seen on Bun async-node).
The fixed 1000ms NEXT_DEFERRED delay only narrows the race. Add a NEXT_RETRY
helper that re-runs the same fake-update version, and retry the activation
update until it lands. Verified by injecting a backend activation delay: the
old test fails, the retrying one passes. Drops the Bun skip.

With Bun running the full suite (via --smol), this case still reports "No
update available" even after retrying the recompile: Bun never processes the
activation request to the lazy-compilation HTTPS backend, so retries can't
recover it. Restore the Bun-only skip; the retry still hardens Node/Deno.