@cloudgrid-io/mcp 0.13.0 → 0.14.0

package/src/corpus/workflows/marketplace.md

@@ -0,0 +1,123 @@
+---
+name: marketplace
+when: "marketplace, multi-vendor platform, two-sided marketplace"
+needs: database
+deploy: runtime
+editions: local
+kind: blueprint
+capabilities_note: "persistent — needs a database (Mongo) and payment/auth secrets. Runtime app, async build, local edition only. Declare the canonical needs:{database:true}; the deployer injects DATABASE_MONGODB_URL (+legacy MONGODB_URL). Map Stripe + auth secrets with a vault: block (STRIPE_KEY / STRIPE_WEBHOOK_SECRET / AUTH_PROVIDER_KEY) and grid secrets set the values."
+summary: "A BLUEPRINT for a two-sided / multi-vendor marketplace — vendors, listings, orders, seller auth with roles, Stripe Connect payouts, and commission logic on persistent Next.js + Mongo. This is not fill-in-the-blanks app code; it ships structure + cloudgrid.yaml. Fetch the template, read AGENTS.md for the file tree / collections / CloudGrid wiring (needs + vault), then BUILD the app under services/web/ following it, and deploy async to a live URL (local edition only)."
+---
+
+# Workflow: marketplace
+
+The user wants a two-sided / multi-vendor marketplace — many vendors listing
+products, buyers ordering, the platform taking a commission and paying sellers
+out. That is a **persistent runtime app** (Next.js + the grid's shared Mongo) with
+three layered concerns: **seller auth with roles**, **Stripe Connect payouts**,
+and **commission logic**. It is the `app-with-data` shape plus auth + payments.
+
+**This is a BLUEPRINT.** Unlike a fill-in-the-blanks template, it ships
+*structure* — a `cloudgrid.yaml` and an `AGENTS.md` structure guide — not finished
+app code. The recipe is: fetch it, **read `AGENTS.md`**, then **build** the app
+following it. Be honest that a runtime deploy is async and needs the local edition.
+
+## 1. Edition check FIRST (hard gate)
+
+A marketplace is a built + deployed container (Next.js + Mongo + Stripe). It
+requires the **local edition** (Claude Desktop / Claude Code) or the CLI.
+
+- **Hosted edition (Claude Web / hosted MCP):** you CANNOT build a runtime app —
+  hosted is inline-only and can only publish static pages. Tell the user plainly,
+  offer a **static storefront mockup** instead, and STOP the runtime path here.
+- **Local edition:** continue.
+
+## 2. Auth + grid
+
+1. Ensure signed in: `gridctl_login_status`; if not, `gridctl_login`.
+2. A grid is required. Respect the grid picker: if the user has more than one
+   grid, ask which to use; do not assume a target.
+
+## 3. Fetch the blueprint and READ AGENTS.md
+
+`gridctl_fetch("template", "marketplace")`. The deliverable is the **`AGENTS.md`
+structure guide** — read it before writing anything. It defines:
+- the `services/web/` file tree (pages, API routes, `lib/`),
+- the Mongo collections (`vendors`, `listings`, `orders`) + fields,
+- the CloudGrid injection table (needs + vault + AI gateway),
+- how to wire auth (Clerk/Auth0 + a `role` claim) and payments (Stripe Connect
+  onboarding, Checkout with `application_fee` + `transfer_data.destination`, and a
+  signature-verified webhook),
+- the deploy flow.
+
+There is no app code to copy — you generate it from the guide.
+
+## 4. Scaffold + fill cloudgrid.yaml
+
+`gridctl_init` an app `<name>` FIRST (creates the entity + `.cloudgrid/link.json`
+and a starter `cloudgrid.yaml` with empty `services:{}`; `plug` needs a linked
+directory). Then put the app under **`services/web/`** and set `cloudgrid.yaml` to
+the blueprint's active fields:
+
+```yaml
+name: my-marketplace
+services:
+  web:
+    type: nextjs
+    path: /
+needs:
+  database: true
+vault:
+  STRIPE_KEY: stripe-live-key
+  STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
+  AUTH_PROVIDER_KEY: auth-provider-key
+```
+
+**App code MUST live under `services/<name>/`** — `path:` is the URL mount, NOT
+the filesystem path. **Declare `needs: { database: true }`** (canonical) — the
+deployer provisions Mongo and injects `DATABASE_MONGODB_URL` (+ legacy
+`MONGODB_URL`). `requires:` is the deprecated v1 alias; never author it and never
+set `needs:` and `requires:` together (the validator rejects the combination).
+
+## 5. Build the app following AGENTS.md
+
+Generate the files under `services/web/` per the guide:
+- **Lazy getters** for injected values — read `process.env.DATABASE_MONGODB_URL`
+  (legacy `MONGODB_URL` fallback) and `process.env.STRIPE_KEY` **inside** a getter,
+  never at module top level (a top-level read fails `next build`).
+- Auth SDK (Clerk/Auth0) in `lib/auth.js` from `AUTH_PROVIDER_KEY`; role-gate the
+  seller dashboard + seller API routes in `middleware.js`.
+- Stripe Connect: onboarding account links, Checkout with the platform fee routed
+  via `application_fee_amount` + `transfer_data.destination`, and a webhook that
+  verifies the signature with `STRIPE_WEBHOOK_SECRET` before marking orders paid.
+- Commission as a pure function (`lib/commission.js`); store money as integer cents.
+
+## 6. Config / secrets
+
+- Map secrets in the `vault:` block (done above), then **store the values**:
+  `grid secrets set stripe-live-key sk_live_…`,
+  `grid secrets set stripe-webhook-secret whsec_…`,
+  `grid secrets set auth-provider-key …`. Non-secret public config → `gridctl_env`.
+- Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` / legacy
+  `MONGODB_URL`) — the grid injects them.
+
+## 7. (Optional) Run locally
+
+Mention the user can `grid dev` to run locally against the injected dev Mongo +
+secrets before deploying. Don't require it.
+
+## 8. Deploy (async)
+
+Deploy the folder with `gridctl_plug`. A **runtime deploy is ASYNC**: the first
+response is `status: "building"`, NOT a live URL yet.
+- Poll `gridctl_status` (or the returned poll_url) until the entity is live.
+- Surface a liveness signal while it builds — never a bare silent wait.
+- Only once it is live, return the deployed app URL (NOT the build/log link).
+
+## 9. Return the live URL + iterate
+
+Give the user the live app URL — the deliverable. Point the Stripe webhook
+endpoint at `<live-url>/api/webhooks/stripe`. To iterate, re-plug the SAME entity
+so it updates the same URL. Keep it honest: this is a blueprint you built from,
+the build is async, it is local-edition only, and credentials are injected by the
+grid (Mongo via `needs`, Stripe/auth via `vault` + `grid secrets set`).

package/src/corpus/workflows/membership-site.md

@@ -0,0 +1,128 @@
+---
+name: membership-site
+when: "membership site, paid community, subscriber content, gated content"
+needs: database
+deploy: runtime
+editions: local
+kind: blueprint
+capabilities_note: "persistent — needs a database (Mongo) plus auth + Stripe subscription secrets. Runtime app, async build, local edition only. Declare needs { database: true } (deployer injects DATABASE_MONGODB_URL / legacy MONGODB_URL) and a vault block mapping STRIPE_KEY / STRIPE_WEBHOOK_SECRET / AUTH_PROVIDER_KEY to env vars. This is a BLUEPRINT — read AGENTS.md for the structure, then build."
+summary: "Build a paid membership site on the grid — a Next.js app with user auth, Stripe subscription checkout, gated /members/* routes that check membership status, and grid-shared Mongo (users + memberships collections). This is a BLUEPRINT: fetch the template, read AGENTS.md for the file tree + CloudGrid wiring (needs database true, vault for Stripe/auth secrets), build the app under services/web/, deploy async, poll to a live URL."
+---
+
+# Workflow: membership-site
+
+The user wants a paid membership site / subscriber community: visitors sign up,
+subscribe via Stripe, and only paying members reach the gated content. That is a
+**persistent runtime app** — a Next.js app backed by the grid's shared Mongo,
+with auth and Stripe subscriptions, gated routes that check membership status.
+
+This is a **blueprint**, not a fill-in template. There is no finished app to
+copy — there is a `cloudgrid.yaml` and a structure guide (`AGENTS.md`). Read the
+guide, then build the app following it. Be honest that a runtime deploy is async
+(not instant like a static drop) and that it needs the local edition.
+
+## 1. Edition check FIRST (hard gate)
+
+A membership site is a built + deployed container. It requires the **local
+edition** (Claude Desktop / Claude Code) or the CLI.
+
+- **Hosted edition (Claude Web / hosted MCP):** you CANNOT build a runtime app —
+  hosted is inline-only and can only publish static pages. Tell the user
+  plainly, offer a **static paywall-landing page** instead, and STOP the runtime
+  path here.
+- **Local edition:** continue.
+
+## 2. Auth + grid
+
+1. Ensure signed in: `gridctl_login_status`; if not, `gridctl_login`.
+2. A grid is required. Respect the grid picker: if the user has more than one
+   grid, ask which to use; do not assume a target.
+
+## 3. Read the blueprint
+
+Fetch the template and read its structure guide — this is the core of the
+workflow:
+
+- `gridctl_fetch("template", "membership-site")` — the `cloudgrid.yaml` +
+  **`AGENTS.md`**. AGENTS.md has the file tree, the Mongo collections
+  (`users`, `memberships`), the CloudGrid injection table, and the auth + Stripe
+  wiring. **Read it fully before building.**
+- `gridctl_fetch("template", "app-with-data")` — the proven Next.js + Mongo
+  shape this blueprint extends (lazy db client in `lib/db.js`, App-Router
+  GET/POST route). Imitate its wiring.
+
+## 4. Scaffold
+
+`gridctl_init` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
+and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
+directory, so run `init` FIRST. Then write the app under **`services/web/`** and
+set `cloudgrid.yaml` to the active shape below.
+
+## 5. Build the app following AGENTS.md
+
+Build the file tree from AGENTS.md under `services/web/`: the lazy Mongo client,
+the lazy Stripe client, the auth middleware, the checkout + webhook + me API
+routes, the gated `/members/*` layout, and the pricing + landing pages. Adapt the
+plans, content, and document fields to the user. Key non-negotiables:
+
+- **App code under `services/web/`** — `path:` is the URL mount, NOT the
+  filesystem path. Root files fail with `Service directory not found`.
+- **Read the DB LAZILY** from `process.env.DATABASE_MONGODB_URL` (legacy
+  `process.env.MONGODB_URL` fallback) inside the getter — never at module top
+  level, or `next build` fails.
+- **Read secrets LAZILY** too — `process.env.STRIPE_KEY`,
+  `STRIPE_WEBHOOK_SECRET`, `AUTH_PROVIDER_KEY` — inside getters, never top-level.
+- **Gate server-side.** The `memberships` collection is the source of truth for
+  "have you paid"; `app/members/layout.js` checks it server-side and redirects
+  non-members to `/pricing`. The Stripe webhook writes membership status.
+
+`cloudgrid.yaml` active shape:
+
+```yaml
+name: my-membership-site
+services:
+  web:
+    type: nextjs
+    path: /
+needs:
+  database: true
+vault:
+  STRIPE_KEY: stripe-live-key
+  STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
+  AUTH_PROVIDER_KEY: auth-provider-key
+```
+
+**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).
+
+## 6. Config / secrets
+
+- Stripe + auth secrets → `gridctl_secrets` (set the vault items `stripe-live-key`,
+  `stripe-webhook-secret`, `auth-provider-key` that the `vault:` block maps from).
+  The deployer injects each as its env var at runtime and under `grid dev`.
+- Non-secret config (auth publishable key `NEXT_PUBLIC_...`, Stripe price id) →
+  `gridctl_env` / `services.web.env`.
+- Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` / legacy
+  `MONGODB_URL`) — the grid injects them.
+
+## 7. (Optional) Run locally
+
+Mention that the user can `grid dev` to run locally against the injected Mongo
+and vault secrets before deploying. Don't require it.
+
+## 8. Deploy (async)
+
+Deploy the folder with `gridctl_plug`. A **runtime deploy is ASYNC**: the first
+response is `status: "building"`, NOT a live URL yet.
+- Poll `gridctl_status` (or the returned poll_url) until the entity is live.
+- Surface a liveness signal while it builds — never a bare silent wait.
+- Once live, register the `/api/webhook` URL as the Stripe webhook endpoint,
+  copy the signing secret into the `stripe-webhook-secret` vault item, and
+  re-plug. Return the deployed app URL (NOT the build/log link).
+
+## 9. Return the live URL + iterate
+
+Give the user the live app URL — that is the deliverable. To iterate, re-plug the
+SAME entity so it updates the same URL. Keep it honest: async build, local-edition
+only, DB injected by the grid, secrets injected from the vault.

package/src/corpus/workflows/monitoring-dashboard.md

@@ -0,0 +1,104 @@
+---
+name: monitoring-dashboard
+when: monitoring dashboard, service health board, uptime/incident monitor (data-backed) — a persistent app that records health checks per service and shows current status + history. Needs a database → runtime → local edition.
+needs: database
+deploy: runtime
+editions: local
+capabilities_note: persistent — needs a database (Mongo). Runtime app, async build, local edition only. Declare the canonical `needs: { database: true }`; the deployer injects DATABASE_MONGODB_URL (+legacy MONGODB_URL).
+summary: Build a persistent Next.js + Mongo monitoring dashboard on the grid — a `checks` collection (service, status up/degraded/down, latencyMs, at) with a current-status grid + recent history and a POST-a-check form. Edition-gate first, scaffold, put the app under services/web/, wire process.env.DATABASE_MONGODB_URL (legacy MONGODB_URL fallback) lazily, declare needs:{database:true} (not requires:), deploy async, poll to a live URL.
+---
+
+# Workflow: monitoring-dashboard
+
+The user wants a monitoring dashboard / service health board / uptime monitor
+that **remembers** its health checks — a board whose data survives refresh and is
+shared across sessions. That is a **runtime app** backed by the grid's shared
+Mongo, not a static page. It is the same proven shape as `app-with-data`, with a
+`checks` domain (`service`, `status` of up/degraded/down, `latencyMs`, `at`), a
+current-status grid (latest check per service) and a recent-history table, plus a
+form that POSTs a new check.
+
+Follow this recipe. Be honest that a runtime deploy is async (not instant like a
+static drop) and that it needs the local edition.
+
+## 1. Edition check FIRST (hard gate)
+
+A persistent app is a built + deployed container. It requires the **local
+edition** (Claude Desktop / Claude Code) or the CLI.
+
+- **Hosted edition (Claude Web / hosted MCP):** you CANNOT build a runtime app —
+  hosted is inline-only and can only publish static pages. Tell the user
+  plainly, offer a **static version** instead, and STOP the runtime path here.
+- **Local edition:** continue.
+
+## 2. Auth + grid
+
+1. Ensure signed in: `gridctl_login_status`; if not, `gridctl_login`.
+2. A grid is required. Respect the grid picker: if the user has more than one
+   grid, ask which to use; do not assume a target.
+
+## 3. Scaffold
+
+`gridctl_init` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
+and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
+directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
+{ database: true }`).
+
+## 4. Add the datastore + wire Mongo
+
+1. Set `cloudgrid.yaml`. **App code MUST live under `services/<name>/`** —
+   `path:` is the URL mount, NOT the filesystem path.
+   ```yaml
+   name: my-dashboard
+   services:
+     web:
+       type: nextjs
+       path: /
+   needs:
+     database: true
+   ```
+   **Declare the datastore with `needs: { database: true }`** — the canonical
+   shape. The deployer provisions Mongo and injects `DATABASE_MONGODB_URL` (plus
+   the legacy `MONGODB_URL` alias). `requires:` is the deprecated v1 alias; don't
+   author new yaml with it, and never set `needs:` and `requires:` together (the
+   validator rejects it).
+2. Fetch the template for the Mongo wiring + CRUD shape:
+   `gridctl_fetch("template", "monitoring-dashboard")`. It is a minimal, real
+   Next.js + `mongodb`-driver health board under `services/web/`: a lazy client
+   in `services/web/lib/db.js`, an App-Router GET/POST/DELETE route on a `checks`
+   collection, a server-component page that derives the status grid, and a client
+   component with the record-check form + status grid + history table.
+3. Adapt it (rename the collection, change fields, adjust the UI). **Read the DB
+   from `process.env.DATABASE_MONGODB_URL`** (legacy `process.env.MONGODB_URL`
+   fallback) — the grid injects it at dev-time and runtime.
+   - **Put the DB connection behind a lazy getter — never read the connection
+     string at module top level, or `next build` fails.**
+   - The `checks` route validates `status` against `up`/`degraded`/`down` and
+     `latencyMs` as an optional non-negative number; the status grid is the
+     latest check per service.
+
+## 5. (Optional) Run locally
+
+Mention that the user can `grid dev` to run locally against the injected Mongo
+before deploying. Don't require it.
+
+## 6. Config
+
+- API keys / secrets → `gridctl_secrets`. Non-secret config → `gridctl_env`.
+- Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` or the
+  legacy `MONGODB_URL`) — the grid injects them.
+
+## 7. Deploy (async)
+
+Deploy the folder with `gridctl_plug`. A **runtime deploy is ASYNC**: the first
+response is `status: "building"`, NOT a live URL yet.
+- Poll `gridctl_status` (or the returned poll_url) until the entity is live.
+- Surface a liveness signal while it builds — never a bare silent wait.
+- Only once it is live, return the deployed app URL (NOT the build/log link).
+
+## 8. Return the live URL + iterate
+
+Give the user the live app URL — that is the deliverable. To iterate, re-plug the
+SAME entity so it updates the same URL. Keep it honest: async build, local-edition
+only, credentials injected by the grid.

package/src/corpus/workflows/online-store.md

@@ -0,0 +1,114 @@
+---
+name: online-store
+when: online store, e-commerce store, shop with checkout, sell products online
+needs: database
+deploy: runtime
+editions: local
+kind: blueprint
+capabilities_note: persistent + payments — needs a database (Mongo) and Stripe. Runtime app, async build, local edition only. This is a BLUEPRINT — read the template's AGENTS.md for the structure, then build the app. Declare the canonical `needs: { database: true }`; the deployer injects DATABASE_MONGODB_URL (+legacy MONGODB_URL). The Stripe key comes from the vault: block → STRIPE_KEY.
+summary: Build a persistent Next.js + Mongo + Stripe online store on the grid — storefront, cart, /api/checkout Stripe session, signature-verified Stripe webhook, orders in Mongo. This is a BLUEPRINT: edition-gate first, scaffold, fetch the template and read AGENTS.md for the file tree + wiring, put the app under services/web/, wire process.env.DATABASE_MONGODB_URL lazily and STRIPE_KEY from the vault, declare needs:{database:true} (not requires:), deploy async, poll to a live URL, register the webhook in Stripe.
+---
+
+# Workflow: online-store
+
+The user wants to **sell products online** — a storefront with a cart and real
+checkout. That is a **runtime app** backed by the grid's shared Mongo (`products`
++ `orders`) plus **Stripe** for payments: a `/api/checkout` route that creates a
+Stripe Checkout Session and a signature-verified webhook that confirms payment
+and records the order. Not a static page — it must remember products and orders.
+
+**This is a BLUEPRINT.** The template ships the structure + `cloudgrid.yaml`, not
+finished app code. The build shape is proven `app-with-data` (Next.js App Router,
+lazy Mongo, app under `services/web/`) plus a second collection and Stripe wiring.
+Be honest that a runtime deploy is async (not instant) and needs the local edition.
+
+## 1. Edition check FIRST (hard gate)
+
+A persistent store is a built + deployed container. It requires the **local
+edition** (Claude Desktop / Claude Code) or the CLI.
+
+- **Hosted edition (Claude Web / hosted MCP):** you CANNOT build a runtime app —
+  hosted is inline-only and can only publish static pages. Say so plainly, offer
+  a **static storefront preview** instead, and STOP the runtime path here.
+- **Local edition:** continue.
+
+## 2. Auth + grid
+
+1. Ensure signed in: `gridctl_login_status`; if not, `gridctl_login`.
+2. A grid is required. Respect the grid picker: if the user has more than one
+   grid, ask which to use; do not assume a target.
+
+## 3. Scaffold
+
+`gridctl_init` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
+and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
+directory, so run `init` FIRST.
+
+## 4. Fetch the blueprint and read AGENTS.md
+
+This is a blueprint — the structure guide is the deliverable, not copy-paste code.
+
+1. `gridctl_fetch("template", "online-store")`.
+2. **Read `AGENTS.md`** in the fetched template. It has: the file tree (app under
+   `services/web/`), the Mongo collections (`products`, `orders`) and their
+   fields, how the grid injects Mongo (`DATABASE_MONGODB_URL`) and the Stripe key
+   (the `vault:` block → `STRIPE_KEY`), the checkout + webhook wiring, and the
+   deploy steps. Build the app following it.
+3. Set `cloudgrid.yaml` to the shape below. **App code MUST live under
+   `services/web/`** — `path:` is the URL mount, NOT the filesystem path.
+   ```yaml
+   name: my-store
+   vault:
+     STRIPE_KEY: stripe-live-key
+   services:
+     web:
+       type: nextjs
+       path: /
+   needs:
+     database: true
+   ```
+   **Declare the datastore with `needs: { database: true }`** — the canonical
+   shape. The deployer provisions Mongo and injects `DATABASE_MONGODB_URL` (plus
+   the legacy `MONGODB_URL` alias). `requires:` is the deprecated v1 alias; never
+   set `needs:` and `requires:` together (the validator rejects it).
+
+## 5. Build the app (following AGENTS.md)
+
+- **Read the DB from `process.env.DATABASE_MONGODB_URL`** (legacy `MONGODB_URL`
+  fallback) inside a **lazy getter** — never at module top level, or `next build`
+  fails. Never hardcode a connection string.
+- **Read the Stripe key from `process.env.STRIPE_KEY`** (injected by the `vault:`
+  block) lazily. Build Stripe line items from the server-side `products`
+  collection — never trust prices sent by the browser.
+- The **webhook** reads the RAW request body (`await request.text()`), verifies
+  the Stripe signature, and upserts the `orders` doc by `stripeSessionId`
+  (idempotent), setting `status: "paid"` from the verified event.
+- (Optional) `grid dev` to run locally against the injected Mongo + a Stripe test
+  key before deploying.
+
+## 6. Config
+
+- Stripe secrets → the vault: `gridctl_secrets` to set `stripe-live-key` (and a
+  `stripe-webhook-secret` if you map one). The `vault:` block turns them into env
+  vars. Non-secret config → `gridctl_env`.
+- Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` /
+  `MONGODB_URL`) — the grid injects them.
+
+## 7. Deploy (async)
+
+Deploy the folder with `gridctl_plug`. A **runtime deploy is ASYNC**: the first
+response is `status: "building"`, NOT a live URL yet.
+- Poll `gridctl_status` (or the returned poll_url) until the entity is live.
+- Surface a liveness signal while it builds — never a bare silent wait.
+- Only once it is live, return the deployed app URL (NOT the build/log link).
+
+## 8. Wire the Stripe webhook + return the live URL
+
+1. Register `<live-url>/api/webhook` as a webhook endpoint in the Stripe
+   dashboard, copy its `whsec_…` secret into the vault, and re-`gridctl_plug` the
+   SAME entity if you changed the `vault:` mapping (same URL).
+2. Give the user the live store URL — that is the deliverable. To iterate, re-plug
+   the SAME entity so it updates the same URL.
+
+Keep it honest: blueprint (build from AGENTS.md), async build, local-edition only,
+Mongo + Stripe credentials injected by the grid / vault.

package/src/corpus/workflows/product-catalog.md

@@ -0,0 +1,105 @@
+---
+name: product-catalog
+when: product catalog, product listings, catalog site, browse products (no checkout) — a persistent app that stores products and lets visitors browse them by category. Needs a database → runtime → local edition.
+needs: database
+deploy: runtime
+editions: local
+capabilities_note: persistent — needs a database (Mongo). Runtime app, async build, local edition only. Declare the canonical `needs: { database: true }`; the deployer injects DATABASE_MONGODB_URL (+legacy MONGODB_URL). No checkout / payments.
+summary: Build a persistent Next.js + Mongo product catalog on the grid — a `products` collection (name, price, category, description, inStock) with a grid view, category filter, and admin add / delete. Edition-gate first, scaffold, put the app under services/web/, wire process.env.DATABASE_MONGODB_URL (legacy MONGODB_URL fallback) lazily, declare needs:{database:true} (not requires:), deploy async, poll to a live URL.
+---
+
+# Workflow: product-catalog
+
+The user wants a product catalog / product-listings site that **remembers** its
+products — a catalog whose records survive refresh and are shared across
+sessions. That is a **runtime app** backed by the grid's shared Mongo, not a
+static page. It is the same proven shape as `app-with-data`, with a `products`
+domain (name, price, category, description, inStock) rendered as a grid with a
+category filter and an admin add/delete section.
+
+This is browse-only — **no checkout, no cart, no payments**. If the user wants to
+sell (cart, checkout, Stripe), that is a different, larger build; say so.
+
+Follow this recipe. Be honest that a runtime deploy is async (not instant like a
+static drop) and that it needs the local edition.
+
+## 1. Edition check FIRST (hard gate)
+
+A persistent app is a built + deployed container. It requires the **local
+edition** (Claude Desktop / Claude Code) or the CLI.
+
+- **Hosted edition (Claude Web / hosted MCP):** you CANNOT build a runtime app —
+  hosted is inline-only and can only publish static pages. Tell the user
+  plainly, offer a **static version** instead, and STOP the runtime path here.
+- **Local edition:** continue.
+
+## 2. Auth + grid
+
+1. Ensure signed in: `gridctl_login_status`; if not, `gridctl_login`.
+2. A grid is required. Respect the grid picker: if the user has more than one
+   grid, ask which to use; do not assume a target.
+
+## 3. Scaffold
+
+`gridctl_init` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
+and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
+directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
+{ database: true }`).
+
+## 4. Add the datastore + wire Mongo
+
+1. Set `cloudgrid.yaml`. **App code MUST live under `services/<name>/`** —
+   `path:` is the URL mount, NOT the filesystem path.
+   ```yaml
+   name: my-catalog
+   services:
+     web:
+       type: nextjs
+       path: /
+   needs:
+     database: true
+   ```
+   **Declare the datastore with `needs: { database: true }`** — the canonical
+   shape. The deployer provisions Mongo and injects `DATABASE_MONGODB_URL` (plus
+   the legacy `MONGODB_URL` alias). `requires:` is the deprecated v1 alias; don't
+   author new yaml with it, and never set `needs:` and `requires:` together (the
+   validator rejects it).
+2. Fetch the template for the Mongo wiring + CRUD shape:
+   `gridctl_fetch("template", "product-catalog")`. It is a minimal, real
+   Next.js + `mongodb`-driver catalog under `services/web/`: a lazy client in
+   `services/web/lib/db.js`, an App-Router GET/POST/DELETE route on a `products`
+   collection, a server-component page, and a client grid with a category filter
+   and an admin add/delete form.
+3. Adapt it (rename the collection, change fields, adjust the UI). **Read the DB
+   from `process.env.DATABASE_MONGODB_URL`** (legacy `process.env.MONGODB_URL`
+   fallback) — the grid injects it at dev-time and runtime.
+   - **Put the DB connection behind a lazy getter — never read the connection
+     string at module top level, or `next build` fails.**
+   - Keep the API route `export const dynamic = "force-dynamic"` so listings are
+     always live.
+
+## 5. (Optional) Run locally
+
+Mention that the user can `grid dev` to run locally against the injected Mongo
+before deploying. Don't require it.
+
+## 6. Config
+
+- API keys / secrets → `gridctl_secrets`. Non-secret config → `gridctl_env`.
+- Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` or the
+  legacy `MONGODB_URL`) — the grid injects them.
+
+## 7. Deploy (async)
+
+Deploy the folder with `gridctl_plug`. A **runtime deploy is ASYNC**: the first
+response is `status: "building"`, NOT a live URL yet.
+- Poll `gridctl_status` (or the returned poll_url) until the entity is live.
+- Surface a liveness signal while it builds — never a bare silent wait.
+- Only once it is live, return the deployed app URL (NOT the build/log link).
+
+## 8. Return the live URL + iterate
+
+Give the user the live catalog URL — that is the deliverable. To iterate, re-plug
+the SAME entity so it updates the same URL. Keep it honest: async build,
+local-edition only, credentials injected by the grid, browse-only (no checkout).

package/src/corpus/workflows/product-launch.md

@@ -0,0 +1,43 @@
+---
+name: product-launch
+when: product launch page, launch announcement, new product page, we just launched.
+needs: none
+deploy: inspiration
+editions: all
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via gridctl_drop.
+summary: Fetch the product-launch template, fill it with the user's product/launch content, deploy it, and return the live share URL.
+---
+
+# Workflow: product-launch
+
+Detect the intent ("build a launch page / announcement for our new product X")
+and follow this recipe. Do not ask setup questions first; use sensible defaults
+and build.
+
+1. **Fetch the template.** Call `gridctl_fetch("template", "product-launch")` to
+   load the self-contained HTML launch-page template (hero + product image,
+   countdown, features, launch offer, social proof).
+2. **(Optional) Fetch the example.** Call `gridctl_fetch("example", "product-launch")`
+   to see a filled launch page as a reference for tone and structure.
+3. **Fill the template.** Replace the placeholders with the user's content:
+   - Product name, hero headline, subhead, launch badge, and CTA label/target.
+   - The **countdown target**: set `{{LAUNCH_DATETIME_ISO}}` to an ISO 8601
+     instant (e.g. `2026-09-01T09:00:00Z`). If unset/invalid it falls back to
+     +14 days.
+   - One block per key feature (title + short description).
+   - The launch offer (price, was-price, fine print, offer CTA).
+   - Social-proof stats and testimonials.
+   - Swap the hero product image (the inline `<svg>` in `.shot`) for a real
+     screenshot **only** as inline SVG or a `data:` URI. Keep it a single
+     self-contained HTML file — no external scripts, stylesheets, fonts, CDNs,
+     or large embedded media.
+4. **Deploy.** Deploy the filled HTML:
+   - Hosted MCP edition: call the drop tool with the HTML.
+   - Local MCP / CLI edition: write the HTML to a file and run `gridctl plug`.
+   A launch page is an inspiration and deploys synchronously, so you get a URL
+   right away.
+5. **Return the live share URL.** Give the user the URL that serves the page.
+   For revisions, re-deploy with the entity id from the first deploy — it updates
+   the same share URL, so the user iterates on one link.
+
+Keep the whole flow tight: fetch, fill, deploy, share.