app: track uniwind-types.d.ts (fresh clones + CI can't generate it)

The file is uniwind-generated at metro start, but its content derives
only from the themes config — and without it `tsc --noEmit` fails on
any checkout that never ran the dev server (CI, fresh contributor
clones): the className augmentation on RN components vanishes. Track
it like a lockfile-ish artifact; expo-env.d.ts and .expo/types stay
ignored (their absence produces no type errors today).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: yyq1025

packages/app/.gitignore

@@ -9,8 +9,11 @@ dist/
 web-build/
 expo-env.d.ts
 
-# uniwind regenerates this on every metro start
-src/uniwind-types.d.ts
+# src/uniwind-types.d.ts is uniwind-generated but TRACKED: its content is
+# derived from the (rarely changing) uniwind themes config, and without it
+# `tsc --noEmit` fails on every fresh clone / CI runner (no className types
+# on RN components) until someone runs metro once. If uniwind regenerates
+# it differently after a config change, commit the diff.
 
 # Native
 .kotlin/

packages/app/src/uniwind-types.d.ts

@@ -0,0 +1,10 @@
+// NOTE: This file is generated by uniwind and it should not be edited manually.
+/// <reference types="uniwind/types" />
+
+declare module 'uniwind' {
+    export interface UniwindConfig {
+        themes: readonly ['light', 'dark']
+    }
+}
+
+export {}