Formatter and Linter style ownership in Biome's shared configuration

When adopting Biome incrementally, teams must decide whether a particular style concern should be managed by the formatter or the linter. The formatter is intended to own layout‑related rules, while the linter focuses on correctness, but some linter rules can still overlap with formatter output, creating potential conflicts during migration.

The goal is to establish a clear ownership boundary that prevents lint rules from fighting formatter output while preserving the ability to enforce correctness checks. Constraints include the formatter’s design intent, the possibility of rule overlap in edge cases, and the need to coordinate ignores, overrides, and per‑language settings in a single biome.json file.

Which criteria should guide assigning a style rule to the formatter versus the linter? How can conflicting lint rules be suppressed or adjusted without disabling necessary correctness checks? What verification approach ensures that formatter and linter outputs remain compatible throughout the transition?