Navigation dynamic config, theme cleanup, agent/rule updates

Navigation:
- Revert root-navigator to dynamic JSX config (Stack.Navigator/Screen)
  with typed generic params; useInitialRoute() hook in component body
- Add HomeTabParamList to root-param-list.ts; export from index.ts
- Update NavigationRoot.tsx and AnimatedTabBar.tsx accordingly

Theme:
- Remove unused italic font variant from fonts.ts
- Add brand.ts token file; export from theme index
- Sync dark/light theme with new token

Auth / User:
- Export AUTH_SESSION_TAGS from auth/api/keys.ts (satisfies AuthTag[])
- Export USER_UPDATE_TAGS from user/api/keys.ts
- Remove dead oauth-brand-colors.ts constant file
- Update useLoginMutation and useUpdateProfile to import named tag arrays

Docs / rules:
- Update navigation.md to reflect dynamic config (not static)
- Minor fixes in CLAUDE.md, react-query.md, shared-services.md, development.md
- Remove rn-architect agent (superseded by rn-code-reviewer)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: maximcoding

.claude/CLAUDE.md

@@ -29,7 +29,7 @@ src/
 ├── shared/                # Cross-cutting code — must NOT import from features
 │   ├── components/ui/     # Button, Text, ScreenWrapper, …
 │   ├── hooks/
-│   ├── constants/         # shared non-config constants (not storage keys)
+│   ├── constants/         # shared non-config constants (not storage keys; tag arrays belong in feature api/keys.ts)
 │   ├── services/api|storage/
 │   ├── stores/
 │   ├── theme/

.claude/agents/code-reviewer.md

@@ -33,20 +33,28 @@ You are a senior code reviewer for this React Native TypeScript project. Your st
 - [ ] Strict mode compliance — no implicit `any`, no untyped function returns on exported APIs
 - [ ] Zod schemas validate every API response in feature services before returning domain models
 
+### Code Quality
+- [ ] No magic numbers in logic — numeric literals with meaning (timeouts, limits, sizes, counts, offsets) must be named constants defined at module or config level
+- [ ] No magic strings in logic — non-i18n string literals used as identifiers, keys, or config values must be named constants (e.g. storage keys from `src/config/constants.ts`, route names from `src/navigation/routes.ts`)
+- [ ] Functions do one thing — no function exceeds ~40 lines or mixes concerns (data fetching + transformation + UI logic); extract helpers when a function grows beyond a single clear responsibility
+- [ ] No deeply nested callbacks or conditionals — flatten with early returns and extracted helpers
+
 ### UI & Styling
 - [ ] All screens use `ScreenWrapper` as root element
-- [ ] No raw hex colors, numeric spacing, or font sizes — `useTheme()` tokens only
-- [ ] `StyleSheet.create()` used; inline styles only for dynamically computed values
+- [ ] No raw hex colors, numeric spacing, or font sizes — `useTheme()` tokens only; brand colors via `theme.brand.*`
+- [ ] `StyleSheet.create()` used; inline styles only for values that are dynamically computed at render time — not for static overrides
+- [ ] Repeated style patterns extracted into shared `StyleSheet` entries or shared style constants — no copy-pasted style blocks across components
 - [ ] Shared UI components accept strings as props — no hardcoded user-facing copy
 
 ### i18n
-- [ ] All user-facing strings use `useT('<feature>')` with the correct per-feature namespace
-- [ ] Namespace matches the feature directory name (lowercase)
+- [ ] All user-facing strings use `useT()` (no argument) and access keys via `t('feature.key')`
+- [ ] Key prefix matches the feature directory name (lowercase)
 
 ### State & Data
 - [ ] Server state via React Query; local UI state via `useState`; global UI state via Zustand in `src/shared/stores/`
 - [ ] Query keys defined in feature `api/keys.ts` using `[feature, entity, id?, params?]` format
