Biome import organization creates diffs unrelated to formatting changes

Biome applies import organization as a pass separate from formatting, so a file can receive import reordering or removal without any layout change. The formatter enforces a fixed print width that defaults to 80 characters and does not mirror the full Prettier option set.

Because biome check runs lint and format validation together and exits non-zero on any violation, differences in biome.json or pinned releases between local and CI can produce intermittent failures.

Goal: isolate whether unexpected diffs come from independent import organization, formatter print-width behavior, or configuration drift across environments.

• Can Biome import organization generate a diff when the formatter makes no changes to a file?
• Which biome.json fields must match between local and CI to rule out configuration drift?
• Does pinning one Biome release remove formatter output differences observed across versions?