Balancing Global Warning Enforcement vs. Silent CI Passes in ESLint

The goal is to set a CI gate that blocks new warning‑level issues while preventing unnecessary merge rejections from existing warnings.

Using `--max-warnings=0` forces a non‑zero exit code on any warning, which is strict but requires a clean baseline before enabling; `--quiet` hides all warnings and keeps the exit code zero, allowing merges but masking emerging issues.

Because the CLI flags apply globally and cannot limit warnings to changed files, teams must decide whether to enforce strict gating after baseline cleanup or use silent mode together with external diff‑aware tooling, and whether native diff‑scoped warning handling exists.

Should the CI configuration adopt `--max-warnings=0` after baseline cleanup, or combine `--quiet` with external diff‑aware tooling? Is there a supported way to scope warning thresholds to changed files in ESLint 9, or must additional plugins be used?