@cloudgrid-io/mcp 0.13.0 → 0.14.0

package/src/corpus/templates/subscription-management/AGENTS.md

@@ -0,0 +1,191 @@
+# AGENTS.md — subscription-management (BLUEPRINT)
+
+This is a **blueprint**, not runnable code. It tells an agent how to build a
+self-serve subscription-management app correctly on CloudGrid: a Next.js app
+where a signed-in customer sees their current plan, changes/upgrades/downgrades
+or cancels it, and manages billing (card, invoices) through the Stripe Billing
+Portal — with a Stripe webhook keeping local subscription state in sync, and
+Mongo for persistence. Read this whole file, then build the app under
+`services/web/` following the structure below. Do not skip the CloudGrid wiring
+rules — they are what make it deploy.
+
+Scope note: this is the **manage-what-you-already-have** surface (view plan,
+switch plan, update payment method, cancel), not the acquisition funnel. If the
+user wants the *sign-up + paywall + gated content* flow, that is the
+`membership-site` blueprint; this one owns the ongoing plan/billing lifecycle.
+The two share the same Stripe + Mongo wiring.
+
+The proven persistent shape is `app-with-data` (Next.js + Mongo). This blueprint
+extends it with Stripe subscriptions + the Billing Portal. Fetch that template
+for the Mongo lazy-client and App-Router API pattern:
+`gridctl_fetch("template", "app-with-data")`.
+
+## 1. File tree
+
+Build exactly this layout. **App code MUST live under `services/web/`** — the
+service is named `web`, so the CLI looks for `services/web/`. `path: /` in
+`cloudgrid.yaml` is the URL mount, NOT the filesystem path. Files at the repo
+root fail with `Error: Service directory not found: …/services/web`.
+
+```
+cloudgrid.yaml                                 # name + services.web (nextjs) + needs:{database:true} + vault: (Stripe secrets)
+services/web/package.json                      # next, react, react-dom, mongodb, stripe (+ auth SDK if used, e.g. @clerk/nextjs)
+services/web/middleware.js                     # auth middleware: protects /account/* + the subscription API routes
+services/web/lib/db.js                         # lazy Mongo client from DATABASE_MONGODB_URL (legacy MONGODB_URL fallback)
+services/web/lib/stripe.js                     # lazy Stripe client from process.env.STRIPE_KEY (never top-level)
+services/web/lib/subscription.js               # getSubscription(customerRef): read current plan/status from subscriptions collection
+services/web/lib/plans.js                      # plan catalog: { key, name, price, stripePriceId } for each plan (upgrade/downgrade options)
+services/web/app/layout.js                     # root layout (+ auth provider wrapper if the SDK needs one)
+services/web/app/page.js                       # entry: link to /account (or the plans view for the unsubscribed)
+services/web/app/account/page.js               # THE dashboard: current plan, status, renewal date, "Change plan" + "Manage billing" + "Cancel"
+services/web/app/account/plans.js              # client component: plan cards + change-plan / cancel buttons calling the API
+services/web/app/api/subscription/route.js     # GET current subscription; PATCH to change plan (Stripe subscription update, prorated)
+services/web/app/api/subscription/cancel/route.js  # POST: cancel at period end (or resume) via Stripe
+services/web/app/api/portal/route.js           # POST: create a Stripe Billing Portal session → return url (card, invoices, receipts)
+services/web/app/api/webhook/route.js          # POST: Stripe webhook — upsert subscription state on subscription/invoice events
+```
+
+## 2. Mongo collections + fields
+
+The grid provisions Mongo from `needs: { database: true }`. Use two collections:
+
+**`customers`** — links your app's user to their Stripe customer. (If an auth SDK
+owns identity you may not need a separate profile store, but you DO need the
+user↔`stripeCustomerId` mapping somewhere — keep it here.)
+- `_id` (ObjectId)
+- `userRef` (string, indexed) — your app's user id (auth provider `sub`, or email)
+- `email` (string)
+- `stripeCustomerId` (string, indexed) — the Stripe customer this user maps to
+- `createdAt` (Date)
+
+**`subscriptions`** — the local mirror of Stripe subscription state. The webhook
+writes it; the account dashboard and plan-change API read it. Never trust the
+client for plan/status — read this (kept current by the webhook).
+- `_id` (ObjectId)
+- `userRef` (string, indexed)
+- `stripeCustomerId` (string, indexed)
+- `stripeSubscriptionId` (string, indexed)
+- `planKey` (string) — matches a `key` in `lib/plans.js` (e.g. `"basic"`, `"pro"`)
+- `stripePriceId` (string) — the active Stripe price
+- `status` (string) — `"active" | "trialing" | "past_due" | "canceled" | "incomplete"`
+- `cancelAtPeriodEnd` (boolean) — user asked to cancel but access runs to period end
+- `currentPeriodEnd` (Date) — renewal / lapse date shown on the dashboard
+- `updatedAt` (Date)
+
+## 3. How CloudGrid injects everything (the wiring that matters)
+
+- **Mongo** — declared by `needs: { database: true }`. The deployer provisions
+  shared Mongo and injects the connection string as **`DATABASE_MONGODB_URL`**
+  (plus the legacy **`MONGODB_URL`** alias) at runtime and under `grid dev`.
+  Read `process.env.DATABASE_MONGODB_URL || process.env.MONGODB_URL` **LAZILY,
+  inside the getter** in `lib/db.js` — never at module top level, or `next build`
+  fails when it imports the module for route analysis before the grid injects
+  the var. Never hardcode a connection string. Never set `needs:` and `requires:`
+  together — `requires:` is the deprecated v1 alias.
+- **Secrets (Stripe) → env vars via the `vault:` block.** In `cloudgrid.yaml`
+  the `vault:` block maps each env var to a vault item key:
+  ```yaml
+  vault:
+    STRIPE_KEY: stripe-live-key
+    STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
+  ```
+  Set the vault items ONCE with `gridctl_secrets` (or `grid secrets set`), then
+  the deployer injects each as the named env var (`process.env.STRIPE_KEY`, etc.)
+  at runtime and under `grid dev`. Do NOT commit keys; do NOT set them in
+  `services.web.env` (that block is for non-secret config only). Read them lazily
+  inside `lib/stripe.js` — same rule as the DB. If you add an auth SDK, add
+  `AUTH_PROVIDER_KEY: auth-provider-key` to the vault block too.
+- **Public / non-secret config** — the Stripe *publishable* key
+  (`NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY`) and price ids are not secret; put them
+  in the non-secret `services.web.env` block (or a build-time env), not the
+  vault. An auth SDK's publishable key goes here too.
+- **AI (optional)** — if you add AI features (e.g. churn-reason summaries),
+  declare `needs: { ai: true }` and call the gateway at
+  `process.env.AI_GATEWAY_URL` via `@cloudgrid-io/ai`. Not required for this
+  blueprint.
+
+## 4. Wiring auth + payments
+
+**Auth (identify the customer).** Every subscription action must be tied to a
+known user — otherwise anyone could change anyone's plan.
+1. Add an auth SDK to `services/web/package.json` (e.g. `@clerk/nextjs`, or
+   Auth0) OR use your own session. Server key from the vault
+   (`process.env.AUTH_PROVIDER_KEY`); publishable key from `services.web.env` as
+   `NEXT_PUBLIC_...`.
+2. `services/web/middleware.js` protects `/account/*` and the
+   `/api/subscription*` + `/api/portal` routes — unauthenticated users get
+   redirected to sign-in. Resolve the current `userRef` server-side in each API
+   route and only ever act on THAT user's `stripeCustomerId`.
+
+**Payments (Stripe subscriptions + Billing Portal).**
+1. Add `stripe` to `package.json`. Build a lazy Stripe client in `lib/stripe.js`
+   reading `process.env.STRIPE_KEY` inside the getter.
+2. **Plan catalog** — `lib/plans.js` is the single source of which plans exist and
+   their `stripePriceId`s. The dashboard renders from it; the change-plan API
+   validates the requested plan against it (never accept an arbitrary price id
+   from the client).
+3. **Change plan** — `app/api/subscription/route.js` PATCH: resolve the user's
+   `stripeSubscriptionId` from Mongo, look up the target `stripePriceId` from
+   `lib/plans.js`, call Stripe `subscriptions.update` swapping the item's price
+   with `proration_behavior` set as you want (e.g. `create_prorations`). Do NOT
+   write the new plan to Mongo here — let the resulting webhook be the source of
+   truth so Stripe and Mongo never diverge.
+4. **Cancel / resume** — `app/api/subscription/cancel/route.js` POST: set
+   `cancel_at_period_end: true` (or `false` to resume) on the Stripe
+   subscription. Again, the webhook reconciles Mongo.
+5. **Billing Portal** — `app/api/portal/route.js` POST: create a Stripe Billing
+   Portal session (`billingPortal.sessions.create`) for the user's
+   `stripeCustomerId` with a `return_url` back to `/account`, and return
+   `session.url`. The "Manage billing" button POSTs here and redirects the
+   browser to the returned URL — Stripe hosts card updates, invoices, and
+   receipts, so you don't rebuild them.
+6. **Webhook (source of truth)** — `app/api/webhook/route.js` POST: verify the
+   signature with `process.env.STRIPE_WEBHOOK_SECRET` (read the RAW request body
+   — do not JSON-parse before verifying). On `customer.subscription.created`,
+   `customer.subscription.updated`, `customer.subscription.deleted`, and
+   `invoice.payment_failed` / `invoice.paid`, upsert the `subscriptions` doc
+   keyed by `stripeSubscriptionId` with the new `planKey` / `stripePriceId` /
+   `status` / `cancelAtPeriodEnd` / `currentPeriodEnd`. Register this route's
+   public URL as the webhook endpoint in the Stripe dashboard after deploy.
+
+**Reading state (the dashboard).**
+- `lib/subscription.js` exports `getSubscription(userRef)` → reads the
+  `subscriptions` collection and returns the current plan/status/renewal.
+- `app/account/page.js` is a server component: resolve the signed-in `userRef`,
+  call `getSubscription`, and render the current plan, status, renewal date, and
+  the Change-plan / Manage-billing / Cancel actions. Read state server-side from
+  Mongo; never derive entitlement purely on the client.
+
+## 5. Deploy steps
+
+1. `gridctl_login_status` → `gridctl_login` if needed. Respect the grid picker
+   (ask which grid if the user has more than one).
+2. `gridctl_init` an app `<name>` FIRST — it creates the entity, writes
+   `.cloudgrid/link.json`, and a `cloudgrid.yaml` with empty `services: {}`.
+   `plug` needs a linked directory.
+3. Write the app under `services/web/` and set `cloudgrid.yaml` to the active
+   shape: `name` + `services.web{type: nextjs, path: /}` + `needs:{database:true}`
+   + the `vault:` block.
+4. Set the secrets: `gridctl_secrets` for `stripe-live-key`,
+   `stripe-webhook-secret` (and `auth-provider-key` if you use an auth SDK) — the
+   vault item keys the `vault:` block maps from. Non-secret config (Stripe
+   publishable key, price ids, auth publishable key) → `gridctl_env` /
+   `services.web.env`. Do NOT set `DATABASE_MONGODB_URL` yourself — the grid
+   injects it.
+5. `gridctl_plug` to deploy. A runtime deploy is **ASYNC** — the first response
+   is `status: building`, not a live URL. Poll `gridctl_status` (or the returned
+   poll_url) until live; surface a liveness signal while it builds, never a bare
+   silent wait.
+6. Once live, add the `/api/webhook` URL as the Stripe webhook endpoint, copy
+   the signing secret into the `stripe-webhook-secret` vault item, and configure
+   the Billing Portal in the Stripe dashboard, then re-plug. Return the live app
+   URL (not the build/log link).
+
+## 6. Edition note
+
+A subscription-management app is a built + deployed runtime container, so it
+requires the **local edition** (Claude Desktop / Claude Code) or the CLI. The
+**hosted** edition (Claude Web / hosted MCP) is inline-only and can only publish
+static pages — it CANNOT build this app. On hosted, say so plainly and offer a
+static pricing/plans page (via `gridctl_drop`) instead, then stop the runtime
+path.

