kappmaker-revenuecatlisted

# KAppMaker — RevenueCat ## Before running any command 1. **Prerequisites** — `kappmaker --version` (install: `npm i -g kappmaker`). If a credential is missing the CLI says so; re-run `kappmaker config init`. 2. **Read `AiGuidelines/` first** — the PRD, positioning and UI spec already answer most questions. 3. **API key** — a **secret API v2 key** (`sk_…`) from the RevenueCat dashboard (Project settings → API keys → V2). A v1 key will not work — and **v2 keys are per-project**: the key is minted inside one project and can only see that project, so each app needs its own. Pass it once with `kappmaker revenuecat setup --api-key sk_...` and it is saved for that app (keyed by bundle ID in `~/.config/kappmaker/revenuecat-keys.json`); every later command finds it automatically. Resolution order: `--api-key` → `REVENUECAT_API_KEY` env → the per-app map → the global `revenuecatApiKey` config value (a fine shortcut when the account has only one app). ### revenuecat setup — Provider Setup **Syntax**: `kappmaker revenuecat setup [--config <path>]` **Syntax**: `kappmaker revenuecat setup [--config <path>] [--api-key <sk_...>]` **Prerequisites**: an API key resolvable per the order above (no external CLI — talks straight to `api.revenuecat.com/v2`). The RevenueCat **project** must already exist in the dashboard. Because the key is project-scoped, it identifies the project by itself — no project ID to configure. The command also cross-checks: a config carrying on