Untrack the emitted vite config, and select biome's files by extension

vite.config.js and vite.config.d.ts are tsc output of vite.config.ts, emitted
next to the source when the composite tsconfig.node.json is built. Nothing
reads them — and vite picks a vite.config.js ahead of the .ts, so the committed
copy was quietly shadowing the real config. Gitignore both.

The biome hook selected by the frontend/ prefix and passed the staged paths on,
but `bun run lint` runs in frontend/, so biome saw frontend/frontend/… and
reported an internal io error for every staged file. The script already lints
the whole tree, so stop passing filenames and let the pattern — now the
extensions biome parses — decide only whether the hook runs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CL9zvnnvcp1mvA8o7impxk

.pre-commit-config.yaml

@@ -19,12 +19,18 @@ repos:
         exclude: ^frontend/src/client/.*
   - repo: local
     hooks:
+      # `bun run lint` runs in frontend/ and already points biome at the whole
+      # tree, so the staged paths must not be appended: they are relative to
+      # this repo root and would reach biome as frontend/frontend/… . The
+      # pattern only decides whether the hook runs at all — hence the
+      # extensions biome actually parses, so a text file dropped under
+      # frontend/ no longer triggers it.
       - id: local-biome-check
         name: biome check
         entry: bun run lint
         language: system
-        types: [text]
-        files: ^frontend/
+        pass_filenames: false
+        files: ^frontend/.*\.([cm]?[jt]sx?|jsonc?|css)$
 
       # Font sizes come from the Tailwind scale only; see the Typography
       # section in the root DESIGN-GUIDELINES.md.