refactor(mobile): compile semantic themes for Uniwind

[juliusmarminge]

Problem

Mobile theme colors were resolved through per-component CSS variable subscriptions and scattered JavaScript color props. Palette changes therefore reconciled across many React consumers, and custom registered themes could miss dark: or light: utility branches.

Solution

• Keep T3 Code’s default palette in Uniwind’s built-in light/dark CSS variants, and compile the other five palettes in both appearances as registered Uniwind themes.
• Delete the duplicate JavaScript default-theme object; global.css is now the sole source for T3 Code’s default color values.
• Move ordinary React Native surfaces to semantic className, colorClassName, and tintColorClassName styling.
• Apply the registered theme immediately, then persist preferences through React; keep one documented palette bridge only for native and third-party APIs that cannot consume classes.
• Let a theme card select both appearances while its nested light and dark rings select one appearance.
• Generate adaptive tokens for appearance-sensitive values and reject future dark:/light: utilities, CSS-variable subscriptions, or undocumented palette bridges.
• Keep the normal open-source uniwind dependency and native fingerprint from main; this PR contains no Pro package, license, Nitro bump, or evaluation binary.

Verification

• vp run --filter @t3tools/mobile generate
• vp test run apps/mobile/scripts/generate-uniwind-themes.test.ts apps/mobile/src/lib/mobileTheme.test.ts apps/mobile/src/lib/mobileThemeRuntime.test.ts apps/mobile/src/features/review/nativeReviewDiffAdapter.test.ts apps/mobile/src/features/terminal/terminalTheme.test.ts — 35 tests passed
• vp test run oxlint-plugin-t3code — 71 tests passed
• vp run --filter @t3tools/mobile typecheck
• vp run --filter oxlint-plugin-t3code typecheck
• vp lint apps/mobile oxlint-plugin-t3code --report-unused-disable-directives
• vp run lint:mobile — SwiftLint, ktlint, and Detekt passed
• React Doctor changed-scope scan — no errors; four advisory warnings from existing component shapes
• Clean iOS development-client prebuild and rebuild on iOS 26.5
• Clean iOS Expo/Metro export — 9,399 modules bundled
• Repeated whole-card and nested-ring selections across T3 Code, T3 Chat, Grove, and Ocean; pressed state released and semantic tokens stayed coherent

UI evidence

Before (main)	After (compiled Uniwind themes)

Split light/dark selection:

Interaction demo: https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/75369d3b7dfc982f/t3code-free-uniwind-theme-demo.mp4

Built with GPT-5 Codex.

---

Note

Medium Risk
Wide UI refactor touching theming across most mobile screens; incorrect generated tokens or theme registration could cause subtle contrast or palette bugs, though behavior is covered by generator and theme runtime tests.

Overview
This PR replaces per-component useThemeColor subscriptions with Uniwind-driven styling so palette switches reconcile through CSS variants instead of many React color props.

A new generate-uniwind-themes script (wired via pnpm generate) emits generated-uniwind-themes.css, theme name list, and default-variable JSON. It registers five built-in palettes (T3 Chat, Grove, Ocean, Ember, Iris) as {palette}-light / {palette}-dark Uniwind variants, adds adaptive semantic tokens for values that used to rely on dark: / light: utilities, and keeps T3 Code’s default colors authored only in global.css. Metro loads extraThemes from the generated manifest and imports the generated CSS.

Across the app, surfaces move to className, tintColorClassName, and colorClassName (including withUniwind on SymbolView, glass, wordmark, and similar). useUniwindTheme remains for native/third-party APIs that need raw CSS variables (markdown, diff themes, swipe backgrounds). useMobileNavigationTheme no longer takes a theme argument; status bar background color props are dropped in favor of translucent styling.

