@cloudgrid-io/mcp 0.20.4 → 0.20.5

package/src/corpus/templates/marketplace/AGENTS.md

@@ -181,7 +181,7 @@ Runtime app → **local edition** only (Claude Desktop / Claude Code / CLI); the
 hosted edition cannot build a runtime container. Order matters — `plug` needs a
 linked directory, so `init` first.
 
-1. `grid init` (or `grid_init`) an app `<name>` — creates the entity +
+1. `grid init` (or `grid_create_project`) an app `<name>` — creates the entity +
    `.cloudgrid/link.json` and a starter `cloudgrid.yaml` with empty `services:{}`.
 2. Fill: put the app under `services/web/` and set `cloudgrid.yaml` to this
    blueprint's active fields (`services.web` nextjs `/`, `needs:{database:true}`,

package/src/corpus/templates/marketplace/index.md

@@ -10,7 +10,7 @@ code** — read the structure guide, then build the app following it.
 `AGENTS.md`. Fetch the bundle, read `AGENTS.md`, then generate the files under
 `services/web/` and deploy.
 
-- **Structure guide:** `grid_fetch("template", "marketplace")` → read
+- **Structure guide:** `grid_get_template("template", "marketplace")` → read
   **`AGENTS.md`** (file tree, Mongo collections, CloudGrid injection table, auth +
   Stripe Connect wiring, deploy steps, edition note).
 

package/src/corpus/templates/membership-site/AGENTS.md

@@ -9,7 +9,7 @@ rules — they are what make it deploy.
 
 The proven persistent shape is `app-with-data` (Next.js + Mongo). This blueprint
 extends it with auth + Stripe. Fetch that template for the Mongo lazy-client and
-App-Router API pattern: `grid_fetch("template", "app-with-data")`.
+App-Router API pattern: `grid_get_template("template", "app-with-data")`.
 
 ## 1. File tree
 
