@donotdev/cli 0.0.15 → 0.0.16

package/templates/root-consumer/guides/dndev/SETUP_OAUTH_PROVIDERS.md.example

@@ -0,0 +1,60 @@
+# OAuth Provider Setup Guide
+
+Each OAuth provider requires manual registration in their developer console.
+`dndev setup oauth` computes the correct redirect URI for you.
+
+## Redirect URIs
+
+### Firebase
+```
+https://{{PROJECT_ID}}.firebaseapp.com/__/auth/handler
+```
+> If you use a custom auth domain, replace `{{PROJECT_ID}}.firebaseapp.com` with your custom domain.
+
+### Supabase
+```
+https://{{PROJECT_ID}}.supabase.co/auth/v1/callback
+```
+
+---
+
+## Google OAuth
+
+1. Go to https://console.cloud.google.com/apis/credentials
+2. Create **OAuth 2.0 Client ID** (type: Web application)
+3. Add **Authorized redirect URI** (see above)
+4. Copy **Client ID** and **Client Secret**
+5. Enable in your backend:
+   - Firebase: Console > Authentication > Sign-in method > Google
+   - Supabase: Dashboard > Authentication > Providers > Google
+
+## GitHub OAuth
+
+1. Go to https://github.com/settings/developers
+2. Click **New OAuth App**
+3. Set **Authorization callback URL** (see redirect URI above)
+4. Copy **Client ID** and **Client Secret**
+5. Enable in your backend:
+   - Firebase: Console > Authentication > Sign-in method > GitHub
+   - Supabase: Dashboard > Authentication > Providers > GitHub
+
+## Apple Sign In
+
+1. Go to https://developer.apple.com/account/resources/identifiers/list/serviceId
+2. Create a **Services ID**
+3. Enable **Sign In with Apple**
+4. Add **Redirect URL** (see above)
+5. Create a **Key** for Sign In with Apple
+6. Enable in your backend:
+   - Firebase: Console > Authentication > Sign-in method > Apple
+   - Supabase: Dashboard > Authentication > Providers > Apple
+
+> **Note:** Apple requires an Apple Developer Program membership ($99/year).
+
+## Verify
+
+```bash
+dndev doctor
+```
+
+Check that auth providers are detected and backend configuration is referenced.

package/templates/root-consumer/guides/dndev/SETUP_STRIPE.md.example