package/src/corpus/templates/subscription-management/README.md

@@ -0,0 +1,21 @@
+# subscription-management template — BLUEPRINT
+
+A self-serve subscription-management app: a Next.js app where a signed-in
+customer sees their current plan, upgrades/downgrades or cancels it, and manages
+billing (card, invoices) through the Stripe Billing Portal — with a Stripe
+webhook keeping local subscription state in sync, and grid-shared Mongo for
+persistence. This is a **blueprint** — it ships the `cloudgrid.yaml` and a
+structure guide (`AGENTS.md`), not finished app code. Read `AGENTS.md` for the
+file tree, Mongo collections, and the CloudGrid wiring (Mongo via
+`needs:{database:true}` → `DATABASE_MONGODB_URL`; Stripe secrets via the `vault:`
+block → env vars), then build the app under `services/web/` following it, adapt
+the plans/fields to the user, and deploy (async — poll to a live URL). It
+requires the local edition.
+
+- `cloudgrid.yaml` — active: `name` + `services.web{type: nextjs, path: /}` +
+  `needs:{database:true}` + `vault:` (Stripe secrets → env vars).
+- `AGENTS.md` — the structure guide: file tree, collections, CloudGrid injection,
+  Stripe change-plan / cancel / billing-portal / webhook wiring, deploy steps,
+  edition note.
+
+**blueprint: structure + cloudgrid.yaml, adapt and build.**

