Import alias usage consistency

Mixed import styles — some files using @/components/ui/button, others using ../../../components/ui/button — are a direct maintainability tax. Relative imports break silently when a file moves; alias imports are path-independent and survive directory reorganization. ISO 25010 maintainability flags this as a modifiability defect: every refactor that moves a file must also audit every relative import pointing at it. AI-generated code produces this drift because each session tends to copy the import style from whatever file it last read, producing a codebase where convention depends on which file the AI happened to open first.

Set alias imports as the standard and convert relative parent imports with a one-time codemod. The ESLint rule import/no-relative-parent-imports prevents backsliding.

// Bad: breaks if src/features/auth/LoginForm.tsx moves
import { Button } from '../../../components/ui/button'

// Good: survives any directory reorganization
import { Button } from '@/components/ui/button'

Run npx @antfu/ni && npx tsr or sed -i to bulk-convert, then add to .eslintrc:

{ "rules": { "import/no-relative-parent-imports": "error" } }

Verify tsconfig.json has "paths": { "@/*": ["./src/*"] } and baseUrl set so the alias resolves correctly at build time.