@cloudgrid-io/mcp 0.13.0 → 0.14.0

package/src/corpus/templates/travel-booking/AGENTS.md

@@ -0,0 +1,207 @@
+# AGENTS.md — travel-booking (BLUEPRINT)
+
+A structure guide for building a travel booking portal on CloudGrid — search and
+book flights and hotels, pay with Stripe, manage trips. This is a **blueprint**,
+not runnable app code: it tells you the exact file tree, data model, and
+CloudGrid wiring to build so it deploys correctly. Build the app yourself
+following this guide — do not expect prewritten routes.
+
+The proven runtime shape is the same as `app-with-data` (Next.js + Mongo under
+`services/web/`); this blueprint layers a travel domain (flights, hotels, trips,
+bookings), Stripe payments, an auth provider, and a trip-reminder cron on top.
+
+---
+
+## 1. File tree
+
+App code MUST live under `services/<name>/` — `path:` in `cloudgrid.yaml` is the
+URL mount, NOT the filesystem path. The service named `web` → the CLI looks for
+`services/web/`. Files at the repo root fail with
+`Error: Service directory not found: …/services/web`.
+
+```
+cloudgrid.yaml                                  # name + services.web (nextjs) + needs:{database:true} + vault:
+AGENTS.md                                       # this guide
+services/web/package.json                       # next, react, react-dom, mongodb, stripe, auth provider SDK
+services/web/lib/db.js                          # lazy Mongo client from DATABASE_MONGODB_URL (legacy MONGODB_URL fallback)
+services/web/lib/inventory.js                   # flight/hotel search + seat/room availability check (core logic)
+services/web/lib/stripe.js                      # lazy Stripe client from process.env.STRIPE_KEY (vault-injected)
+services/web/lib/auth.js                        # auth-provider server helpers (session, current user) from AUTH_PROVIDER_KEY
+services/web/app/layout.js                      # root layout + inline CSS
+services/web/app/page.js                        # server component: search form (origin/dest, dates, guests)
+services/web/app/search/page.js                 # results: matching flights + hotels for the query
+services/web/app/trips/page.js                  # "my trips" — the signed-in user's bookings
+services/web/app/checkout/[bookingId]/page.js   # review + pay (redirects to Stripe Checkout)
+services/web/app/search-form.js                 # client component: query builder → /search
+services/web/app/api/flights/route.js           # GET search flights { origin, dest, date, pax }
+services/web/app/api/hotels/route.js            # GET search hotels { city, checkIn, checkOut, guests }
+services/web/app/api/bookings/route.js          # GET my bookings; POST create (holds inventory, starts Stripe checkout)
+services/web/app/api/bookings/[id]/route.js     # GET one; PATCH modify; DELETE cancel
+services/web/app/api/webhooks/stripe/route.js   # POST Stripe webhook: on checkout.session.completed → confirm booking
+#
+# ── CRON (intended shape, NOT yet deployable — see §7 + platform issue #1543) ──
+# services/reminders/package.json                # mongodb (+ email/SMS SDK)
+# services/reminders/index.js                     # batch job: send trip reminders, sweep abandoned holds
+```
+
+---
+
+## 2. MongoDB collections + fields
+
+The grid provisions shared Mongo from `needs: { database: true }`. Suggested
+collections (all `_id` is a Mongo ObjectId; store dates as real `Date`s, in UTC):
+
+**`flights`** — bookable flight inventory.
+- `carrier` (string) — e.g. "AA"
+- `flightNumber` (string)
+- `origin` / `destination` (string) — IATA codes, e.g. "SFO" / "JFK"
+- `departAt` / `arriveAt` (Date, UTC)
+- `priceCents` (number) — fare per seat
+- `seatsTotal` / `seatsBooked` (number) — availability = total − booked
+- `active` (boolean)
+
+**`hotels`** — bookable hotel inventory.
+- `name` (string)
+- `city` (string)
+- `roomType` (string) — e.g. "standard-king"
+- `pricePerNightCents` (number)
+- `roomsTotal` (number) — capacity for a given night
+- `active` (boolean)
+
+**`bookings`** — a reserved flight or hotel stay. Source of truth for inventory.
+- `type` (string) — `flight` | `hotel`
+- `itemId` (ObjectId → flights | hotels)
+- `customerId` (string) — auth-provider user id, or null for guest
+- `customerEmail` (string) — for the reminder + confirmation
+- `startAt` / `endAt` (Date, UTC) — departure/arrival, or check-in/check-out
+- `quantity` (number) — seats, or room-nights
+- `amountCents` (number) — total charged
+- `status` (string) — `pending` (inventory held, awaiting payment) → `confirmed`
+  (paid) → `cancelled` | `completed`
+- `stripeSessionId` (string, nullable) — links to the Checkout session
+- `reminderSentAt` (Date, nullable) — set by the reminder cron; prevents dupes
+- `createdAt` (Date)
+
+**`trips`** (optional) — groups one customer's bookings into an itinerary.
+- `customerId` (string)
+- `name` (string) — e.g. "NYC — March"
+- `bookingIds` (ObjectId[] → bookings)
+
+**Overbooking guard:** availability for a flight is
+`seatsTotal − seatsBooked − (pending holds)`; for a hotel it is `roomsTotal`
+minus overlapping `confirmed`/`pending` bookings for each night in
+`[checkIn, checkOut)`. Enforce it at write time inside a guarded update — e.g.
+`updateOne({ _id, $expr: { $lt: ["$seatsBooked", "$seatsTotal"] } }, { $inc: { seatsBooked: qty } })`
+so two concurrent requests cannot oversell the same seats (the loser matches 0
+docs → return 409). `inventory.js` runs the search queries and computes remaining
+availability.
+
+---
+
+## 3. How CloudGrid injects things
+
+You do NOT provision infra or set connection strings/secrets by hand. Declared in
+`cloudgrid.yaml`, the platform injects env vars at `grid dev` and after `grid plug`:
+
+- **Database (`needs: { database: true }`)** → `DATABASE_MONGODB_URL` (plus the
+  legacy `MONGODB_URL` alias). Read it **lazily inside a getter**, never at module
+  top level — a top-level read fails `next build`, which imports the module for
+  route analysis before the grid injects the var:
+  ```js
+  // services/web/lib/db.js
+  const uri = process.env.DATABASE_MONGODB_URL || process.env.MONGODB_URL;
+  ```
+- **Secrets (`vault:` block)** → each mapped item becomes the named env var:
+  `STRIPE_KEY`, `STRIPE_WEBHOOK_SECRET`, `AUTH_PROVIDER_KEY`. Add the underlying
+  vault items with `grid secrets set <item> <value>` (or the vault UI) BEFORE
+  plug, so resolution succeeds. Never hardcode a key; never commit `.env`.
+- **AI (`needs: { ai: true }`, if you add it)** → `AI_GATEWAY_URL`, used via
+  `@cloudgrid-io/ai`. Optional — e.g. a natural-language "plan my trip" search
+  assistant. Not required for a basic portal.
+
+Read every injected var lazily (inside getters), same rule as the DB.
+
+---
+
+## 4. Wiring auth + payments
+
+**Auth (provider SDK — Clerk / Auth0 / similar).** Put the secret key in the
+`vault:` block as `AUTH_PROVIDER_KEY` and read it lazily in
+`services/web/lib/auth.js`. Use the provider's Next.js middleware/server helpers
+to gate: booking creation (attach `customerId`), "my trips", and any admin
+inventory management. Public flight/hotel search can stay unauthenticated. Guest
+booking is allowed if you capture `customerEmail` and leave `customerId` null.
+Store only the provider's user id in Mongo — never mirror passwords.
+
+**Payments (Stripe).** Put the live key in `vault:` as `STRIPE_KEY` and the
+webhook signing secret as `STRIPE_WEBHOOK_SECRET`; read both lazily in
+`services/web/lib/stripe.js`. Flow:
+1. `POST /api/bookings` — validate inventory is still available, insert the
+   booking as `status: "pending"` and hold inventory via the guarded `$inc`
+   update, then create a Stripe **Checkout Session** for `amountCents`, store
+   `stripeSessionId` on the booking, and return the session URL for the client to
+   redirect to.
+2. `POST /api/webhooks/stripe` — verify the signature with
+   `STRIPE_WEBHOOK_SECRET`, and on `checkout.session.completed` flip the matching
+   booking to `status: "confirmed"`. This webhook — not the browser redirect — is
+   the source of truth for payment. Expire/cancel stale `pending` bookings so held
+   inventory is released if checkout is abandoned (a job for the reminder cron, or
+   an on-read sweep).
+
+---
+
+## 5. Deploy steps
+
+1. `grid init` — scaffolds the entity + `.cloudgrid/link.json`; writes a
+   `cloudgrid.yaml` with an empty `services: {}`. Run this FIRST (plug needs a
+   linked directory).
+2. Fill it in: build the files under `services/web/` and set `cloudgrid.yaml` to
+   this template's shape (`services.web` nextjs + `needs: { database: true }` +
+   the `vault:` block).
+3. `grid secrets set stripe-live-key <sk_live_…>` and the other vault items
+   (`stripe-webhook-secret`, `auth-provider-key`), so the `vault:` mappings
+   resolve at deploy.
+4. (Optional) `grid dev` — runs Next.js locally with `DATABASE_MONGODB_URL` and
+   the vault env vars injected against dev resources. Good for testing the search
+   + availability logic before shipping.
+5. `grid plug` — builds + deploys. A runtime deploy is **async**: the first
+   response is `status: "building"`, not a live URL. Poll `grid status` (or the
+   returned poll_url) until live; surface a liveness signal while it builds, never
+   a bare silent wait. Return the live app URL only once it is up.
+6. Iterate by re-plugging the SAME entity — it updates the same URL.
+
+---
+
+## 6. Edition note
+
+This is a built + deployed container (runtime app), so it requires the **local
+edition** (Claude Desktop / Claude Code) or the CLI. The **hosted edition**
+(Claude Web / hosted MCP) is inline/static-only and CANNOT build a runtime app —
+on hosted, the most you can ship is a static preview page, not the real booking
+backend.
+
+---
+
+## 7. Trip-reminder cron — intended shape, NOT yet deployable (platform issue #1543)
+
+The design calls for a scheduled job that sends trip reminders (e.g. check-in /
+departure reminders 24h before `startAt`) and sweeps abandoned `pending` bookings
+back into inventory.
+
+**Intended shape** (mirrors the commented `reminders:` service in
+`cloudgrid.yaml`):
+- A second service `services/reminders/` of `type: cron`, `run: job` (batch, no
+  HTTP), on a `schedule` like `0 * * * *` (hourly).
+- On each run: connect to Mongo via the same `DATABASE_MONGODB_URL`; find
+  `confirmed` bookings whose `startAt` is within a reminder window and
+  `reminderSentAt` is null; send via an email/SMS provider (key from `vault:`);
+  set `reminderSentAt`. Also cancel `pending` bookings older than the hold timeout
+  and release their held seats/rooms (`$inc` the inventory back).
+
+**Status: PENDING.** cron-service deploy is currently blocked by **platform issue
+#1543** — `grid plug` will reject a `type: cron` service until it lands. Keep the
+`reminders:` service COMMENTED in `cloudgrid.yaml` and ship the `web` service
+alone for now. Until #1543 is fixed, run reminders as a stopgap: an on-read sweep
+inside `GET /api/bookings`, or an external scheduler hitting a protected
+`POST /api/cron/reminders` route on the web service. Swap to the real cron service
+once the issue is resolved.

