Import organization is consistent

Inconsistent import ordering is a low-stakes signal with a real cost: it generates unnecessary merge conflicts when two developers touch the same file, and it slows down code review because readers must mentally parse which dependencies are third-party versus internal. ISO 25010 maintainability.analysability degrades when every file has a different ordering convention. Projects assembled across multiple AI sessions are especially prone to this because each session may apply a different implicit convention.

Let tooling enforce ordering automatically so no human has to think about it. Add the import/order rule to your ESLint config:

"import/order": ["warn", {
  "groups": ["builtin", "external", "internal", "parent", "sibling", "index"]
}]

Alternatively, configure @trivago/prettier-plugin-sort-imports. Run once across the codebase to reformat all existing files, then every future file auto-conforms on save.