-- [ ] Mutations include `meta.tags` for targeted invalidation
+- [ ] Tag arrays (e.g. `AUTH_SESSION_TAGS`) exported from the feature's `api/keys.ts` — not defined inline in hooks or placed in `src/shared/constants/`
+- [ ] Mutations include `meta.tags` for targeted invalidation; invalidation uses `invalidateByTags` with the feature's own `tagMap` only — no cross-feature tagMap references
 - [ ] MMKV key strings imported from `src/config/constants.ts`, not hardcoded
 
 ### React Native Specifics

.claude/agents/rn-architect.md

@@ -7,11 +7,11 @@ Global rules: [AGENTS.md](../../AGENTS.md). Claude stack summary: [CLAUDE.md](..
 # Rules — navigation
 
 ## Structure
-- **Static config** (`src/navigation/root/root-navigator.tsx`): `createNativeStackNavigator({screens:{}})` — no JSX navigator wrappers.
-- **Root entry** `src/navigation/NavigationRoot.tsx`: `createStaticNavigation(RootStack)` — render exactly once, no second instance.
-- **Initial route:** `getInitialRoute()` from `src/session/bootstrap.ts` — sync MMKV read that resolves `ROOT_ONBOARDING | ROOT_AUTH | ROOT_APP`.
+- **Navigator** (`src/navigation/root/root-navigator.tsx`): JSX `<Stack.Navigator>` + `<Stack.Screen>` pattern. Export `RootNavigator` (the root stack component) and `HomeTabs` (tab navigator component). Create navigators at module level: `const Stack = createNativeStackNavigator<RootStackParamList>()`.
+- **Root entry** `src/navigation/NavigationRoot.tsx`: single `<NavigationContainer>` with `ref={navigationRef}` — render exactly once, no second instance.
+- **Initial route:** `useInitialRoute()` from `src/session/useInitialRoute.ts` — sync `useState` initializer that reads MMKV once, resolves `ROOT_ONBOARDING | ROOT_AUTH | ROOT_APP`.
 - **Routes:** all constants in `src/navigation/routes.ts` — never inline route string literals anywhere.
-- **ParamList:** `RootStackParamList` in `src/navigation/root-param-list.ts`; declared manually (not via `StaticParamList`) to avoid circular deps through feature screens. Declared globally once:
+- **ParamLists:** `RootStackParamList` and `HomeTabParamList` in `src/navigation/root-param-list.ts`; declared manually to avoid circular deps. Global augmentation declared once there:
   ```ts
   declare global {
     namespace ReactNavigation {
@@ -30,14 +30,15 @@ GestureHandlerRootView
       ErrorBoundary
         QueryProvider
           OfflineBanner
-          NavigationRoot
+          NavigationRoot        ← contains NavigationContainer + RootNavigator
 ```
 
-## Static config rules (React Navigation v7)
-- Add screens via the `screens` object — each value is a component, a nested static navigator, or `{ screen, options, linking }`.
-- Use `groups` to share `screenOptions` across a set of screens — do not create a nested navigator just for code organization.
-- Use the `if` property (hook callback) on a screen or group for conditional rendering (auth gate, feature flag). Never call `navigation.navigate()` after auth state changes — React Navigation transitions automatically.
-- Attach dynamic logic (runtime `screenOptions`, `screenListeners`) via `.with()` — it shallow-merges with the static config.
+## Dynamic navigator rules (React Navigation v7)
+- Create navigator instances (`const Stack = createNativeStackNavigator<T>()`) at module scope — not inside components.
+- Add new screens as `<Stack.Screen name={ROUTES.X} component={ScreenComponent} />` inside the appropriate navigator JSX.
+- Share `screenOptions` via the `screenOptions` prop on `<Stack.Navigator>` — do not repeat options on individual screens if they apply to all.
+- For auth gating or feature flags: conditionally render `<Stack.Screen>` in JSX — do not call `navigation.navigate()` after auth state changes.
+- Nested navigators (e.g. tabs inside a stack screen): create a dedicated component (e.g. `HomeTabs`) and register it as the screen component.
 
 ## Params
 - Params must be **JSON-serializable** — required for state persistence and deep linking.
@@ -79,10 +80,10 @@ GestureHandlerRootView
 - `InteractionManager.runAfterInteractions` for heavy non-UI work triggered by navigation.
 
 ## Must not
-- Do not render a second `createStaticNavigation(...)` instance — one root only.
+- Do not render a second `<NavigationContainer>` — one root only.
 - Do not call `navigation.navigate()` after an auth state change — conditional screen rendering handles it.
 - Do not nest navigators of the same type (tabs-in-tabs, stack-in-stack at the same level).
-- Do not create a nested navigator solely for code organization — use `groups` instead.
+- Do not create a nested navigator solely for code organization — group screens under a shared `screenOptions` prop instead.
 - Do not navigate from `src/shared/**` directly — pass callbacks as props or use `navigationRef` helpers.
 - Do not add navigation logic inside `src/shared/components/ui/` components.
 - Do not pass full data objects as params — pass IDs and fetch data inside the screen.

.claude/rules/navigation.md

@@ -38,6 +38,7 @@ Never hardcode numeric stale/gc values — always reference a `Freshness` profil
 
 ## Must not
 - No React Query keys inline in components — always use `api/keys.ts`.
+- No tag arrays (e.g. `['auth:me', 'auth:session']`) inline in hooks — export named arrays from the feature's `api/keys.ts` and import from there.
 - No `invalidateQueries()` without a targeted key — use tag-based invalidation.
 - No magic `staleTime` / `gcTime` numbers — use `Freshness` profiles.
 - No server data duplicated in Zustand.

.claude/rules/react-query.md

@@ -35,7 +35,7 @@ shared/services/
 - All HTTP calls must go through `http/http.client.ts` (exported `httpClient`) / `http/api.ts` helpers or a `transport/` adapter — never bare `fetch`.
 - Every adapter must pass responses through `src/shared/utils/normalize-error.ts` for consistent error shapes.
 - React Query client configuration (staleTime, retry, persistence) must live in `query/policy/`, `query/client/`, or `query/persistence/` — not scattered across feature hooks.
-- Tag-based cache invalidation must use `query/helpers/invalidate-by-tags.ts` and tag constants from `query/tags.ts`.
+- Tag-based cache invalidation must use `query/helpers/invalidate-by-tags.ts`. The `Tag`, `TagMap`, and `KeyGetter` types live in `query/tags.ts`; feature tag arrays (e.g. `AUTH_SESSION_TAGS`) and tagMaps belong in each feature's `api/keys.ts`.
 - MMKV key strings must be imported from `src/config/constants.ts`.
 - Sentry calls (`captureException`, `captureMessage`) must go through `monitoring/sentry.ts` helpers — do not call the Sentry SDK directly in feature code.
 - The mock transport adapter (`transport/adapters/mock.adapter.ts`) is dev-only; it must be gated by `flags.USE_MOCK` from `src/config/constants.ts`.

.claude/rules/shared-services.md

@@ -0,0 +1,29 @@
+# RN Starter Review Checklist
+
+Use this as a concise pass/fail checklist during reviews.
+
+## Correctness
+- [ ] Logic changes handle happy path and edge cases.
+- [ ] Async flows handle loading, success, and error states.
+- [ ] Errors are not swallowed; context is preserved.
+
+## Architecture and imports
+- [ ] `src/shared` does not import feature code.
+- [ ] Imports use `@/` aliases, not deep relative paths.
+- [ ] New feature code is placed under `src/features/<feature>/...`.
+
+## RN UI and theming
+- [ ] No raw colors/spacing/fonts in UI code.
+- [ ] Styling uses theme tokens and `StyleSheet.create()`.
+- [ ] Platform-specific behavior is handled where required.
+
+## Data and state
+- [ ] Server state uses React Query patterns from feature `api/keys.ts`.
+- [ ] Mutations include targeted invalidation patterns.
+- [ ] No server/domain data is moved into Zustand global stores.
+- [ ] No direct `fetch` usage; transport/API layer is used.
+
+## Tests
+- [ ] Non-trivial behavior changes include tests.
+- [ ] Missing tests are called out with exact suggested scenarios.
+- [ ] Residual risk and untested paths are explicitly noted.

.claude/skills/rn-code-reviewer/CHECKLIST.md

@@ -0,0 +1,82 @@
+---
+name: rn-code-reviewer
+description: Reviews React Native bare-workflow changes in this starter for correctness, regressions, architecture boundaries, React Query usage, theming, and test coverage. Use when reviewing PRs, diffs, or requested code reviews.
+---
+
+# RN Code Reviewer
+
+Project-specific code review workflow for this React Native starter.
+
+## When to apply
+
+Use this skill when:
+- Reviewing pull requests or local diffs
+- Asked to "review" code quality, bugs, or regressions
+- Validating RN architecture and repo conventions before merge
+
+## Review priorities
+
+Always prioritize findings in this order:
+1. Correctness and behavioral regressions
+2. Security/privacy risks and error handling gaps
+3. Architecture and boundary violations
+4. Performance concerns with real user impact
+5. Missing or weak tests
+
+## Required checks
+
+### 1) Correctness and risk
+- Verify changed logic matches intended behavior and handles edge cases.
+- Flag silent failures, swallowed errors, or lossy error handling.
+- Check async flows for loading, success, and error-state handling.
+
+### 2) Repository architecture constraints
+- Enforce feature/shared boundaries (`src/shared` must not import from features).
+- Enforce alias imports (`@/`); flag deep relative imports.
+- Verify feature code stays under `src/features/<feature>/...` with expected folders.
+
+### 3) React Native UI conventions
+- Flag raw colors/spacing/fonts in UI; require theme tokens.
+- Prefer `StyleSheet.create()` over broad inline styles (except dynamic values).
+- Verify platform-specific behavior is handled where needed (`Platform.select`, native differences).
+
+### 4) Data/state conventions
+- Server state should use React Query (feature-level `api/keys.ts` key patterns).
+- Mutations should use targeted invalidation (`meta.tags` / invalidation paths).
+- Flag server data leaking into Zustand stores.
+- Flag direct `fetch` usage (project transport layer should be used).
+
+### 5) Tests and verification
+- Ensure non-trivial logic changes include tests or justify why not.
+- Suggest concrete missing tests (what behavior, where to add).
+- Highlight risky untested paths before merge.
+
+## Output format
+
+Return findings first, ordered by severity:
+
+1. `Critical` — must fix before merge
+2. `Major` — high-impact issues, should fix
+3. `Minor` — quality/maintainability improvements
+
+For each finding include:
+- File path
+- Why it is a problem (risk/regression)
+- Specific fix direction
+
+Then include:
+- Open questions/assumptions
+- Brief change summary (secondary)
+- Residual testing gaps
+
+## Review behavior rules
+
+- Do not lead with a broad summary before findings.
+- Be explicit about potential regressions and user impact.
+- Prefer actionable, minimal suggestions over large refactors.
+- If no issues are found, explicitly state "No findings" and note residual risks or test gaps.
+
+## Additional reference
+
+Use this checklist for quick pass/fail scanning:
+- [CHECKLIST.md](CHECKLIST.md)

.claude/skills/rn-code-reviewer/SKILL.md

@@ -17,7 +17,7 @@ src/
 ├── shared/                     # Cross-app code (must NOT import from features)
 │   ├── components/ui/          # Button, Text, ScreenWrapper, OfflineBanner, IconSvg, ErrorBoundary, Activity, SuspenseBoundary
 │   ├── hooks/                  # Shared hooks (useAppState, useToggle, …)
-│   ├── constants/              # Shared non-config constants (e.g. query tag lists)
+│   ├── constants/              # Shared non-config constants (tag arrays belong in feature api/keys.ts)
 │   ├── services/
 │   │   ├── api/                # http, transport, query, network, offline
 │   │   ├── monitoring/         # Optional Sentry init + boundary reporting (see OPERATIONS.md#sentry)

docs/development.md

@@ -43,3 +43,8 @@ export const authKeys = {
 } as const
 
 export type AuthTag = keyof typeof tagMap
+
+export const AUTH_SESSION_TAGS = [
+  'auth:me',
+  'auth:session',
+] as const satisfies readonly AuthTag[]