@@ -78,7 +78,7 @@ A user is a member when a `memberships` doc for their `authId` has
     STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
     AUTH_PROVIDER_KEY: auth-provider-key
   ```
-  Set the vault items ONCE with `grid_secrets` (or `grid secrets set`), then
+  Set the vault items ONCE with `grid_set_secret` (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
@@ -132,18 +132,18 @@ A user is a member when a `memberships` doc for their `authId` has
 
 1. `grid_login_status` → `grid_login` if needed. Respect the grid picker
    (ask which grid if the user has more than one).
-2. `grid_init` an app `<name>` FIRST — it creates the entity, writes
+2. `grid_create_project` 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: `grid_secrets` for `stripe-live-key`,
+4. Set the secrets: `grid_set_secret` for `stripe-live-key`,
    `stripe-webhook-secret`, `auth-provider-key` (the vault item keys the
    `vault:` block maps from). Non-secret config (publishable auth key, price id)
-   → `grid_env` / `services.web.env`. Do NOT set `DATABASE_MONGODB_URL`
+   → `grid_set_env` / `services.web.env`. Do NOT set `DATABASE_MONGODB_URL`
    yourself — the grid injects it.
-5. `grid_plug` to deploy. A runtime deploy is **ASYNC** — the first response
+5. `grid_deploy` to deploy. 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.
@@ -157,4 +157,4 @@ A membership site 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
-paywall-landing page (via `grid_plug`) instead, then stop the runtime path.
+paywall-landing page (via `grid_deploy`) instead, then stop the runtime path.

package/src/corpus/templates/membership-site/index.md

@@ -9,8 +9,8 @@ adapt plans/content/fields, then deploy (async — poll to a live URL). Local
 edition only.
 
 **Fetch the bundle:**
-- `grid_fetch("template", "membership-site")` — this blueprint (`cloudgrid.yaml` + `AGENTS.md`).
-- `grid_fetch("template", "app-with-data")` — the proven Next.js + Mongo shape to extend (lazy db client, App-Router API).
+- `grid_get_template("template", "membership-site")` — this blueprint (`cloudgrid.yaml` + `AGENTS.md`).
+- `grid_get_template("template", "app-with-data")` — the proven Next.js + Mongo shape to extend (lazy db client, App-Router API).
 
 **Key rules:**
 
@@ -24,7 +24,7 @@ edition only.
    the getter, never at module top level (top-level read fails `next build`).
 4. **Secrets via the `vault:` block** → env vars. `STRIPE_KEY`,
    `STRIPE_WEBHOOK_SECRET`, `AUTH_PROVIDER_KEY` map to vault items; set them with
-   `grid_secrets`, and the deployer injects them at runtime. Read lazily; do
+   `grid_set_secret`, and the deployer injects them at runtime. Read lazily; do
    not commit keys or put secrets in `services.web.env`.
 5. **Gate server-side.** Auth answers "who are you"; the `memberships`
    collection answers "have you paid". `app/members/layout.js` checks membership
@@ -60,7 +60,7 @@ vault:
 
 ## Deploy (async, local edition)
 
-`grid_init` first (creates the entity + link.json), write the app under
-`services/web/`, set the vault secrets with `grid_secrets`, `grid_plug`
+`grid_create_project` first (creates the entity + link.json), write the app under
+`services/web/`, set the vault secrets with `grid_set_secret`, `grid_deploy`
 (async — poll `grid_status` to a live URL), then register the `/api/webhook`
 URL in Stripe and re-plug. Re-plug the same entity to update the same URL.

package/src/corpus/templates/online-store/index.md

@@ -74,7 +74,7 @@ needs:
 
 ## Build it
 
-Fetch `grid_fetch("template", "online-store")` and read **`AGENTS.md`** — it
+Fetch `grid_get_template("template", "online-store")` and read **`AGENTS.md`** — it
 has the checkout + webhook wiring, the vault/secret setup, and the deploy steps
 (`grid init` → write under `services/web/` → `grid secrets set` → `grid plug`,
 async → poll to a live URL → register the webhook endpoint in Stripe). Adapt the

package/src/corpus/templates/portfolio/README.md

@@ -3,12 +3,12 @@
 A single self-contained HTML personal / freelancer portfolio: a hero intro, an about section, a skills list, a projects grid, and a contact section.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `grid_plug` and works on every
+no external CDNs). It deploys instantly via `grid_deploy` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in
 
-Fetch the template with `grid_fetch("template", "portfolio")`, then replace the
+Fetch the template with `grid_get_template("template", "portfolio")`, then replace the
 placeholders:
 
    - The person's name, role/title, and short intro.

package/src/corpus/templates/portfolio/index.md

@@ -5,13 +5,13 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`grid_plug`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
+To publish this page, use **`grid_deploy`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
 edition (Claude Web) as well as local. The reference `cloudgrid.yaml` in this
 directory (`type: static`) is ONLY for plugging the page as an OWNED static
-runtime (async, local edition only); the fast path is `grid_plug`.
+runtime (async, local edition only); the fast path is `grid_deploy`.
 
 The fillable HTML is the real template — fetch it with
-`grid_fetch("template", "portfolio")` and fill in the user's content.
+`grid_get_template("template", "portfolio")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

package/src/corpus/templates/product-launch/README.md

@@ -34,12 +34,12 @@ A one-page launch announcement with:
 ## How it deploys
 
 Deploys as an **inspiration** — instant, and works on the **hosted** edition
-(Claude Web) as well as local. Use **`grid_plug`** with the inline `html`: you get a live share URL right away. Re-dropping the same entity
+(Claude Web) as well as local. Use **`grid_deploy`** with the inline `html`: you get a live share URL right away. Re-dropping the same entity
 updates the same URL, so the user iterates on one link.
 
 The reference `cloudgrid.yaml` in this directory (`type: static`) is ONLY for
 plugging the page as an OWNED static runtime (async, local edition only); the
-fast path is `grid_plug`.
+fast path is `grid_deploy`.
 
 The fillable HTML is the real template — fetch it with