package/src/corpus/templates/travel-booking/README.md

@@ -0,0 +1,17 @@
+# travel-booking template — flights + hotels booking portal (BLUEPRINT)
+
+A blueprint for a persistent travel booking portal on CloudGrid: a Next.js app
+under `services/web/` backed by grid-shared Mongo (`flights`, `hotels`,
+`bookings`, `trips` collections) with search + availability logic, Stripe
+checkout for paid bookings, an auth provider for accounts, and a trip-reminder
+cron for scheduled notifications. It exists because trips and bookings must
+survive refresh and be shared across sessions — a runtime app, not a static page
+— and because the payment + scheduling wiring is CloudGrid-specific
+(vault-injected secrets, injected `DATABASE_MONGODB_URL`, a cron service).
+
+> **This is a blueprint: structure + cloudgrid.yaml, adapt and build.** It ships
+> the annotated `cloudgrid.yaml` and `AGENTS.md` (file tree, data model, and
+> CloudGrid wiring) — NOT prewritten app code. Read `AGENTS.md`, then build the
+> app under `services/web/` following it. Note: the trip-reminder **cron service
+> is not yet deployable** (platform issue #1543) — see `AGENTS.md` §7 for the
+> intended shape and the stopgap.

package/src/corpus/templates/travel-booking/cloudgrid.yaml

@@ -0,0 +1,249 @@
+# ============================================================================
+# 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: travel-booking
+
+# 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.
+# A travel-booking portal needs payment + auth provider secrets. These are the
+# CloudGrid-correct way to inject them — the platform resolves each vault item and
+# sets the named env var at runtime. Add the vault items with `grid secrets set`
+# (or via the vault UI) BEFORE plug so resolution succeeds.
+vault:
+  STRIPE_KEY: stripe-live-key
+  STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
+  AUTH_PROVIDER_KEY: auth-provider-key
+
+
+# ─── 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
+
+  # ─── CRON SERVICE (INTENDED SHAPE — NOT YET DEPLOYABLE) ───────────────────
+  # A travel-booking portal needs a scheduled job to send trip reminders (e.g.
+  # check-in / departure reminders) and to sweep abandoned pending bookings back
+  # into inventory. This is the intended shape. cron deploy is currently PENDING
+  # platform issue #1543 — do NOT uncomment this yet; plug will reject a cron
+  # service until #1543 lands. See AGENTS.md §7 for the reminder-job design.
+  # reminders:
+  #   type: cron
+  #   schedule: "0 * * * *"      # hourly: scan for trips needing a reminder
+  #   timezone: UTC
+  #   run: job                   # runs services/reminders/ as a batch job (no HTTP)
+
+
+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/travel-booking/index.md

@@ -0,0 +1,88 @@
+# Template: travel-booking (BLUEPRINT — Next.js + Mongo flights/hotels portal)
+
+A blueprint for a travel booking portal — search and book flights and hotels, pay
+with Stripe, manage trips. Data lives in grid-shared MongoDB so trips and bookings
+survive refresh and are shared across sessions — a runtime app, not a static page.
+This bundle ships the annotated `cloudgrid.yaml` and the `AGENTS.md` structure
+guide, NOT prewritten app code.
+
+**This is a blueprint: structure + cloudgrid.yaml, adapt and build.** Fetch it,
+read `AGENTS.md`, then build the app under `services/web/` following the file tree
+and data model there. The proven runtime shape is the same as `app-with-data`
+(lazy Mongo client under `services/web/`).
+
+**Key rules:**
+
+1. **Service code MUST live under `services/<name>/`, not the repo root.** `path:`
+   in `cloudgrid.yaml` is the URL mount, NOT the filesystem path. The service
+   named `web` → the CLI looks for `services/web/`. Root files fail with
+   `Error: Service directory not found: …/services/web`.
+2. **Read injected vars LAZILY (inside getters), never at module top level.** The
+   grid injects `DATABASE_MONGODB_URL` (legacy `MONGODB_URL` alias) from
+   `needs: { database: true }`, and the `vault:` secrets (`STRIPE_KEY`,
+   `STRIPE_WEBHOOK_SECRET`, `AUTH_PROVIDER_KEY`) as env vars. A top-level read
+   fails `next build`. Never hardcode a key; never commit a secret.
+3. **Declare the datastore with `needs: { database: true }`** — the canonical
+   shape. `requires:` is the deprecated v1 alias; don't author new yaml with it,
+   and never set `needs:` and `requires:` together (the validator rejects it).
+4. **Payment/auth secrets go through the `vault:` block**, resolved to env vars
+   at deploy — add the vault items with `grid secrets set` before plug.
+5. **The trip-reminder cron service is NOT yet deployable** (platform issue
+   #1543). Keep the `reminders:` cron COMMENTED and ship `web` alone; see
+   `AGENTS.md` §7.
+
+## cloudgrid.yaml
+
+```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. (A commented `reminders:` cron service
+# shows the intended — not-yet-deployable — shape; see AGENTS.md §7.)
+name: travel-booking
+vault:
+  STRIPE_KEY: stripe-live-key
+  STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
+  AUTH_PROVIDER_KEY: auth-provider-key
+services:
+  web:
+    type: nextjs
+    path: /
+needs:
+  database: true
+```
+
+> **Capability:** need is `database: true` — the deployer provisions Mongo and
+> injects `DATABASE_MONGODB_URL` (plus the legacy `MONGODB_URL` alias). Secrets
+> come from the `vault:` block as env vars. See the capability-map for the full
+> injection table.
+
+## AGENTS.md — the structure guide
+
+The heart of this blueprint. Read it before building. It covers:
+
+1. **File tree** — `services/web/{app/, lib/, api routes, package.json}` with a
+   search flow, inventory + Stripe + auth libs, and the API routes (flights /
+   hotels / bookings / Stripe webhook).
+2. **Mongo collections + fields** — `flights`, `hotels`, `bookings`, `trips`,
+   plus the guarded-`$inc` overbooking rule that prevents overselling seats/rooms.
+3. **CloudGrid injection** — `DATABASE_MONGODB_URL` for Mongo, `vault:` → env vars
+   for secrets, `AI_GATEWAY_URL` for ai.
+4. **Auth + payments wiring** — provider SDK from `AUTH_PROVIDER_KEY`; Stripe
+   checkout + signature-verified webhook from `STRIPE_KEY` /
+   `STRIPE_WEBHOOK_SECRET`.
+5. **Deploy steps** — `grid init` → fill → `grid secrets set` → `grid plug` →
+   poll to live.
+6. **Edition note** — runtime app → local edition only (hosted is static-only).
+7. **Trip-reminder cron** — intended shape + the platform-issue-#1543 PENDING note
+   and stopgap.
+
+## Adapt it
+
+- Rename `flights` / `hotels` / `bookings` collections and fields to your domain
+  (cars, tours, activities, packages).
+- Swap the auth provider (Clerk / Auth0 / …) and payment flow (or drop Stripe for
+  free holds — skip checkout, mark `confirmed`).
+- Add `needs: { cache: true }` only if you actually need Redis (e.g. inventory
+  hold locks or search caching).
+- Wire the trip-reminder cron once platform issue #1543 lands; until then use the
+  stopgap in `AGENTS.md` §7.