Why

This is the third step of the ESLint-to-Oxlint migration. After establishing native Oxlint parity in CI, this layer makes Oxlint authoritative for migrated rules and leaves ESLint responsible only for compatibility gaps.

What changed

• derive an ESLint disable layer from enabled rules in oxlint.json, avoiding duplicated checks and rule drift
• map Oxlint TypeScript, import, and Node plugin names back to their ESLint equivalents
• retain ESLint checks that Oxlint cannot yet replace, including Nx boundaries, local CLI rules, import ordering, naming conventions, and unsupported JSDoc/TSDoc rules
• label ESLint explicitly as a compatibility check in scripts, CI, and contributor documentation
• run Oxlint fixes before ESLint compatibility fixes
• preserve the full ESLint autofix configuration used to make generated GraphQL output deterministic
• suppress ESLint unused-disable reporting because directives can now target rules owned by Oxlint

Validation

• pnpm lint:eslint --output-style=static
• pnpm lint
• pnpm graphql-codegen with no generated-file changes
• verified representative ESLint effective config disables Oxlint-owned rules while retaining compatibility rules
• git diff --check

The compatibility-only ESLint pass decreased locally from approximately 19.8 seconds to 16.2 seconds; plugin and parser startup now dominate its remaining runtime.