-`grid_fetch("template", "product-launch")` and fill in the user's content.
+`grid_get_template("template", "product-launch")` and fill in the user's content.

package/src/corpus/templates/product-launch/cloudgrid.yaml

@@ -17,7 +17,7 @@
 # active fields are exactly name + services.web{type: static, path: /}; there
 # are no needs. This cloudgrid.yaml is the reference for plugging the page as an
 # OWNED static runtime; the fast path is to deploy it as an INSPIRATION via
-# grid_plug (instant, and works on the hosted edition too).
+# grid_deploy (instant, and works on the hosted edition too).
 # ============================================================================
 
 

package/src/corpus/templates/product-launch/index.md

@@ -8,13 +8,13 @@ client-side.
 
 ## How it deploys
 
-To publish this page, use **`grid_plug`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
+To publish this page, use **`grid_deploy`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
 edition (Claude Web) as well as local. The reference `cloudgrid.yaml` in this
 directory (`type: static`) is ONLY for plugging the page as an OWNED static
-runtime (async, local edition only); the fast path is `grid_plug`.
+runtime (async, local edition only); the fast path is `grid_deploy`.
 
 The fillable HTML is the real template — fetch it with
-`grid_fetch("template", "product-launch")` and fill in the user's content
+`grid_get_template("template", "product-launch")` and fill in the user's content
 (product name, hero copy, countdown target, features, offer, quotes). Keep it a
 single self-contained file: inline SVG / `data:` URIs only, no external scripts,
 stylesheets, fonts, or CDNs.

package/src/corpus/templates/report/cloudgrid.yaml

@@ -16,7 +16,7 @@
 # THIS TEMPLATE (report): a single self-contained static page. The active fields
 # are exactly name + services.web{type: static, path: /}; there are no needs.
 # This cloudgrid.yaml is the reference for plugging it as an OWNED static
-# runtime; the fast path is to deploy it as an INSPIRATION via grid_plug
+# runtime; the fast path is to deploy it as an INSPIRATION via grid_deploy
 # (instant, and works on the hosted edition too).
 # ============================================================================
 

package/src/corpus/templates/report/index.md

@@ -5,13 +5,13 @@ no `needs:`. State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`grid_plug`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
+To publish this page, use **`grid_deploy`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
 edition (Claude Web) as well as local. The reference `cloudgrid.yaml` in this
 directory (`type: static`) is ONLY for plugging the page as an OWNED static
-runtime (async, local edition only); the fast path is `grid_plug`.
+runtime (async, local edition only); the fast path is `grid_deploy`.
 
 The fillable HTML is the real template — fetch it with
