☂️ `useReactCompiler` remaining work

[dyc3]

Description

Failing test cases from upstream that need to be evaluated:

# --- Biome matches Babel's canonical output; the OXC oracle under-reports ---
# Biome emits exactly the error the fixture's own .expect.md documents; OXC
# misses it (loses the local-vs-context / optional-chaining-dependency
# distinction). These are oracle limitations, not Biome bugs.
error.bug-invariant-local-or-context-references.js
preserve-memo-validation/error.useCallback-conditional-access-noAlloc.ts

# --- Documented React Compiler Rust-port frontier (backend, not Biome) ---
# Minified CommonJS prod code; the fixture header documents a known
# PromoteUsedTemporaries divergence in the Rust port itself.
todo-round3_promote_used_temps.js

# --- Deep edge cases on `error.` fixtures; both frontends still flag an error ---
# default-param-accesses-local: Biome compiles where Babel/OXC bail with a
#   reorderability Todo on an arrow-valued default parameter.
# invalid-hook-optional-property: Biome flags a Hooks violation but with a
#   different reason than the conditional-call wording (optional-chained hook).
# invalid-unclosed-eslint-suppression: multi-error fixture; the two frontends
#   surface overlapping-but-different secondary errors (both report VoidUseMemo).
error.default-param-accesses-local.js
rules-of-hooks/error.invalid-hook-optional-property.js
error.invalid-unclosed-eslint-suppression.js

• Address prefiltering heuristics problems feat(lint/js): add useReactCompiler #10710 (comment)
• Consider splitting it into multiple rules

Requires forking:

• Remove brittle string comparisons for the diagnostics we emit.
• Skip converting Biome CST -> Babel AST -> React Compiler HIR, just go straight from Biome CST -> HIR

[github-actions]

✅ Organic activity

No automation signals detected in the analyzed events.

View full analysis →

_{This is an automated analysis by AgentScan}

[lixiaoyan]

It would be even better if they could be split into separate rules. Many of the rules provided by the React Compiler are also useful in projects that don't have the React Compiler enabled. For a lot of these rules, the React Compiler is more of an implementation detail — or to put it another way, they're stricter rules motivated by enabling the React Compiler, but not exclusively for it.

Splitting them into individual rules would also make it easier to disable a single rule via biome-ignore, rather than having to disable everything backed by the React Compiler at once. I suspect this is also why the official ESLint plugin splits them into multiple rules and doesn't include "compiler" in most of the rule names.