Root cause: eslint v10

  The chain:

  1. The CircleCI install-deps command always runs with package-overrides: react@<version>
  (.circleci/config.yml:80-81). For the React-18 job that's react@^18.
  2. That invokes code-infra's set-version-overrides. Looking at its source
  (cmdSetVersionOverrides.mjs:106-112), for a non-stable version it writes the React pins into
  package.json's resolutions field and then runs pnpm dedupe.
  3. pnpm dedupe is a full, non-frozen re-resolution of the whole graph (unlike the normal jobs, which
  install from the frozen lockfile). During that re-resolve, every version range is re-evaluated to
  its highest match.
  4. @mui/internal-code-infra declares "eslint": "^9.0.0 || ^10.0.0" (I confirmed this in the
  installed package manifest). eslint 10.5.0 was published, so the re-resolve now picks 10.5.0 instead
  of the locked 9.39.2.
  5. But code-infra's bundled lint plugins only support eslint ≤9 — [email protected],
  [email protected], [email protected] (exactly the versions in your error).
  eslint 10 makes the graph unsatisfiable, and pnpm dedupe exits 1.

  - Stable jobs are fine: set-version-overrides with react@stable returns empty overrides and skips
  pnpm dedupe entirely (cmdSetVersionOverrides.mjs:33-35, 97-100), so they install frozen → eslint
  stays 9.39.2.
  - Only the override jobs (react@^18, use-material-ui-v6, use-material-ui-next) run the dedupe → only
  they float eslint to 10.

  Fix

  The real bug is upstream: code-infra's eslint: "^9.0.0 || ^10.0.0" range is wrong while its plugins
  cap at eslint 9. That should be reported/fixed in mui-public (@mui/internal-code-infra) — either cap
  eslint to ^9 or bump the plugins to eslint-10-compatible versions.