@@ -0,0 +1,62 @@
+# Stripe Setup Guide
+
+## Prerequisites
+- Stripe account (https://dashboard.stripe.com)
+- `@donotdev/billing` installed
+
+## 1. Get API Keys
+
+1. Go to https://dashboard.stripe.com/apikeys
+2. Copy your **Publishable key** (`pk_test_...`) → `.env`
+3. Copy your **Secret key** (`sk_test_...`) → `supabase/functions/.env` or `functions/.env`
+
+> **Security:** Never commit secret keys. Stripe also supports restricted keys (`rk_test_...`, `rk_live_...`) for tighter permissions.
+
+## 2. Configure Webhook
+
+1. Go to https://dashboard.stripe.com/webhooks
+2. Click **Add endpoint**
+3. Set endpoint URL:
+   - Supabase: `https://{{PROJECT_ID}}.supabase.co/functions/v1/stripe-webhook`
+   - Firebase: `https://europe-west1-{{PROJECT_ID}}.cloudfunctions.net/stripeWebhook` (replace `europe-west1` with your region if different)
+4. Select events:
+   - `checkout.session.completed`
+   - `customer.subscription.created`
+   - `customer.subscription.updated`
+   - `customer.subscription.deleted`
+   - `invoice.payment_succeeded`
+   - `invoice.payment_failed`
+5. Copy the **Signing secret** (`whsec_...`) → `supabase/functions/.env`
+
+## 3. Environment Variables
+
+### App `.env` (public)
+```
+VITE_STRIPE_PUBLISHABLE_KEY=pk_test_...
+```
+
+### Functions `.env` (secret)
+```
+STRIPE_SECRET_KEY=sk_test_...
+STRIPE_WEBHOOK_SECRET=whsec_...
+```
+
+## 4. Test Clocks (Optional)
+
+For subscription testing without waiting for real billing cycles:
+1. Go to https://dashboard.stripe.com/test/test-clocks
+2. Create a test clock
+3. Create customers attached to the test clock
+4. Advance time to trigger billing events
+
+## 5. Verify
+
+```bash
+dndev setup stripe   # Interactive key setup + validation
+dndev doctor         # Health check for all providers
+```
+
+Check that:
+- Publishable key format is valid
+- Secret key format is valid
+- Key modes match (both test or both live)

package/templates/root-consumer/guides/dndev/SETUP_SUPABASE.md.example

@@ -7,7 +7,7 @@
 ## Step 1: Run Supabase Setup
 
 ```bash
-dndev supabase:setup
+dndev setup supabase
 ```
 
 This command:
@@ -114,11 +114,11 @@ Supabase gives you **Auth, Postgres, Storage, and Edge Functions**. It does **no
 
 ## Local Development
 
-- **Against hosted Supabase:** After `supabase:setup`, run `bun dev` — the app talks to your Supabase project.
+- **Against hosted Supabase:** After `dndev setup supabase`, run `bun dev` — the app talks to your Supabase project.
 - **Local Supabase:** Install the [Supabase CLI](https://supabase.com/docs/guides/cli) and run `supabase start` for a local Postgres + Auth + Storage stack. Point `VITE_SUPABASE_URL` and keys to the local instance.
 
 ---
 
 ## Summary
 
-**`dndev supabase:setup`** → paste URL + anon key → **`dn generate sql`** → apply migrations → **`bun dev`**. The adapter normalizes read (snake→camel, ISO) and leaves timestamps to the DB on write.
+**`dndev setup supabase`** → paste URL + anon key → **`dn generate sql`** → apply migrations → **`bun dev`**. The adapter normalizes read (snake→camel, ISO) and leaves timestamps to the DB on write.

package/templates/root-consumer/guides/dndev/SETUP_VERCEL.md.example

@@ -29,7 +29,7 @@ Get the Firebase web config from: **Project Settings → General → Your apps
 ## Step 2: Run Setup
 
 ```bash
-dndev firebase:setup
+dndev setup firebase
 ```
 
 This writes Firebase SDK config to your app's `.env`. The `overlay-vercel` providers.ts initializes the Firebase client SDK.
@@ -173,4 +173,4 @@ See [ENV_SETUP.md → Secrets Philosophy](./ENV_SETUP.md#secrets-philosophy) for
 
 ---
 
-**`dndev firebase:setup` → configure Vercel project → set env vars → `git push`. Vercel deploys automatically.**
+**`dndev setup firebase` → configure Vercel project → set env vars → `git push`. Vercel deploys automatically.**

package/templates/root-consumer/guides/wai-way/WAI_WAY_CLI.md.example

@@ -168,18 +168,17 @@ Present completed spec summary:
 **READ:**
 - `guides/wai-way/page_patterns.md` - Page structure patterns
 
-```bash
-# Create new app
-dndev create-app my-app --preset [from spec]
+**`dndev` is an installed CLI — run directly, never via `bunx` or `npx`.**
 
-# Install dependencies
-cd my-app && bun install
+```bash
+# Create new app (interactive wizard — no --preset flag, it prompts you)
+dndev create-app
 
-# Start emulators
+# Start emulators (if Firebase backend was selected)
 dndev emu start
 
-# Verify it runs
-bun dev
+# Start the dev server
+dndev dev
 ```
 
 ### Step 1.1: Create Page Files

package/templates/root-consumer/guides/wai-way/blueprints/1_scaffold.md.example

@@ -11,14 +11,18 @@
 
 ## Step 1: Create App
 
+**`dndev` is an installed CLI — run directly, never via `bunx` or `npx`.**
+
 ```bash
-dndev create-app my-app --preset [from spec]
-cd my-app && bun install
+# Interactive wizard — prompts for builder, backend, features (no --preset flag)
+dndev create-app
+
+# Start emulators (if Firebase backend was selected)
 dndev emu start
-bun dev
-```
 
-Preset comes from your completed spec (Phase 0).
+# Start the dev server
+dndev dev
+```
 
 ---
 

package/dist/bin/commands/lint.d.ts

@@ -1,11 +0,0 @@
-/**
- * @fileoverview Lint Command Wrapper
- * @description Re-exports lint from tooling for CLI bundling.
- * Each command wrapper is bundled separately as a fully self-contained script.
- *
- * @version 0.0.4
- * @since 0.0.1
- * @author AMBROISE PARK Consulting
- */
-export { lint as main } from '@donotdev/tooling';
-//# sourceMappingURL=lint.d.ts.map

package/dist/bin/commands/lint.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"lint.d.ts","sourceRoot":"","sources":["../../../src/bin/commands/lint.ts"],"names":[],"mappings":"AACA;;;;;;;;GAQG;AAEH,OAAO,EAAE,IAAI,IAAI,IAAI,EAAE,MAAM,mBAAmB,CAAC"}

package/dist/bin/commands/lint.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"lint.js","sourceRoot":"","sources":["../../../src/bin/commands/lint.ts"],"names":[],"mappings":"AAAA,wCAAwC;AACxC;;;;;;;;GAQG;AAEH,OAAO,EAAE,IAAI,IAAI,IAAI,EAAE,MAAM,mBAAmB,CAAC"}

package/dist/bin/commands/staging.d.ts

@@ -1,11 +0,0 @@
-/**
- * @fileoverview Staging Command Wrapper
- * @description Staging is a thin wrapper around deploy with --staging flag.
- * Re-exports deploy from tooling — the staging flag is set by the CLI entry point.
- *
- * @version 0.0.1
- * @since 0.0.1
- * @author AMBROISE PARK Consulting
- */
-export { deploy as main } from '@donotdev/tooling';
-//# sourceMappingURL=staging.d.ts.map

package/dist/bin/commands/staging.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"staging.d.ts","sourceRoot":"","sources":["../../../src/bin/commands/staging.ts"],"names":[],"mappings":"AACA;;;;;;;;GAQG;AAEH,OAAO,EAAE,MAAM,IAAI,IAAI,EAAE,MAAM,mBAAmB,CAAC"}

package/dist/bin/commands/staging.js

@@ -1,12 +0,0 @@
-// packages/cli/src/bin/commands/staging.ts
-/**
- * @fileoverview Staging Command Wrapper
- * @description Staging is a thin wrapper around deploy with --staging flag.
- * Re-exports deploy from tooling — the staging flag is set by the CLI entry point.
- *
- * @version 0.0.1
- * @since 0.0.1
- * @author AMBROISE PARK Consulting
- */
-export { deploy as main } from '@donotdev/tooling';
-//# sourceMappingURL=staging.js.map

package/dist/bin/commands/staging.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"staging.js","sourceRoot":"","sources":["../../../src/bin/commands/staging.ts"],"names":[],"mappings":"AAAA,2CAA2C;AAC3C;;;;;;;;GAQG;AAEH,OAAO,EAAE,MAAM,IAAI,IAAI,EAAE,MAAM,mBAAmB,CAAC"}