package/src/corpus/templates/subscription-management/cloudgrid.yaml

@@ -0,0 +1,236 @@
+# ============================================================================
+# cloudgrid.yaml — Complete Example
+# ============================================================================
+#
+# This file shows EVERY field the platform supports, with comments explaining
+# each one. It is a reference — no real project would use all of these at once.
+#
+# STANDARD: every CloudGrid template ships its cloudgrid.yaml in THIS full form.
+# Uncomment ONLY the fields the archetype needs (always: name + services; plus
+# needs: for runtime apps). Leave everything else commented. Comments are
+# ignored by the parser, so the file deploys to exactly the active fields.
+#
+# Only two fields are required: name and services. Everything else is optional.
+# Full docs: docs/cloudgrid-yaml-reference.md
+# ============================================================================
+
+
+# ─── IDENTITY ───────────────────────────────────────────────────────────────
+
+# Entity slug (REQUIRED). 2-42 chars, lowercase alphanumeric + hyphens.
+# Must start and end with a letter or digit.
+# Becomes part of your public URL: <name>-<4hex>.<org>.cloudgrid.io
+name: subscription-management
+
+# One-line summary. Max 280 chars. If omitted, Grid Brain auto-generates one.
+# description: Order processing API for the e-commerce platform
+
+# Single emoji or short text shown as the entity icon. Max 64 chars.
+# icon: "📦"
+
+# Entity type: 'app' (default) or 'agent'. An agent is an app with an agent: block.
+# kind: app
+
+
+# ─── NETWORKING ─────────────────────────────────────────────────────────────
+
+# Whether this entity serves public HTTP traffic.
+# true = public URL + Ingress (default). false = internal only.
+# expose: true
+
+# Additional domain names this entity serves on (the platform URL is always active).
+# custom_domains:
+#   - orders.example.com
+#   - shop.example.com
+
+
+# ─── HEALTH PROBE (entity-level override) ──────────────────────────────────
+
+# Override the default health check for the entire entity.
+# probe:
+#   path: /healthz               # HTTP path to probe (default: /).
+#   expected: "<500"             # '<500' (default), '200', '2xx'.
+
+
+# ─── DEPLOY NOTIFICATIONS ──────────────────────────────────────────────────
+
+# Slack notification to the org's default channel on deploy failure.
+# true = notify (default), false = silent.
+# notify: true
+
+
+# ─── SCALING ────────────────────────────────────────────────────────────────
+
+# Replica scaling intent.
+#   'auto'  — platform decides from the grid tier (default).
+#   'alert' — single-replica, emit a SPOF warning at plug time.
+#   1-10    — explicit replica count, clamped to the grid max.
+# scale: auto
+
+
+# ─── INFRASTRUCTURE NEEDS ──────────────────────────────────────────────────
+#
+# Declare infrastructure; the platform provisions it and injects connection
+# details as env vars. Nine needs: database, cache, kv, queue, pubsub, vector,
+# object_storage, disk, ai. Simplest form is `true`.
+#
+# needs:
+#   # database — MongoDB. Injects DATABASE_MONGODB_URL (+ legacy MONGODB_URL).
+#   #   true | pool | dedicated | { tier: external, secret: MY_DB }
+#   database: true
+#   # cache — Redis, LRU eviction (derived data). Injects CACHE_REDIS_URL (+ REDIS_URL).
+#   #   true | redis | { engine: external, secret: MY_REDIS_URL }
+#   cache: true
+#   # kv — Redis, no eviction (durable: flags, idempotency). Injects KV_REDIS_URL.
+#   kv: true
+#   # queue — Redis job-queue substrate (BullMQ). Injects QUEUE_REDIS_URL.
+#   queue: true
+#   # pubsub — Redis broadcast pub/sub. Injects PUBSUB_REDIS_URL.
+#   pubsub: true
+#   # vector — pgvector on Postgres. Injects VECTOR_PGVECTOR_URL (+ PGVECTOR_URL).
+#   #   true | pgvector | { engine: pgvector, dim: 1536 }
+#   vector: pgvector
+#   # object_storage — GCS bucket. Injects OBJECT_STORAGE_GCS_BUCKET, _GCS_REGION.
+#   #   true | { size: 10Gi }
+#   object_storage: true
+#   # disk — persistent FS mount (PVC). Injects DISK_PATH. Pins to 1 replica.
+#   #   true | { size: 1Gi, mount: /var/data }  (forbidden: /proc /sys /dev)
+#   disk: true
+#   # ai — AI Gateway via @cloudgrid-io/ai. Injects AI_GATEWAY_URL. true | false.
+#   ai: true
+
+
+# ─── INTER-ENTITY COMMUNICATION ────────────────────────────────────────────
+
+# Entities this app calls (outbound). Service-account token injected per pair.
+# calls:
+#   - org:atomic/billing-api
+
+# Inbound caller policy — who can call YOUR entity.
+# callers:
+#   policy: auto                 # 'auto' | 'manual' (default).
+#   scope: org                   # 'org' (default) | 'space' | 'explicit'.
+#   fallback: deny               # 'deny' (default) | 'warn'.
+#   # allowed_apps:              # required only when scope: explicit
+#   #   - org:atomic/frontend
+
+
+# ─── VAULT ──────────────────────────────────────────────────────────────────
+
+# Map org vault items to env vars. Keys UPPER_SNAKE_CASE; values = vault item keys.
+# Self-serve subscription management needs Stripe secrets injected as env vars —
+# this is the CloudGrid-correct way. Set the vault items once (grid secrets set),
+# then the deployer injects each as the named env var at runtime and under
+# `grid dev`. Add AUTH_PROVIDER_KEY here too if you use an auth SDK (e.g. Clerk).
+vault:
+  STRIPE_KEY: stripe-live-key                  # Stripe secret key (billing portal sessions + subscription updates)
+  STRIPE_WEBHOOK_SECRET: stripe-webhook-secret # verifies Stripe webhook signatures
+
+
+# ─── CONNECTORS AND HOOKS ──────────────────────────────────────────────────
+
+# connectors:
+#   - id: team-slack
+#     target: org                # 'system' | 'org'.
+#     channel: "#deploys"
+# hooks:
+#   - on: deploy.failed          # release.published | deploy.failed | feedback.received | entity.created
+#     via: team-slack
+#     template: "Deploy failed for {entity_name}: {error}"
+#     channel: "#alerts"
+# triggers:
+#   - from: team-slack
+#     event: message
+#     channel: "#support"
+#     route: /webhooks/slack
+
+
+# ─── LOCAL DEVELOPMENT ──────────────────────────────────────────────────────
+
+# Config for `grid dev`. Redact fields in dev data snapshots.
+# dev:
+#   snapshot:
+#     mask:
+#       - users.email
+#       - users.phone
+
+
+# ─── AGENT METADATA ────────────────────────────────────────────────────────
+
+# An agent is an app with kind: agent (above) and an agent: block.
+# agent:
+#   purpose: Sync customer data from external CRM every night
+#   schedule: "0 2 * * *"
+#   trigger: webhook
+
+
+# ─── PRIVATE RESOURCE AUTO-DEPENDENCIES ────────────────────────────────────
+
+# When true (default), private resources are auto-injected as depends_on.
+# auto_depends_on_private_requires: true
+
+
+# ─── SERVICES (REQUIRED) ───────────────────────────────────────────────────
+#
+# At least one service is required. Key = service name (slug rules).
+# Types: node, nextjs, python, static, cron.
+#
+services:
+  web:
+    # type (REQUIRED): node | nextjs | python | static | cron
+    type: nextjs
+    # HTTP route: '/' | '/api' | false (internal) | omitted (=false + warning).
+    # Only one service per entity can claim '/'.
+    path: /
+    # Container port (default 8080; read process.env.PORT). Not for cron.
+    # port: 3000
+    # nextjs only: base_image: distroless (default) | alpine
+    # base_image: distroless
+    # node only: lang: javascript (default) | typescript
+    # lang: typescript
+    # Custom source location (default services/<name>/). '.' = project root.
+    # source:
+    #   path: src/worker
+    # Health probe: false/omitted (TCP) | true (/health) | "/path" | {path,expected}
+    # health:
+    #   path: /api/health
+    #   expected: "200"
+    # Static runtime env vars (strings). Reserved: PORT, APP_NAME, SERVICE_NAME,
+    # NODE_ENV, MONGODB_URL, REDIS_URL, AI_GATEWAY_URL, N8N_WEBHOOK_URL, CLOUDGRID_*.
+    # env:
+    #   LOG_LEVEL: info
+    # Sibling services/private resources that must be Ready first (no cron, no cycles).
+    # depends_on:
+    #   - worker
+    # Per-service needs override (merges with app-level needs).
+    # needs:
+    #   queue: true
+    # Static-only build step:
+    # build:
+    #   command: npm run build
+    #   output: dist
+    #   env:
+    #     VITE_API_URL: https://api.example.com
+    # node_version: "22"          # static build step: '18'|'20'|'22'|'24' (quoted)
+    # Cron-only: schedule (REQUIRED), timezone (UTC|EST|PST), run (job | https URL)
+    # schedule: "0 9 * * 1"
+    # timezone: UTC
+    # run: job
+    # Verbose per-service persistence (prefer needs.disk):
+    # persist:
+    #   - name: scratch
+    #     path: /tmp/scratch
+    #     size: 500Mi
+
+
+needs:
+  database: true
+
+
+# ============================================================================
+# NOTES
+# - NOT here: org:/entity_id: (→ .cloudgrid/link.json), secrets (→ grid secrets set),
+#   Dockerfile (platform generates from services.*.type).
+# - Deploy: grid plug   |   Local with grid resources: grid dev
+# - Full reference: docs/cloudgrid-yaml-reference.md  |  CLI: docs/cli-reference.md
+# ============================================================================

