chore: migrate to tailwind v4

frontend/AGENTS.md

@@ -5,11 +5,12 @@ Also follow the repository root guide at `../AGENTS.md`.
 
 ## 1) Stack
 
-- Package manager: `bun`
+- Package manager: `pnpm`
 - Framework: React + Vite
 - Data fetching: React Query
 - API generation: Orval
-- Linting: ESLint + Tailwind plugin
+- Styling: Tailwind CSS v4 (CSS-first config)
+- Linting: oxlint (config in `.oxlintrc.json`) + `oxlint-tailwindcss` for Tailwind rules
 - Formatting: Prettier
 
 ## 2) Conventions
@@ -20,14 +21,15 @@ Also follow the repository root guide at `../AGENTS.md`.
 - Avoid custom class names in JSX `className` values unless the Tailwind lint config already allows them.
 - For decorative icons in inputs or labels, disable hover styling via the icon component API rather than overriding it ad hoc.
 - Prefer `LoadingState` for result-area loading indicators; avoid early returns that unmount search/filter forms during fetches.
-- Use theme tokens from `tailwind.config.js` / `src/index.css` (`bg-surface`, `text-content`, `border-border`, `primary`, etc.) for new UI work instead of adding raw light/dark color pairs.
+- Use theme tokens defined in `src/index.css` `@theme` (`bg-surface`, `text-content`, `border-border`, `primary`, etc.) for new UI work instead of adding raw light/dark color pairs. There is no `tailwind.config.js` — Tailwind v4 config is CSS-first.
+- Semantic colors map to runtime CSS variables (`--color-x: rgb(var(--x))`) via `@theme inline`; light/dark values live in `:root` / `.dark` in `src/index.css`. Dark mode is class-based via `@custom-variant dark`, toggled by `ThemeProvider`.
 - Store frontend-only preferences in `src/utils/localSettings.ts` so appearance and view settings share one local-storage shape.
 
 ## 3) Generated API client
 
 - Do not edit `src/generated/**` directly.
 - Edit `../api/v1/openapi.yaml` and regenerate instead.
-- Regenerate with: `bun run generate:api`
+- Regenerate with: `pnpm run generate:api`
 
 ### Important behavior
 
@@ -43,25 +45,27 @@ Also follow the repository root guide at `../AGENTS.md`.
 
 ## 5) Commands
 
-- Lint: `bun run lint`
-- Typecheck: `bun run typecheck`
-- Lint fix: `bun run lint:fix`
-- Format check: `bun run format`
-- Format fix: `bun run format:fix`
-- Build: `bun run build`
-- Generate API client: `bun run generate:api`
+- Lint: `pnpm run lint`
+- Typecheck: `pnpm run typecheck`
+- Lint fix: `pnpm run lint:fix`
+- Format check: `pnpm run format`
+- Format fix: `pnpm run format:fix`
+- Build: `pnpm run build`
+- Generate API client: `pnpm run generate:api`
 
 ## 6) Validation Notes
 
-- ESLint ignores `src/generated/**`.
+- oxlint ignores `src/generated/**` and `dist/**` (via `ignorePatterns` in `.oxlintrc.json`).
+- `lint` runs `oxlint --max-warnings=0`; keep the tree warning-free. `react-hooks/exhaustive-deps` is enforced — fix deps rather than disabling the rule; use a justified inline `// oxlint-disable-next-line` only for genuine init-once effects.
+- The Tailwind lint plugin uses oxlint `jsPlugins` (experimental, not run by the editor language server), so Tailwind diagnostics surface via CLI/CI, not in-editor. It reads the theme from `src/index.css` (`settings.tailwindcss.entryPoint`).
 - Frontend unit tests use Vitest and live alongside source as `src/**/*.test.ts(x)`.
 - Read `TESTING_STRATEGY.md` before adding or expanding frontend tests.
 - Prefer tests for meaningful app behavior, branching logic, side effects, and user-visible outcomes.
 - Avoid low-value tests that mainly assert exact styling classes, duplicate existing coverage, or re-test framework/library behavior.
-- `bun run lint` includes test files but does not typecheck.
-- Use `bun run typecheck` to run TypeScript validation for app code and colocated tests without a full production build.
-- Run frontend tests with `bun run test`.
-- `bun run build` still runs `tsc && vite build`, so unrelated TypeScript issues elsewhere in `src/` can fail the build.
+- `pnpm run lint` includes test files but does not typecheck.
+- Use `pnpm run typecheck` to run TypeScript validation for app code and colocated tests without a full production build.
+- Run frontend tests with `pnpm run test`.
+- `pnpm run build` still runs `tsc && vite build`, so unrelated TypeScript issues elsewhere in `src/` can fail the build.
 - When possible, validate changed files directly before escalating to full-project fixes.
 
 ## 7) Live Dev Server Debugging