^{Reviewed by Cursor Bugbot for commit c39f3e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Migrate mobile theming from useThemeColor to Uniwind semantic classes

• Replaces useThemeColor hook calls with useUniwindTheme and class-based tint props (tintColorClassName, colorClassName) across nearly all mobile components, so icon, text, and surface colors resolve via CSS class tokens instead of computed runtime values
• Deletes apps/mobile/src/lib/useThemeColor.ts and adds generated Uniwind theme assets: a build script (generate-uniwind-themes.mts), CSS variable definitions (generated-uniwind-themes.css), and JSON theme maps loaded via Metro config
• Reworks AppearancePreferencesProvider to wrap the app in ScopedTheme, apply theme runtime operations granularly (including native Appearance.setColorScheme), and apply theme switches urgently while deferring non-theme preference saves
• Makes useMobileNavigationTheme parameterless — it now reads appearance from the provider and derives colors from a single Uniwind palette
• Adds oxlint rule no-mobile-uniwind-theme-escape-hatches to flag unapproved escape hatches like useCSSVariable and appearance variants in mobile source
• Risk: getMobileThemeVariables no longer accepts the default theme id and always derives variables from the theme palette; callers of createNativeReviewDiffTheme must now pass an explicit appTheme: MobileThemeVariables. useMobileNavigationTheme signature changed to take no arguments, so existing call sites passing themeAppearance are updated in-tree

^{Macroscope summarized c39f3e4.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+603 B (+10.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.6 KiB	+5.9 KiB (+11.8%)	66.4 KiB	✅
Codex	Live turn messages	16	11	−5 (−31.3%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.7%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.5 KiB	+610 B (+10.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.4 KiB	+5.9 KiB (+11.6%)	66.4 KiB	✅
Claude	Live turn messages	16	11	−5 (−31.3%)	21	✅

Baseline: 83d769f · PR result: c39f3e4 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dad7e213-30a7-4234-b7f8-5e3d10f4c17e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

closing because this is explicitly marked DO NOT MERGE and is an evaluation-only Uniwind Pro experiment containing a local binary package.

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a broad 110-file mobile theming migration that changes shared runtime theme selection, native appearance synchronization, compiled theme registration, and rendering across most screens. The generated assets and tests help constrain the change, but its production blast radius and new theming infrastructure are too substantial for an automated approval recommendation.

^{You can add or adjust custom eligibility rules. Learn more.}

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit a77ec4c59bf2939d6c255e8f28d4d60ba34670e2. Configure here.}

[juliusmarminge]

Problem

Mobile theme colors were resolved through per-component CSS variable subscriptions and scattered JavaScript color props. Palette changes therefore reconciled across many React consumers, and custom registered themes could miss dark: or light: utility branches.

Solution

• Keep T3 Code’s default palette in Uniwind’s built-in light/dark CSS variants, and compile the other five palettes in both appearances as registered Uniwind themes.
• Delete the duplicate JavaScript default-theme object; global.css is now the sole source for T3 Code’s default color values.
• Move ordinary React Native surfaces to semantic className, colorClassName, and tintColorClassName styling.
• Apply the registered theme immediately, then persist preferences through React; keep one documented palette bridge only for native and third-party APIs that cannot consume classes.
• Let a theme card select both appearances while its nested light and dark rings select one appearance.
• Generate adaptive tokens for appearance-sensitive values and reject future dark:/light: utilities, CSS-variable subscriptions, or undocumented palette bridges.
• Keep the normal open-source uniwind dependency and native fingerprint from main; this PR contains no Pro package, license, Nitro bump, or evaluation binary.

Verification

• vp run --filter @t3tools/mobile generate
• vp test run apps/mobile/scripts/generate-uniwind-themes.test.ts apps/mobile/src/lib/mobileTheme.test.ts apps/mobile/src/lib/mobileThemeRuntime.test.ts apps/mobile/src/features/review/nativeReviewDiffAdapter.test.ts apps/mobile/src/features/terminal/terminalTheme.test.ts — 35 tests passed
• vp test run oxlint-plugin-t3code — 71 tests passed
• vp run --filter @t3tools/mobile typecheck
• vp run --filter oxlint-plugin-t3code typecheck
• vp lint apps/mobile oxlint-plugin-t3code --report-unused-disable-directives
• vp run lint:mobile — SwiftLint, ktlint, and Detekt passed
• React Doctor changed-scope scan — no errors; four advisory warnings from existing component shapes
• Clean iOS development-client prebuild and rebuild on iOS 26.5
• Clean iOS Expo/Metro export — 9,399 modules bundled
• Repeated whole-card and nested-ring selections across T3 Code, T3 Chat, Grove, and Ocean; pressed state released and semantic tokens stayed coherent

UI evidence

Before (main)	After (compiled Uniwind themes)

Split light/dark selection:

Interaction demo: https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/75369d3b7dfc982f/t3code-free-uniwind-theme-demo.mp4

Built with GPT-5 Codex.

---

Note

Medium Risk
Wide UI refactor touching theming across most mobile screens; incorrect generated tokens or theme registration could cause subtle contrast or palette bugs, though behavior is covered by generator and theme runtime tests.

Overview
This PR replaces per-component useThemeColor subscriptions with Uniwind-driven styling so palette switches reconcile through CSS variants instead of many React color props.

A new generate-uniwind-themes script (wired via pnpm generate) emits generated-uniwind-themes.css, theme name list, and default-variable JSON. It registers five built-in palettes (T3 Chat, Grove, Ocean, Ember, Iris) as {palette}-light / {palette}-dark Uniwind variants, adds adaptive semantic tokens for values that used to rely on dark: / light: utilities, and keeps T3 Code’s default colors authored only in global.css. Metro loads extraThemes from the generated manifest and imports the generated CSS.

Across the app, surfaces move to className, tintColorClassName, and colorClassName (including withUniwind on SymbolView, glass, wordmark, and similar). useUniwindTheme remains for native/third-party APIs that need raw CSS variables (markdown, diff themes, swipe backgrounds). useMobileNavigationTheme no longer takes a theme argument; status bar background color props are dropped in favor of translucent styling.

^{Reviewed by Cursor Bugbot for commit c39f3e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Migrate mobile theming from useThemeColor to Uniwind semantic classes

• Replaces useThemeColor hook calls with useUniwindTheme and class-based tint props (tintColorClassName, colorClassName) across nearly all mobile components, so icon, text, and surface colors resolve via CSS class tokens instead of computed runtime values
• Deletes apps/mobile/src/lib/useThemeColor.ts and adds generated Uniwind theme assets: a build script (generate-uniwind-themes.mts), CSS variable definitions (generated-uniwind-themes.css), and JSON theme maps loaded via Metro config
• Reworks AppearancePreferencesProvider to wrap the app in ScopedTheme, apply theme runtime operations granularly (including native Appearance.setColorScheme), and apply theme switches urgently while deferring non-theme preference saves
• Makes useMobileNavigationTheme parameterless — it now reads appearance from the provider and derives colors from a single Uniwind palette
• Adds oxlint rule no-mobile-uniwind-theme-escape-hatches to flag unapproved escape hatches like useCSSVariable and appearance variants in mobile source
• Risk: getMobileThemeVariables no longer accepts the default theme id and always derives variables from the theme palette; callers of createNativeReviewDiffTheme must now pass an explicit appTheme: MobileThemeVariables. useMobileNavigationTheme signature changed to take no arguments, so existing call sites passing themeAppearance are updated in-tree

^{Macroscope summarized c39f3e4.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+603 B (+10.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.6 KiB	+5.9 KiB (+11.8%)	66.4 KiB	✅
Codex	Live turn messages	16	11	−5 (−31.3%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.7%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.5 KiB	+610 B (+10.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.4 KiB	+5.9 KiB (+11.6%)	66.4 KiB	✅
Claude	Live turn messages	16	11	−5 (−31.3%)	21	✅

Baseline: 83d769f · PR result: c39f3e4 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dad7e213-30a7-4234-b7f8-5e3d10f4c17e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

closing because this is explicitly marked DO NOT MERGE and is an evaluation-only Uniwind Pro experiment containing a local binary package.

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a broad 110-file mobile theming migration that changes shared runtime theme selection, native appearance synchronization, compiled theme registration, and rendering across most screens. The generated assets and tests help constrain the change, but its production blast radius and new theming infrastructure are too substantial for an automated approval recommendation.

^{You can add or adjust custom eligibility rules. Learn more.}

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit a77ec4c59bf2939d6c255e8f28d4d60ba34670e2. Configure here.}

[juliusmarminge]

Problem

Mobile theme colors were resolved through per-component CSS variable subscriptions and scattered JavaScript color props. Palette changes therefore reconciled across many React consumers, and custom registered themes could miss dark: or light: utility branches.

Solution

• Keep T3 Code’s default palette in Uniwind’s built-in light/dark CSS variants, and compile the other five palettes in both appearances as registered Uniwind themes.
• Delete the duplicate JavaScript default-theme object; global.css is now the sole source for T3 Code’s default color values.
• Move ordinary React Native surfaces to semantic className, colorClassName, and tintColorClassName styling.
• Apply the registered theme immediately, then persist preferences through React; keep one documented palette bridge only for native and third-party APIs that cannot consume classes.
• Let a theme card select both appearances while its nested light and dark rings select one appearance.
• Generate adaptive tokens for appearance-sensitive values and reject future dark:/light: utilities, CSS-variable subscriptions, or undocumented palette bridges.
• Keep the normal open-source uniwind dependency and native fingerprint from main; this PR contains no Pro package, license, Nitro bump, or evaluation binary.

Verification

• vp run --filter @t3tools/mobile generate
• vp test run apps/mobile/scripts/generate-uniwind-themes.test.ts apps/mobile/src/lib/mobileTheme.test.ts apps/mobile/src/lib/mobileThemeRuntime.test.ts apps/mobile/src/features/review/nativeReviewDiffAdapter.test.ts apps/mobile/src/features/terminal/terminalTheme.test.ts — 35 tests passed
• vp test run oxlint-plugin-t3code — 71 tests passed
• vp run --filter @t3tools/mobile typecheck
• vp run --filter oxlint-plugin-t3code typecheck
• vp lint apps/mobile oxlint-plugin-t3code --report-unused-disable-directives
• vp run lint:mobile — SwiftLint, ktlint, and Detekt passed
• React Doctor changed-scope scan — no errors; four advisory warnings from existing component shapes
• Clean iOS development-client prebuild and rebuild on iOS 26.5
• Clean iOS Expo/Metro export — 9,399 modules bundled
• Repeated whole-card and nested-ring selections across T3 Code, T3 Chat, Grove, and Ocean; pressed state released and semantic tokens stayed coherent

UI evidence

Before (main)	After (compiled Uniwind themes)

Split light/dark selection:

Interaction demo: https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/75369d3b7dfc982f/t3code-free-uniwind-theme-demo.mp4

Built with GPT-5 Codex.

---

Note

Medium Risk
Wide UI refactor touching theming across most mobile screens; incorrect generated tokens or theme registration could cause subtle contrast or palette bugs, though behavior is covered by generator and theme runtime tests.

Overview
This PR replaces per-component useThemeColor subscriptions with Uniwind-driven styling so palette switches reconcile through CSS variants instead of many React color props.

A new generate-uniwind-themes script (wired via pnpm generate) emits generated-uniwind-themes.css, theme name list, and default-variable JSON. It registers five built-in palettes (T3 Chat, Grove, Ocean, Ember, Iris) as {palette}-light / {palette}-dark Uniwind variants, adds adaptive semantic tokens for values that used to rely on dark: / light: utilities, and keeps T3 Code’s default colors authored only in global.css. Metro loads extraThemes from the generated manifest and imports the generated CSS.

Across the app, surfaces move to className, tintColorClassName, and colorClassName (including withUniwind on SymbolView, glass, wordmark, and similar). useUniwindTheme remains for native/third-party APIs that need raw CSS variables (markdown, diff themes, swipe backgrounds). useMobileNavigationTheme no longer takes a theme argument; status bar background color props are dropped in favor of translucent styling.

^{Reviewed by Cursor Bugbot for commit c39f3e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Migrate mobile theming from useThemeColor to Uniwind semantic classes

• Replaces useThemeColor hook calls with useUniwindTheme and class-based tint props (tintColorClassName, colorClassName) across nearly all mobile components, so icon, text, and surface colors resolve via CSS class tokens instead of computed runtime values
• Deletes apps/mobile/src/lib/useThemeColor.ts and adds generated Uniwind theme assets: a build script (generate-uniwind-themes.mts), CSS variable definitions (generated-uniwind-themes.css), and JSON theme maps loaded via Metro config
• Reworks AppearancePreferencesProvider to wrap the app in ScopedTheme, apply theme runtime operations granularly (including native Appearance.setColorScheme), and apply theme switches urgently while deferring non-theme preference saves
• Makes useMobileNavigationTheme parameterless — it now reads appearance from the provider and derives colors from a single Uniwind palette
• Adds oxlint rule no-mobile-uniwind-theme-escape-hatches to flag unapproved escape hatches like useCSSVariable and appearance variants in mobile source
• Risk: getMobileThemeVariables no longer accepts the default theme id and always derives variables from the theme palette; callers of createNativeReviewDiffTheme must now pass an explicit appTheme: MobileThemeVariables. useMobileNavigationTheme signature changed to take no arguments, so existing call sites passing themeAppearance are updated in-tree

^{Macroscope summarized c39f3e4.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+603 B (+10.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.6 KiB	+5.9 KiB (+11.8%)	66.4 KiB	✅
Codex	Live turn messages	16	11	−5 (−31.3%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.7%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.5 KiB	+610 B (+10.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.4 KiB	+5.9 KiB (+11.6%)	66.4 KiB	✅
Claude	Live turn messages	16	11	−5 (−31.3%)	21	✅

Baseline: 83d769f · PR result: c39f3e4 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dad7e213-30a7-4234-b7f8-5e3d10f4c17e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

closing because this is explicitly marked DO NOT MERGE and is an evaluation-only Uniwind Pro experiment containing a local binary package.

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a broad 110-file mobile theming migration that changes shared runtime theme selection, native appearance synchronization, compiled theme registration, and rendering across most screens. The generated assets and tests help constrain the change, but its production blast radius and new theming infrastructure are too substantial for an automated approval recommendation.

^{You can add or adjust custom eligibility rules. Learn more.}

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit a77ec4c59bf2939d6c255e8f28d4d60ba34670e2. Configure here.}

[juliusmarminge]

Problem

Mobile theme colors were resolved through per-component CSS variable subscriptions and scattered JavaScript color props. Palette changes therefore reconciled across many React consumers, and custom registered themes could miss dark: or light: utility branches.

Solution

• Keep T3 Code’s default palette in Uniwind’s built-in light/dark CSS variants, and compile the other five palettes in both appearances as registered Uniwind themes.
• Delete the duplicate JavaScript default-theme object; global.css is now the sole source for T3 Code’s default color values.
• Move ordinary React Native surfaces to semantic className, colorClassName, and tintColorClassName styling.
• Apply the registered theme immediately, then persist preferences through React; keep one documented palette bridge only for native and third-party APIs that cannot consume classes.
• Let a theme card select both appearances while its nested light and dark rings select one appearance.
• Generate adaptive tokens for appearance-sensitive values and reject future dark:/light: utilities, CSS-variable subscriptions, or undocumented palette bridges.
• Keep the normal open-source uniwind dependency and native fingerprint from main; this PR contains no Pro package, license, Nitro bump, or evaluation binary.

Verification

• vp run --filter @t3tools/mobile generate
• vp test run apps/mobile/scripts/generate-uniwind-themes.test.ts apps/mobile/src/lib/mobileTheme.test.ts apps/mobile/src/lib/mobileThemeRuntime.test.ts apps/mobile/src/features/review/nativeReviewDiffAdapter.test.ts apps/mobile/src/features/terminal/terminalTheme.test.ts — 35 tests passed
• vp test run oxlint-plugin-t3code — 71 tests passed
• vp run --filter @t3tools/mobile typecheck
• vp run --filter oxlint-plugin-t3code typecheck
• vp lint apps/mobile oxlint-plugin-t3code --report-unused-disable-directives
• vp run lint:mobile — SwiftLint, ktlint, and Detekt passed
• React Doctor changed-scope scan — no errors; four advisory warnings from existing component shapes
• Clean iOS development-client prebuild and rebuild on iOS 26.5
• Clean iOS Expo/Metro export — 9,399 modules bundled
• Repeated whole-card and nested-ring selections across T3 Code, T3 Chat, Grove, and Ocean; pressed state released and semantic tokens stayed coherent

UI evidence

Before (main)	After (compiled Uniwind themes)

Split light/dark selection:

Interaction demo: https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/75369d3b7dfc982f/t3code-free-uniwind-theme-demo.mp4

Built with GPT-5 Codex.

---

Note

Medium Risk
Wide UI refactor touching theming across most mobile screens; incorrect generated tokens or theme registration could cause subtle contrast or palette bugs, though behavior is covered by generator and theme runtime tests.

Overview
This PR replaces per-component useThemeColor subscriptions with Uniwind-driven styling so palette switches reconcile through CSS variants instead of many React color props.

A new generate-uniwind-themes script (wired via pnpm generate) emits generated-uniwind-themes.css, theme name list, and default-variable JSON. It registers five built-in palettes (T3 Chat, Grove, Ocean, Ember, Iris) as {palette}-light / {palette}-dark Uniwind variants, adds adaptive semantic tokens for values that used to rely on dark: / light: utilities, and keeps T3 Code’s default colors authored only in global.css. Metro loads extraThemes from the generated manifest and imports the generated CSS.

Across the app, surfaces move to className, tintColorClassName, and colorClassName (including withUniwind on SymbolView, glass, wordmark, and similar). useUniwindTheme remains for native/third-party APIs that need raw CSS variables (markdown, diff themes, swipe backgrounds). useMobileNavigationTheme no longer takes a theme argument; status bar background color props are dropped in favor of translucent styling.

^{Reviewed by Cursor Bugbot for commit c39f3e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Migrate mobile theming from useThemeColor to Uniwind semantic classes

• Replaces useThemeColor hook calls with useUniwindTheme and class-based tint props (tintColorClassName, colorClassName) across nearly all mobile components, so icon, text, and surface colors resolve via CSS class tokens instead of computed runtime values
• Deletes apps/mobile/src/lib/useThemeColor.ts and adds generated Uniwind theme assets: a build script (generate-uniwind-themes.mts), CSS variable definitions (generated-uniwind-themes.css), and JSON theme maps loaded via Metro config
• Reworks AppearancePreferencesProvider to wrap the app in ScopedTheme, apply theme runtime operations granularly (including native Appearance.setColorScheme), and apply theme switches urgently while deferring non-theme preference saves
• Makes useMobileNavigationTheme parameterless — it now reads appearance from the provider and derives colors from a single Uniwind palette
• Adds oxlint rule no-mobile-uniwind-theme-escape-hatches to flag unapproved escape hatches like useCSSVariable and appearance variants in mobile source
• Risk: getMobileThemeVariables no longer accepts the default theme id and always derives variables from the theme palette; callers of createNativeReviewDiffTheme must now pass an explicit appTheme: MobileThemeVariables. useMobileNavigationTheme signature changed to take no arguments, so existing call sites passing themeAppearance are updated in-tree

^{Macroscope summarized c39f3e4.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+603 B (+10.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.6 KiB	+5.9 KiB (+11.8%)	66.4 KiB	✅
Codex	Live turn messages	16	11	−5 (−31.3%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.7%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.5 KiB	+610 B (+10.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.4 KiB	+5.9 KiB (+11.6%)	66.4 KiB	✅
Claude	Live turn messages	16	11	−5 (−31.3%)	21	✅

Baseline: 83d769f · PR result: c39f3e4 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dad7e213-30a7-4234-b7f8-5e3d10f4c17e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

closing because this is explicitly marked DO NOT MERGE and is an evaluation-only Uniwind Pro experiment containing a local binary package.

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a broad 110-file mobile theming migration that changes shared runtime theme selection, native appearance synchronization, compiled theme registration, and rendering across most screens. The generated assets and tests help constrain the change, but its production blast radius and new theming infrastructure are too substantial for an automated approval recommendation.

^{You can add or adjust custom eligibility rules. Learn more.}

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit a77ec4c59bf2939d6c255e8f28d4d60ba34670e2. Configure here.}

[juliusmarminge]

Problem

Mobile theme colors were resolved through per-component CSS variable subscriptions and scattered JavaScript color props. Palette changes therefore reconciled across many React consumers, and custom registered themes could miss dark: or light: utility branches.

Solution

• Keep T3 Code’s default palette in Uniwind’s built-in light/dark CSS variants, and compile the other five palettes in both appearances as registered Uniwind themes.
• Delete the duplicate JavaScript default-theme object; global.css is now the sole source for T3 Code’s default color values.
• Move ordinary React Native surfaces to semantic className, colorClassName, and tintColorClassName styling.
• Apply the registered theme immediately, then persist preferences through React; keep one documented palette bridge only for native and third-party APIs that cannot consume classes.
• Let a theme card select both appearances while its nested light and dark rings select one appearance.
• Generate adaptive tokens for appearance-sensitive values and reject future dark:/light: utilities, CSS-variable subscriptions, or undocumented palette bridges.
• Keep the normal open-source uniwind dependency and native fingerprint from main; this PR contains no Pro package, license, Nitro bump, or evaluation binary.

Verification

• vp run --filter @t3tools/mobile generate
• vp test run apps/mobile/scripts/generate-uniwind-themes.test.ts apps/mobile/src/lib/mobileTheme.test.ts apps/mobile/src/lib/mobileThemeRuntime.test.ts apps/mobile/src/features/review/nativeReviewDiffAdapter.test.ts apps/mobile/src/features/terminal/terminalTheme.test.ts — 35 tests passed
• vp test run oxlint-plugin-t3code — 71 tests passed
• vp run --filter @t3tools/mobile typecheck
• vp run --filter oxlint-plugin-t3code typecheck
• vp lint apps/mobile oxlint-plugin-t3code --report-unused-disable-directives
• vp run lint:mobile — SwiftLint, ktlint, and Detekt passed
• React Doctor changed-scope scan — no errors; four advisory warnings from existing component shapes
• Clean iOS development-client prebuild and rebuild on iOS 26.5
• Clean iOS Expo/Metro export — 9,399 modules bundled
• Repeated whole-card and nested-ring selections across T3 Code, T3 Chat, Grove, and Ocean; pressed state released and semantic tokens stayed coherent

UI evidence

Before (main)	After (compiled Uniwind themes)

Split light/dark selection:

Interaction demo: https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/75369d3b7dfc982f/t3code-free-uniwind-theme-demo.mp4

Built with GPT-5 Codex.

---

Note

Medium Risk
Wide UI refactor touching theming across most mobile screens; incorrect generated tokens or theme registration could cause subtle contrast or palette bugs, though behavior is covered by generator and theme runtime tests.

Overview
This PR replaces per-component useThemeColor subscriptions with Uniwind-driven styling so palette switches reconcile through CSS variants instead of many React color props.

A new generate-uniwind-themes script (wired via pnpm generate) emits generated-uniwind-themes.css, theme name list, and default-variable JSON. It registers five built-in palettes (T3 Chat, Grove, Ocean, Ember, Iris) as {palette}-light / {palette}-dark Uniwind variants, adds adaptive semantic tokens for values that used to rely on dark: / light: utilities, and keeps T3 Code’s default colors authored only in global.css. Metro loads extraThemes from the generated manifest and imports the generated CSS.

Across the app, surfaces move to className, tintColorClassName, and colorClassName (including withUniwind on SymbolView, glass, wordmark, and similar). useUniwindTheme remains for native/third-party APIs that need raw CSS variables (markdown, diff themes, swipe backgrounds). useMobileNavigationTheme no longer takes a theme argument; status bar background color props are dropped in favor of translucent styling.

^{Reviewed by Cursor Bugbot for commit c39f3e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Migrate mobile theming from useThemeColor to Uniwind semantic classes

• Replaces useThemeColor hook calls with useUniwindTheme and class-based tint props (tintColorClassName, colorClassName) across nearly all mobile components, so icon, text, and surface colors resolve via CSS class tokens instead of computed runtime values
• Deletes apps/mobile/src/lib/useThemeColor.ts and adds generated Uniwind theme assets: a build script (generate-uniwind-themes.mts), CSS variable definitions (generated-uniwind-themes.css), and JSON theme maps loaded via Metro config
• Reworks AppearancePreferencesProvider to wrap the app in ScopedTheme, apply theme runtime operations granularly (including native Appearance.setColorScheme), and apply theme switches urgently while deferring non-theme preference saves
• Makes useMobileNavigationTheme parameterless — it now reads appearance from the provider and derives colors from a single Uniwind palette
• Adds oxlint rule no-mobile-uniwind-theme-escape-hatches to flag unapproved escape hatches like useCSSVariable and appearance variants in mobile source
• Risk: getMobileThemeVariables no longer accepts the default theme id and always derives variables from the theme palette; callers of createNativeReviewDiffTheme must now pass an explicit appTheme: MobileThemeVariables. useMobileNavigationTheme signature changed to take no arguments, so existing call sites passing themeAppearance are updated in-tree

^{Macroscope summarized c39f3e4.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+603 B (+10.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.6 KiB	+5.9 KiB (+11.8%)	66.4 KiB	✅
Codex	Live turn messages	16	11	−5 (−31.3%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.7%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.5 KiB	+610 B (+10.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.4 KiB	+5.9 KiB (+11.6%)	66.4 KiB	✅
Claude	Live turn messages	16	11	−5 (−31.3%)	21	✅

Baseline: 83d769f · PR result: c39f3e4 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dad7e213-30a7-4234-b7f8-5e3d10f4c17e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

closing because this is explicitly marked DO NOT MERGE and is an evaluation-only Uniwind Pro experiment containing a local binary package.

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a broad 110-file mobile theming migration that changes shared runtime theme selection, native appearance synchronization, compiled theme registration, and rendering across most screens. The generated assets and tests help constrain the change, but its production blast radius and new theming infrastructure are too substantial for an automated approval recommendation.

^{You can add or adjust custom eligibility rules. Learn more.}

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit a77ec4c59bf2939d6c255e8f28d4d60ba34670e2. Configure here.}

[juliusmarminge]

Problem

Mobile theme colors were resolved through per-component CSS variable subscriptions and scattered JavaScript color props. Palette changes therefore reconciled across many React consumers, and custom registered themes could miss dark: or light: utility branches.

Solution

• Keep T3 Code’s default palette in Uniwind’s built-in light/dark CSS variants, and compile the other five palettes in both appearances as registered Uniwind themes.
• Delete the duplicate JavaScript default-theme object; global.css is now the sole source for T3 Code’s default color values.
• Move ordinary React Native surfaces to semantic className, colorClassName, and tintColorClassName styling.
• Apply the registered theme immediately, then persist preferences through React; keep one documented palette bridge only for native and third-party APIs that cannot consume classes.
• Let a theme card select both appearances while its nested light and dark rings select one appearance.
• Generate adaptive tokens for appearance-sensitive values and reject future dark:/light: utilities, CSS-variable subscriptions, or undocumented palette bridges.
• Keep the normal open-source uniwind dependency and native fingerprint from main; this PR contains no Pro package, license, Nitro bump, or evaluation binary.

Verification

• vp run --filter @t3tools/mobile generate
• vp test run apps/mobile/scripts/generate-uniwind-themes.test.ts apps/mobile/src/lib/mobileTheme.test.ts apps/mobile/src/lib/mobileThemeRuntime.test.ts apps/mobile/src/features/review/nativeReviewDiffAdapter.test.ts apps/mobile/src/features/terminal/terminalTheme.test.ts — 35 tests passed
• vp test run oxlint-plugin-t3code — 71 tests passed
• vp run --filter @t3tools/mobile typecheck
• vp run --filter oxlint-plugin-t3code typecheck
• vp lint apps/mobile oxlint-plugin-t3code --report-unused-disable-directives
• vp run lint:mobile — SwiftLint, ktlint, and Detekt passed
• React Doctor changed-scope scan — no errors; four advisory warnings from existing component shapes
• Clean iOS development-client prebuild and rebuild on iOS 26.5
• Clean iOS Expo/Metro export — 9,399 modules bundled
• Repeated whole-card and nested-ring selections across T3 Code, T3 Chat, Grove, and Ocean; pressed state released and semantic tokens stayed coherent

UI evidence

Before (main)	After (compiled Uniwind themes)

Split light/dark selection:

Interaction demo: https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/75369d3b7dfc982f/t3code-free-uniwind-theme-demo.mp4

Built with GPT-5 Codex.

---

Note

Medium Risk
Wide UI refactor touching theming across most mobile screens; incorrect generated tokens or theme registration could cause subtle contrast or palette bugs, though behavior is covered by generator and theme runtime tests.

Overview
This PR replaces per-component useThemeColor subscriptions with Uniwind-driven styling so palette switches reconcile through CSS variants instead of many React color props.

A new generate-uniwind-themes script (wired via pnpm generate) emits generated-uniwind-themes.css, theme name list, and default-variable JSON. It registers five built-in palettes (T3 Chat, Grove, Ocean, Ember, Iris) as {palette}-light / {palette}-dark Uniwind variants, adds adaptive semantic tokens for values that used to rely on dark: / light: utilities, and keeps T3 Code’s default colors authored only in global.css. Metro loads extraThemes from the generated manifest and imports the generated CSS.

Across the app, surfaces move to className, tintColorClassName, and colorClassName (including withUniwind on SymbolView, glass, wordmark, and similar). useUniwindTheme remains for native/third-party APIs that need raw CSS variables (markdown, diff themes, swipe backgrounds). useMobileNavigationTheme no longer takes a theme argument; status bar background color props are dropped in favor of translucent styling.

^{Reviewed by Cursor Bugbot for commit c39f3e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Migrate mobile theming from useThemeColor to Uniwind semantic classes

• Replaces useThemeColor hook calls with useUniwindTheme and class-based tint props (tintColorClassName, colorClassName) across nearly all mobile components, so icon, text, and surface colors resolve via CSS class tokens instead of computed runtime values
• Deletes apps/mobile/src/lib/useThemeColor.ts and adds generated Uniwind theme assets: a build script (generate-uniwind-themes.mts), CSS variable definitions (generated-uniwind-themes.css), and JSON theme maps loaded via Metro config
• Reworks AppearancePreferencesProvider to wrap the app in ScopedTheme, apply theme runtime operations granularly (including native Appearance.setColorScheme), and apply theme switches urgently while deferring non-theme preference saves
• Makes useMobileNavigationTheme parameterless — it now reads appearance from the provider and derives colors from a single Uniwind palette
• Adds oxlint rule no-mobile-uniwind-theme-escape-hatches to flag unapproved escape hatches like useCSSVariable and appearance variants in mobile source
• Risk: getMobileThemeVariables no longer accepts the default theme id and always derives variables from the theme palette; callers of createNativeReviewDiffTheme must now pass an explicit appTheme: MobileThemeVariables. useMobileNavigationTheme signature changed to take no arguments, so existing call sites passing themeAppearance are updated in-tree

^{Macroscope summarized c39f3e4.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+603 B (+10.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.6 KiB	+5.9 KiB (+11.8%)	66.4 KiB	✅
Codex	Live turn messages	16	11	−5 (−31.3%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.7%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.5 KiB	+610 B (+10.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.4 KiB	+5.9 KiB (+11.6%)	66.4 KiB	✅
Claude	Live turn messages	16	11	−5 (−31.3%)	21	✅

Baseline: 83d769f · PR result: c39f3e4 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dad7e213-30a7-4234-b7f8-5e3d10f4c17e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

closing because this is explicitly marked DO NOT MERGE and is an evaluation-only Uniwind Pro experiment containing a local binary package.

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a broad 110-file mobile theming migration that changes shared runtime theme selection, native appearance synchronization, compiled theme registration, and rendering across most screens. The generated assets and tests help constrain the change, but its production blast radius and new theming infrastructure are too substantial for an automated approval recommendation.

^{You can add or adjust custom eligibility rules. Learn more.}

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit a77ec4c59bf2939d6c255e8f28d4d60ba34670e2. Configure here.}

[juliusmarminge]

Problem

Mobile theme colors were resolved through per-component CSS variable subscriptions and scattered JavaScript color props. Palette changes therefore reconciled across many React consumers, and custom registered themes could miss dark: or light: utility branches.

Solution

• Keep T3 Code’s default palette in Uniwind’s built-in light/dark CSS variants, and compile the other five palettes in both appearances as registered Uniwind themes.
• Delete the duplicate JavaScript default-theme object; global.css is now the sole source for T3 Code’s default color values.
• Move ordinary React Native surfaces to semantic className, colorClassName, and tintColorClassName styling.
• Apply the registered theme immediately, then persist preferences through React; keep one documented palette bridge only for native and third-party APIs that cannot consume classes.
• Let a theme card select both appearances while its nested light and dark rings select one appearance.
• Generate adaptive tokens for appearance-sensitive values and reject future dark:/light: utilities, CSS-variable subscriptions, or undocumented palette bridges.
• Keep the normal open-source uniwind dependency and native fingerprint from main; this PR contains no Pro package, license, Nitro bump, or evaluation binary.

Verification

• vp run --filter @t3tools/mobile generate
• vp test run apps/mobile/scripts/generate-uniwind-themes.test.ts apps/mobile/src/lib/mobileTheme.test.ts apps/mobile/src/lib/mobileThemeRuntime.test.ts apps/mobile/src/features/review/nativeReviewDiffAdapter.test.ts apps/mobile/src/features/terminal/terminalTheme.test.ts — 35 tests passed
• vp test run oxlint-plugin-t3code — 71 tests passed
• vp run --filter @t3tools/mobile typecheck
• vp run --filter oxlint-plugin-t3code typecheck
• vp lint apps/mobile oxlint-plugin-t3code --report-unused-disable-directives
• vp run lint:mobile — SwiftLint, ktlint, and Detekt passed
• React Doctor changed-scope scan — no errors; four advisory warnings from existing component shapes
• Clean iOS development-client prebuild and rebuild on iOS 26.5
• Clean iOS Expo/Metro export — 9,399 modules bundled
• Repeated whole-card and nested-ring selections across T3 Code, T3 Chat, Grove, and Ocean; pressed state released and semantic tokens stayed coherent

UI evidence

Before (main)	After (compiled Uniwind themes)

Split light/dark selection:

Interaction demo: https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/75369d3b7dfc982f/t3code-free-uniwind-theme-demo.mp4

Built with GPT-5 Codex.

---

Note

Medium Risk
Wide UI refactor touching theming across most mobile screens; incorrect generated tokens or theme registration could cause subtle contrast or palette bugs, though behavior is covered by generator and theme runtime tests.

Overview
This PR replaces per-component useThemeColor subscriptions with Uniwind-driven styling so palette switches reconcile through CSS variants instead of many React color props.

A new generate-uniwind-themes script (wired via pnpm generate) emits generated-uniwind-themes.css, theme name list, and default-variable JSON. It registers five built-in palettes (T3 Chat, Grove, Ocean, Ember, Iris) as {palette}-light / {palette}-dark Uniwind variants, adds adaptive semantic tokens for values that used to rely on dark: / light: utilities, and keeps T3 Code’s default colors authored only in global.css. Metro loads extraThemes from the generated manifest and imports the generated CSS.

Across the app, surfaces move to className, tintColorClassName, and colorClassName (including withUniwind on SymbolView, glass, wordmark, and similar). useUniwindTheme remains for native/third-party APIs that need raw CSS variables (markdown, diff themes, swipe backgrounds). useMobileNavigationTheme no longer takes a theme argument; status bar background color props are dropped in favor of translucent styling.

^{Reviewed by Cursor Bugbot for commit c39f3e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Migrate mobile theming from useThemeColor to Uniwind semantic classes

• Replaces useThemeColor hook calls with useUniwindTheme and class-based tint props (tintColorClassName, colorClassName) across nearly all mobile components, so icon, text, and surface colors resolve via CSS class tokens instead of computed runtime values
• Deletes apps/mobile/src/lib/useThemeColor.ts and adds generated Uniwind theme assets: a build script (generate-uniwind-themes.mts), CSS variable definitions (generated-uniwind-themes.css), and JSON theme maps loaded via Metro config
• Reworks AppearancePreferencesProvider to wrap the app in ScopedTheme, apply theme runtime operations granularly (including native Appearance.setColorScheme), and apply theme switches urgently while deferring non-theme preference saves
• Makes useMobileNavigationTheme parameterless — it now reads appearance from the provider and derives colors from a single Uniwind palette
• Adds oxlint rule no-mobile-uniwind-theme-escape-hatches to flag unapproved escape hatches like useCSSVariable and appearance variants in mobile source
• Risk: getMobileThemeVariables no longer accepts the default theme id and always derives variables from the theme palette; callers of createNativeReviewDiffTheme must now pass an explicit appTheme: MobileThemeVariables. useMobileNavigationTheme signature changed to take no arguments, so existing call sites passing themeAppearance are updated in-tree

^{Macroscope summarized c39f3e4.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+603 B (+10.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.6 KiB	+5.9 KiB (+11.8%)	66.4 KiB	✅
Codex	Live turn messages	16	11	−5 (−31.3%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.7%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.5 KiB	+610 B (+10.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.4 KiB	+5.9 KiB (+11.6%)	66.4 KiB	✅
Claude	Live turn messages	16	11	−5 (−31.3%)	21	✅

Baseline: 83d769f · PR result: c39f3e4 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dad7e213-30a7-4234-b7f8-5e3d10f4c17e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

closing because this is explicitly marked DO NOT MERGE and is an evaluation-only Uniwind Pro experiment containing a local binary package.

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a broad 110-file mobile theming migration that changes shared runtime theme selection, native appearance synchronization, compiled theme registration, and rendering across most screens. The generated assets and tests help constrain the change, but its production blast radius and new theming infrastructure are too substantial for an automated approval recommendation.

^{You can add or adjust custom eligibility rules. Learn more.}

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit a77ec4c59bf2939d6c255e8f28d4d60ba34670e2. Configure here.}

[juliusmarminge]

Problem

Mobile theme colors were resolved through per-component CSS variable subscriptions and scattered JavaScript color props. Palette changes therefore reconciled across many React consumers, and custom registered themes could miss dark: or light: utility branches.

Solution

• Keep T3 Code’s default palette in Uniwind’s built-in light/dark CSS variants, and compile the other five palettes in both appearances as registered Uniwind themes.
• Delete the duplicate JavaScript default-theme object; global.css is now the sole source for T3 Code’s default color values.
• Move ordinary React Native surfaces to semantic className, colorClassName, and tintColorClassName styling.
• Apply the registered theme immediately, then persist preferences through React; keep one documented palette bridge only for native and third-party APIs that cannot consume classes.
• Let a theme card select both appearances while its nested light and dark rings select one appearance.
• Generate adaptive tokens for appearance-sensitive values and reject future dark:/light: utilities, CSS-variable subscriptions, or undocumented palette bridges.
• Keep the normal open-source uniwind dependency and native fingerprint from main; this PR contains no Pro package, license, Nitro bump, or evaluation binary.

Verification

• vp run --filter @t3tools/mobile generate
• vp test run apps/mobile/scripts/generate-uniwind-themes.test.ts apps/mobile/src/lib/mobileTheme.test.ts apps/mobile/src/lib/mobileThemeRuntime.test.ts apps/mobile/src/features/review/nativeReviewDiffAdapter.test.ts apps/mobile/src/features/terminal/terminalTheme.test.ts — 35 tests passed
• vp test run oxlint-plugin-t3code — 71 tests passed
• vp run --filter @t3tools/mobile typecheck
• vp run --filter oxlint-plugin-t3code typecheck
• vp lint apps/mobile oxlint-plugin-t3code --report-unused-disable-directives
• vp run lint:mobile — SwiftLint, ktlint, and Detekt passed
• React Doctor changed-scope scan — no errors; four advisory warnings from existing component shapes
• Clean iOS development-client prebuild and rebuild on iOS 26.5
• Clean iOS Expo/Metro export — 9,399 modules bundled
• Repeated whole-card and nested-ring selections across T3 Code, T3 Chat, Grove, and Ocean; pressed state released and semantic tokens stayed coherent

UI evidence

Before (main)	After (compiled Uniwind themes)

Split light/dark selection:

Interaction demo: https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/75369d3b7dfc982f/t3code-free-uniwind-theme-demo.mp4

Built with GPT-5 Codex.

---

Note

Medium Risk
Wide UI refactor touching theming across most mobile screens; incorrect generated tokens or theme registration could cause subtle contrast or palette bugs, though behavior is covered by generator and theme runtime tests.

Overview
This PR replaces per-component useThemeColor subscriptions with Uniwind-driven styling so palette switches reconcile through CSS variants instead of many React color props.

A new generate-uniwind-themes script (wired via pnpm generate) emits generated-uniwind-themes.css, theme name list, and default-variable JSON. It registers five built-in palettes (T3 Chat, Grove, Ocean, Ember, Iris) as {palette}-light / {palette}-dark Uniwind variants, adds adaptive semantic tokens for values that used to rely on dark: / light: utilities, and keeps T3 Code’s default colors authored only in global.css. Metro loads extraThemes from the generated manifest and imports the generated CSS.

Across the app, surfaces move to className, tintColorClassName, and colorClassName (including withUniwind on SymbolView, glass, wordmark, and similar). useUniwindTheme remains for native/third-party APIs that need raw CSS variables (markdown, diff themes, swipe backgrounds). useMobileNavigationTheme no longer takes a theme argument; status bar background color props are dropped in favor of translucent styling.

^{Reviewed by Cursor Bugbot for commit c39f3e4. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Migrate mobile theming from useThemeColor to Uniwind semantic classes

• Replaces useThemeColor hook calls with useUniwindTheme and class-based tint props (tintColorClassName, colorClassName) across nearly all mobile components, so icon, text, and surface colors resolve via CSS class tokens instead of computed runtime values
• Deletes apps/mobile/src/lib/useThemeColor.ts and adds generated Uniwind theme assets: a build script (generate-uniwind-themes.mts), CSS variable definitions (generated-uniwind-themes.css), and JSON theme maps loaded via Metro config
• Reworks AppearancePreferencesProvider to wrap the app in ScopedTheme, apply theme runtime operations granularly (including native Appearance.setColorScheme), and apply theme switches urgently while deferring non-theme preference saves
• Makes useMobileNavigationTheme parameterless — it now reads appearance from the provider and derives colors from a single Uniwind palette
• Adds oxlint rule no-mobile-uniwind-theme-escape-hatches to flag unapproved escape hatches like useCSSVariable and appearance variants in mobile source
• Risk: getMobileThemeVariables no longer accepts the default theme id and always derives variables from the theme palette; callers of createNativeReviewDiffTheme must now pass an explicit appTheme: MobileThemeVariables. useMobileNavigationTheme signature changed to take no arguments, so existing call sites passing themeAppearance are updated in-tree

^{Macroscope summarized c39f3e4.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+26.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	6.4 KiB	+603 B (+10.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	55.6 KiB	+5.9 KiB (+11.8%)	66.4 KiB	✅
Codex	Live turn messages	16	11	−5 (−31.3%)	21	✅
Claude	Total thread wire	11.3 KiB	13.3 KiB	+2.0 KiB (+17.7%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	6.9 KiB	+1.4 KiB (+25.8%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	6.5 KiB	+610 B (+10.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	56.4 KiB	+5.9 KiB (+11.6%)	66.4 KiB	✅
Claude	Live turn messages	16	11	−5 (−31.3%)	21	✅

Baseline: 83d769f · PR result: c39f3e4 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dad7e213-30a7-4234-b7f8-5e3d10f4c17e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

closing because this is explicitly marked DO NOT MERGE and is an evaluation-only Uniwind Pro experiment containing a local binary package.

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a broad 110-file mobile theming migration that changes shared runtime theme selection, native appearance synchronization, compiled theme registration, and rendering across most screens. The generated assets and tests help constrain the change, but its production blast radius and new theming infrastructure are too substantial for an automated approval recommendation.

^{You can add or adjust custom eligibility rules. Learn more.}

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit a77ec4c59bf2939d6c255e8f28d4d60ba34670e2. Configure here.}