-`grid_fetch("template", "report")` and fill in the user's content.
+`grid_get_template("template", "report")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

package/src/corpus/templates/restaurant-reservations/AGENTS.md

@@ -115,9 +115,9 @@ You never provision infra or set connection strings by hand. Declare intent in
   `STRIPE_KEY: stripe-live-key`, `SENDGRID_API_KEY: sendgrid-key`,
   `AUTH_PROVIDER_KEY: auth-provider-secret`. The platform reads the named item
   from the org vault and injects it as that env var at runtime. Store the actual
-  secret value with `grid_secrets` (or the org vault UI) — never commit it. In
+  secret value with `grid_set_secret` (or the org vault UI) — never commit it. In
   code read `process.env.STRIPE_KEY`, `process.env.SENDGRID_API_KEY`, etc. Vault
-  is the CloudGrid-correct path for third-party keys; `grid_env` is for
+  is the CloudGrid-correct path for third-party keys; `grid_set_env` is for
   non-secret config only.
 
 - **AI (optional).** If you add AI (e.g. menu-copy generation, natural-language
@@ -154,7 +154,7 @@ Reserved env var names you must NOT set: `PORT`, `APP_NAME`, `SERVICE_NAME`,
    provider; leave `/`, `/reserve`, `/api/menu`, `/api/reservations` (POST),
    `/api/webhooks/stripe` public.
 3. Initialize the SDK from `process.env.AUTH_PROVIDER_KEY` (+ any public
-   publishable key via `grid_env`). The public booking flow needs no login.
+   publishable key via `grid_set_env`). The public booking flow needs no login.
 
 Keep the public reservation POST open; only staff read/mutate endpoints
 (`GET /api/reservations`, `PATCH/DELETE /api/reservations/[id]`, `/staff/*`) sit
@@ -169,17 +169,17 @@ build is **asynchronous**.
 
 1. `grid_login_status` (→ `grid_login` if needed). Pick the grid if the
    user has more than one.
-2. `grid_init` an app `<name>` — creates the entity + `.cloudgrid/link.json`
+2. `grid_create_project` an app `<name>` — creates the entity + `.cloudgrid/link.json`
    and a `cloudgrid.yaml` with empty `services: {}`. Run `init` FIRST (plug needs
    a linked dir).
 3. **Fill** — write the app under `services/web/`, then set `cloudgrid.yaml` to
    this blueprint's active fields: `name`, `services.web { type: nextjs, path: / }`,
    `needs: { database: true }`, and the `vault:` mappings you actually use.
-4. Store secrets: `grid_secrets` for the vault item values (Stripe/SendGrid/
-   auth). Non-secret config (publishable keys, feature flags) → `grid_env`.
+4. Store secrets: `grid_set_secret` for the vault item values (Stripe/SendGrid/
+   auth). Non-secret config (publishable keys, feature flags) → `grid_set_env`.
 5. (Optional) `grid dev` — runs Next.js locally with `DATABASE_MONGODB_URL` and
    vault vars injected against dev Mongo. Seed `menu`, test a booking.
-6. `grid_plug` — builds + deploys `services/web/`. **Async**: the first
+6. `grid_deploy` — builds + deploys `services/web/`. **Async**: the first
    response is `status: building`, not a URL. Poll `grid_status` (or the
    returned poll URL) until live; surface a liveness signal while it builds
    (never a bare silent wait). Only then return the **live app URL** (not the

package/src/corpus/templates/restaurant-reservations/index.md

@@ -20,7 +20,7 @@ app under `services/web/` following it — the proven `app-with-data` shape with
    `MONGODB_URL` fallback — the grid injects it; never hardcode, never commit.
 3. **Third-party secrets go through the `vault:` block** (Stripe `STRIPE_KEY`,
    email `SENDGRID_API_KEY`, optional `AUTH_PROVIDER_KEY`) → injected env vars;
-   store values with `grid_secrets`.
+   store values with `grid_set_secret`.
 4. **Declare `needs: { database: true }`** (canonical) — never mix `needs:` and
    `requires:`.
 5. **Cron reminder service is documented but NOT deployable yet** (platform issue
@@ -29,7 +29,7 @@ app under `services/web/` following it — the proven `app-with-data` shape with
 ## Fetch bundle
 
 ```
-grid_fetch("template", "restaurant-reservations")   # cloudgrid.yaml + AGENTS.md + README
+grid_get_template("template", "restaurant-reservations")   # cloudgrid.yaml + AGENTS.md + README
 ```
 
 Then read `AGENTS.md` (file tree, `menu`/`reservations`/`tables` collections,

package/src/corpus/templates/saas-marketing/README.md

@@ -3,12 +3,12 @@
 A single self-contained HTML SaaS marketing site (hero, features, pricing tiers, testimonials, FAQ, and a closing call to action). Richer than the landing-page template.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `grid_plug` and works on every
+no external CDNs). It deploys instantly via `grid_deploy` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in
 
-Fetch the template with `grid_fetch("template", "saas-marketing")`, then replace the
+Fetch the template with `grid_get_template("template", "saas-marketing")`, then replace the
 placeholders:
 
    - The product name, tagline, and hero eyebrow/headline/subheadline.

package/src/corpus/templates/saas-marketing/index.md

@@ -5,13 +5,13 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`grid_plug`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
+To publish this page, use **`grid_deploy`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
 edition (Claude Web) as well as local. The reference `cloudgrid.yaml` in this
 directory (`type: static`) is ONLY for plugging the page as an OWNED static
-runtime (async, local edition only); the fast path is `grid_plug`.
+runtime (async, local edition only); the fast path is `grid_deploy`.
 
 The fillable HTML is the real template — fetch it with
-`grid_fetch("template", "saas-marketing")` and fill in the user's content.
+`grid_get_template("template", "saas-marketing")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

package/src/corpus/templates/status-page/README.md

@@ -3,12 +3,12 @@
 A single self-contained HTML service status page: an overall banner, a component list with up / degraded / down pills, per-component uptime bars, and an incident history log. Status is baked into the page.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `grid_plug` and works on every
+no external CDNs). It deploys instantly via `grid_deploy` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in
 
-Fetch the template with `grid_fetch("template", "status-page")`, then replace the
+Fetch the template with `grid_get_template("template", "status-page")`, then replace the
 placeholders:
 
    - The overall status banner text and state class (`ok` / `degraded` / `down`).

package/src/corpus/templates/status-page/index.md

@@ -5,13 +5,13 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`grid_plug`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
+To publish this page, use **`grid_deploy`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
 edition (Claude Web) as well as local. The reference `cloudgrid.yaml` in this
 directory (`type: static`) is ONLY for plugging the page as an OWNED static
-runtime (async, local edition only); the fast path is `grid_plug`.
+runtime (async, local edition only); the fast path is `grid_deploy`.
 
 The fillable HTML is the real template — fetch it with
-`grid_fetch("template", "status-page")` and fill in the user's content.
+`grid_get_template("template", "status-page")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

@@ -18,7 +18,7 @@ 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:
-`grid_fetch("template", "app-with-data")`.
+`grid_get_template("template", "app-with-data")`.
 
 ## 1. File tree
 
@@ -89,7 +89,7 @@ client for plan/status — read this (kept current by the webhook).
     STRIPE_KEY: stripe-live-key
     STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
   ```
-  Set the vault items ONCE with `grid_secrets` (or `grid secrets set`), then
+  Set the vault items ONCE with `grid_set_secret` (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
@@ -160,19 +160,19 @@ known user — otherwise anyone could change anyone's plan.
 
 1. `grid_login_status` → `grid_login` if needed. Respect the grid picker
    (ask which grid if the user has more than one).
-2. `grid_init` an app `<name>` FIRST — it creates the entity, writes
+2. `grid_create_project` 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: `grid_secrets` for `stripe-live-key`,
+4. Set the secrets: `grid_set_secret` 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) → `grid_env` /
+   publishable key, price ids, auth publishable key) → `grid_set_env` /
    `services.web.env`. Do NOT set `DATABASE_MONGODB_URL` yourself — the grid
    injects it.
-5. `grid_plug` to deploy. A runtime deploy is **ASYNC** — the first response
+5. `grid_deploy` to deploy. 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.
@@ -187,5 +187,5 @@ 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 `grid_plug`) instead, then stop the runtime
+static pricing/plans page (via `grid_deploy`) instead, then stop the runtime
 path.

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

@@ -15,8 +15,8 @@ flow, use the `membership-site` blueprint — the two share the same Stripe + Mo
 wiring.
 
 **Fetch the bundle:**
-- `grid_fetch("template", "subscription-management")` — this blueprint (`cloudgrid.yaml` + `AGENTS.md`).
-- `grid_fetch("template", "app-with-data")` — the proven Next.js + Mongo shape to extend (lazy db client, App-Router API).
+- `grid_get_template("template", "subscription-management")` — this blueprint (`cloudgrid.yaml` + `AGENTS.md`).
+- `grid_get_template("template", "app-with-data")` — the proven Next.js + Mongo shape to extend (lazy db client, App-Router API).
 
 **Key rules:**
 
@@ -30,7 +30,7 @@ wiring.
    `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 `grid_secrets`,
+   `STRIPE_WEBHOOK_SECRET` map to vault items; set them with `grid_set_secret`,
    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;
@@ -66,8 +66,8 @@ vault:
 
 ## Deploy (async, local edition)
 
-`grid_init` first (creates the entity + link.json), write the app under
-`services/web/`, set the vault secrets with `grid_secrets`, `grid_plug`
+`grid_create_project` first (creates the entity + link.json), write the app under
+`services/web/`, set the vault secrets with `grid_set_secret`, `grid_deploy`
 (async — poll `grid_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.

package/src/corpus/templates/waitlist/README.md

@@ -3,12 +3,12 @@
 A single self-contained HTML launch waitlist / coming-soon page: a hero, an email capture form, and a social-proof counter.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `grid_plug` and works on every
+no external CDNs). It deploys instantly via `grid_deploy` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in
 
-Fetch the template with `grid_fetch("template", "waitlist")`, then replace the
+Fetch the template with `grid_get_template("template", "waitlist")`, then replace the
 placeholders:
 
    - The product name, coming-soon headline, and subheadline.

package/src/corpus/templates/waitlist/index.md

@@ -5,13 +5,13 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`grid_plug`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
+To publish this page, use **`grid_deploy`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
 edition (Claude Web) as well as local. The reference `cloudgrid.yaml` in this
 directory (`type: static`) is ONLY for plugging the page as an OWNED static
-runtime (async, local edition only); the fast path is `grid_plug`.
+runtime (async, local edition only); the fast path is `grid_deploy`.
 
 The fillable HTML is the real template — fetch it with
-`grid_fetch("template", "waitlist")` and fill in the user's content.
+`grid_get_template("template", "waitlist")` and fill in the user's content.
 
 ## Note on storing signups
 

package/src/corpus/templates/web-app/cloudgrid.yaml

@@ -16,7 +16,7 @@
 # THIS TEMPLATE (web-app): a single self-contained static page. The active fields
 # are exactly name + services.web{type: static, path: /}; there are no needs.
 # This cloudgrid.yaml is the reference for plugging it as an OWNED static
-# runtime; the fast path is to deploy it as an INSPIRATION via grid_plug
+# runtime; the fast path is to deploy it as an INSPIRATION via grid_deploy
 # (instant, and works on the hosted edition too).
 # ============================================================================
 

package/src/corpus/templates/web-app/index.md

@@ -5,13 +5,13 @@ no `needs:`. State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`grid_plug`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
+To publish this page, use **`grid_deploy`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
 edition (Claude Web) as well as local. The reference `cloudgrid.yaml` in this
 directory (`type: static`) is ONLY for plugging the page as an OWNED static
-runtime (async, local edition only); the fast path is `grid_plug`.
+runtime (async, local edition only); the fast path is `grid_deploy`.
 
 The fillable HTML is the real template — fetch it with
-`grid_fetch("template", "web-app")` and fill in the user's content.
+`grid_get_template("template", "web-app")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

package/src/corpus/usage.md

@@ -45,7 +45,7 @@ npx skills add cloudgrid-io/skills
 ```
 claude mcp add cloudgrid -- npx -y @cloudgrid-io/mcp
 ```
-- **Find it under `/mcp`.** Exposes tools `grid_plug`, `grid_login`, …
+- **Find it under `/mcp`.** Exposes tools `grid_deploy`, `grid_login`, …
 - Invoke by describing the task; the model calls the tool.
 
 > Where did my install go? `/skills` (skills), `/plugin` (plugin), `/mcp` (MCP).

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

@@ -39,7 +39,7 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_init` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
+`grid_create_project` 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:
@@ -64,7 +64,7 @@ and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
    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:
-   `grid_fetch("template", "admin-dashboard")`. It is a minimal, real Next.js
+   `grid_get_template("template", "admin-dashboard")`. It is a minimal, real Next.js
    + `mongodb`-driver admin panel under `services/web/`: a lazy client in
    `services/web/lib/db.js`, two App-Router GET/POST/DELETE routes (`users` and
    `orders`), a server-component page that computes a metrics header, and a
@@ -83,13 +83,13 @@ before deploying. Don't require it.
 
 ## 6. Config
 
-- API keys / secrets → `grid_secrets`. Non-secret config → `grid_env`.
+- API keys / secrets → `grid_set_secret`. Non-secret config → `grid_set_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 `grid_plug`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/ai-app.md

@@ -41,7 +41,7 @@ Persistent apps are owned entities.
 
 ## 3. Scaffold
 
-`grid_init` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
+`grid_create_project` 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.
 
@@ -75,7 +75,7 @@ ai: true, database: true }`).
    yaml with it, and never set `needs:` and `requires:` together (the validator
    rejects it).
 2. Fetch the template for the chat wiring:
-   `grid_fetch("template", "ai-app")`. It is a minimal Next.js App Router chat
+   `grid_get_template("template", "ai-app")`. It is a minimal Next.js App Router chat
    app under `services/web/`: a chat page, an API route
    (`app/api/chat/route.js`, `export const dynamic = "force-dynamic"`) that reads
    the user message, calls the AI gateway, persists the exchange to Mongo, and
@@ -95,7 +95,7 @@ ai: true, database: true }`).
    imported for route analysis before the grid injects the var). Store the user
    message and the assistant reply so the conversation survives refresh. Never
    hardcode a connection string; never commit a secret.
-   - (Optional) fetch `grid_fetch("example", "ai-app")` for a richer filled
+   - (Optional) fetch `grid_get_template("example", "ai-app")` for a richer filled
      reference (a themed assistant) to imitate.
 
 ## 5. (Optional) Run locally
@@ -105,15 +105,15 @@ are wired in dev too — and send a test message before deploying. Don't require
 
 ## 6. Config
 
-- Extra API keys / secrets (only if the app needs its own) → `grid_secrets`.
-- Non-secret config → `grid_env`.
+- Extra API keys / secrets (only if the app needs its own) → `grid_set_secret`.
+- Non-secret config → `grid_set_env`.
 - Do **NOT** set the DB connection var yourself (`DATABASE_MONGODB_URL` / legacy
   `MONGODB_URL`) and do **NOT** set an AI key — the grid injects the DB var and
   the AI SDK auto-detects the in-grid identity.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"` with a `poll_url` / entity, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/ai-knowledge-base.md

@@ -50,7 +50,7 @@ CLI.
 
 ## 3. Fetch the blueprint and READ AGENTS.md
 
-`grid_fetch("template", "ai-knowledge-base")`. The deliverable is the
+`grid_get_template("template", "ai-knowledge-base")`. The deliverable is the
 **`AGENTS.md` structure guide** — read it before writing anything. It defines:
 - the `services/web/` file tree (pages, `api/documents` + `api/ask` routes, `lib/`),
 - the Mongo collections (`documents`, `chunks`) + fields,
@@ -64,7 +64,7 @@ There is no app code to copy — you generate it from the guide.
 
 ## 4. Scaffold + fill cloudgrid.yaml
 
-`grid_init` an app `<name>` FIRST (creates the entity + `.cloudgrid/link.json`
+`grid_create_project` 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:
@@ -112,7 +112,7 @@ Generate the files under `services/web/` per the guide:
   yourself; the grid injects them.
 - Only if you add auth/payments: map the secret in the `vault:` block
   (`AUTH_PROVIDER_KEY` and/or `STRIPE_KEY`) and store the value with
-  `grid secrets set <vault-item-key> …`. Non-secret public config → `grid_env`.
+  `grid secrets set <vault-item-key> …`. Non-secret public config → `grid_set_env`.
 
 ## 7. (Optional) Run locally
 
@@ -121,7 +121,7 @@ Gateway before deploying. Don't require it.
 
 ## 8. Deploy (async)
 
-Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.