package/src/corpus/templates/subscription-management/index.md

@@ -0,0 +1,73 @@
+# Template: subscription-management (BLUEPRINT — Next.js + Stripe + Mongo)
+
+A self-serve subscription-management app. **Blueprint, not finished code**: it
+ships the `cloudgrid.yaml` and a structure guide (`AGENTS.md`) so an agent can
+build it correctly on CloudGrid — a Next.js app where a signed-in customer views
+their current plan, changes/upgrades/downgrades or cancels it, and manages
+billing through the Stripe Billing Portal, with a Stripe webhook syncing local
+state and grid-shared Mongo. Read `AGENTS.md`, build the app under
+`services/web/`, adapt plans/fields, then deploy (async — poll to a live URL).
+Local edition only.
+
+This is the **manage-what-you-already-have** surface (view / switch plan, update
+payment method, cancel). For the sign-up + paywall + gated-content acquisition
+flow, use the `membership-site` blueprint — the two share the same Stripe + Mongo
+wiring.
+
+**Fetch the bundle:**
+- `gridctl_fetch("template", "subscription-management")` — this blueprint (`cloudgrid.yaml` + `AGENTS.md`).
+- `gridctl_fetch("template", "app-with-data")` — the proven Next.js + Mongo shape to extend (lazy db client, App-Router API).
+
+**Key rules:**
+
+1. **Blueprint — read `AGENTS.md` first.** It has the file tree, Mongo
+   collections (`customers`, `subscriptions`), CloudGrid injection table, and the
+   Stripe change-plan / cancel / billing-portal / webhook wiring. Build following
+   it; do not invent structure.
+2. **App code MUST live under `services/web/`.** `path: /` is the URL mount, NOT
+   the filesystem path. Root files fail with `Service directory not found`.
+3. **Mongo via `needs:{database:true}`** → the grid injects
+   `DATABASE_MONGODB_URL` (legacy `MONGODB_URL` fallback). Read it LAZILY inside
+   the getter, never at module top level (top-level read fails `next build`).
+4. **Secrets via the `vault:` block** → env vars. `STRIPE_KEY` and
+   `STRIPE_WEBHOOK_SECRET` map to vault items; set them with `gridctl_secrets`,
+   and the deployer injects them at runtime. Read lazily; do not commit keys or
+   put secrets in `services.web.env` (publishable key + price ids go there).
+5. **The webhook is the source of truth.** Change-plan / cancel APIs call Stripe;
+   the `/api/webhook` route reconciles the `subscriptions` collection so Stripe
+   and Mongo never diverge. Read plan/status server-side from Mongo, never trust
+   the client. Validate requested plans against `lib/plans.js`.
+6. **Never set `needs:` and `requires:` together** — `requires:` is the
+   deprecated v1 alias.
+
+## cloudgrid.yaml (active fields)
+
+```yaml
+# On disk this file is the full-annotated reference (templates/_cloudgrid.yaml.reference) with EVERY
+# field present as a comment; only the fields below are uncommented, so it
+# deploys to exactly these active fields.
+name: subscription-management
+services:
+  web:
+    type: nextjs
+    path: /
+needs:
+  database: true
+vault:
+  STRIPE_KEY: stripe-live-key
+  STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
+```
+
+> **Capability:** `needs: { database: true }` → the deployer provisions Mongo and
+> injects `DATABASE_MONGODB_URL` (+ legacy `MONGODB_URL`). The `vault:` block maps
+> Stripe secrets to env vars — the CloudGrid-correct way to inject credentials.
+> `requires:` is the deprecated v1 alias; don't mix it with `needs:`. See the
+> capability-map for the full injection table.
+
+## Deploy (async, local edition)
+
+`gridctl_init` first (creates the entity + link.json), write the app under
+`services/web/`, set the vault secrets with `gridctl_secrets`, `gridctl_plug`
+(async — poll `gridctl_status` to a live URL), then register the `/api/webhook`
+URL in Stripe, configure the Billing Portal, and re-plug. Re-plug the same entity
+to update the same URL.