No-code in-app messaging
without the engineering wait.

You are a senior React Native engineer. Implement NudgeKit in this app so we can show in-app home-screen cards without shipping a new binary for every change.

## Goal
Integrate the official NudgeKit React Native SDK so product can publish home cards / carousels from the NudgeKit dashboard and they render inside our app.

## Package
Install:
```bash
npm install nudgekit-react-native react-native-webview
```
(or yarn/pnpm equivalent)

Docs / package: https://www.npmjs.com/package/nudgekit-react-native

## Requirements
1. Add `react-native-webview` if not already present (peer dependency).
2. Create a reusable `HomeCardsSection` (or similar) component that:
   - Imports `NudgeKitProvider` and `NudgeKitCards` from `nudgekit-react-native`
   - Wraps cards like this:

```tsx
import { NudgeKitCards, NudgeKitProvider } from 'nudgekit-react-native';

export function HomeCardsSection({ userId }: { userId: string }) {
  return (
    <NudgeKitProvider
      apiKey={process.env.EXPO_PUBLIC_NUDGEKIT_API_KEY!}
      userId={userId}
      buildId={Number(process.env.EXPO_PUBLIC_NUDGEKIT_BUILD_ID ?? 1)}
    >
      <NudgeKitCards />
    </NudgeKitProvider>
  );
}
```

3. Render `HomeCardsSection` on the main Home / dashboard screen (where promos or offers should appear).
4. Use environment variables — never hardcode live keys:
   - `EXPO_PUBLIC_NUDGEKIT_API_KEY` (from NudgeKit dashboard → API keys)
   - `EXPO_PUBLIC_NUDGEKIT_BUILD_ID` (numeric build id from the dashboard)
5. Pass a stable `userId` for the logged-in user (or a guest id if logged out).
6. Keep styles consistent with the app (spacing, safe areas). Prefer a vertical stack with reasonable gap under the header / above the main feed.
7. Do not break existing navigation or auth.
8. Add a short comment in code: where to get apiKey/buildId in the NudgeKit dashboard.
9. If TypeScript complains, fix types without `any` where possible.
10. After implementing, list files changed and exact env vars the developer must set.

## Constraints
- Expo React Native is the documented path.
- Only implement what is needed for cards to load and render.
- Do not invent non-existent SDK APIs — stick to `NudgeKitProvider` + `NudgeKitCards` as shown.
- If the project structure differs, adapt paths but keep the same integration pattern.

## Deliverable
- Working integration PR-ready code
- Minimal README snippet: install command + env vars + where cards render