@cloudgrid-io/mcp 0.20.4 → 0.20.5

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

@@ -40,7 +40,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.
 
@@ -48,7 +48,7 @@ directory, so run `init` FIRST.
 
 This is a blueprint — the structure guide is the deliverable, not copy-paste code.
 
-1. `grid_fetch("template", "online-store")`.
+1. `grid_get_template("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
@@ -88,15 +88,15 @@ This is a blueprint — the structure guide is the deliverable, not copy-paste c
 
 ## 6. Config
 
-- Stripe secrets → the vault: `grid_secrets` to set `stripe-live-key` (and a
+- Stripe secrets → the vault: `grid_set_secret` 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 → `grid_env`.
+  vars. Non-secret config → `grid_set_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 `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.
@@ -105,7 +105,7 @@ response is `status: "building"`, NOT a live URL yet.
 ## 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-`grid_plug` the
+   dashboard, copy its `whsec_…` secret into the vault, and re-`grid_deploy` 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.

package/src/corpus/workflows/portfolio.md

@@ -4,7 +4,7 @@ when: portfolio, personal site, freelancer site, my work, showcase, resume site,
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
 summary: Fetch the portfolio template, fill it with the user's projects and bio, deploy it, and return the live share URL.
 ---
 
@@ -15,7 +15,7 @@ follow this recipe. Reach for this over `landing-page` when the request is about
 showcasing projects with an about, skills, and contact. Do not ask setup
 questions first; use sensible defaults and build.
 
-1. **Fetch the template.** Call `grid_fetch("template", "portfolio")` to load
+1. **Fetch the template.** Call `grid_get_template("template", "portfolio")` to load
    the self-contained HTML portfolio (hero, about, skills, projects grid,
    contact).
 2. **Fill the template.** Replace the placeholders with the user's content:

package/src/corpus/workflows/presentation.md

@@ -4,7 +4,7 @@ when: slides, deck, pitch, presentation, slideshow.
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
 summary: Fetch the deck template, fill it with the user's content, deploy it, and return the live share URL.
 ---
 
@@ -13,9 +13,9 @@ summary: Fetch the deck template, fill it with the user's content, deploy it, an
 Detect the intent ("build me a presentation / deck / slides about X") and follow
 this recipe. Do not ask setup questions first; use sensible defaults and build.
 
-1. **Fetch the template.** Call `grid_fetch("template", "deck")` to load the
+1. **Fetch the template.** Call `grid_get_template("template", "deck")` to load the
    self-contained HTML deck template.
-2. **(Optional) Fetch the example.** Call `grid_fetch("example", "deck")` to
+2. **(Optional) Fetch the example.** Call `grid_get_template("example", "deck")` to
    see a filled deck as a reference for tone and structure.
 3. **Fill the template.** Replace the placeholders with the user's content:
    - The deck title and subtitle.

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

@@ -41,7 +41,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:
@@ -66,7 +66,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", "product-catalog")`. It is a minimal, real
+   `grid_get_template("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
@@ -86,13 +86,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/product-launch.md

@@ -4,7 +4,7 @@ when: product launch page, launch announcement, new product page, we just launch
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
 summary: Fetch the product-launch template, fill it with the user's product/launch content, deploy it, and return the live share URL.
 ---
 
@@ -14,10 +14,10 @@ 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 `grid_fetch("template", "product-launch")` to
+1. **Fetch the template.** Call `grid_get_template("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 `grid_fetch("example", "product-launch")`
+2. **(Optional) Fetch the example.** Call `grid_get_template("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.

package/src/corpus/workflows/project-management.md

@@ -42,7 +42,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:
@@ -67,7 +67,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", "project-management")`. It is a minimal, real
+   `grid_get_template("template", "project-management")`. It is a minimal, real
    Next.js + `mongodb`-driver app under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/DELETE route on a `projects`
    collection, a GET/POST/PATCH/DELETE route on a `tasks` collection, a
@@ -87,13 +87,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/property-listings.md

@@ -38,7 +38,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:
@@ -63,7 +63,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", "property-listings")`. It is a minimal, real
+   `grid_get_template("template", "property-listings")`. It is a minimal, real
    Next.js + `mongodb`-driver listings site under `services/web/`: a lazy client
    in `services/web/lib/db.js`, an App-Router GET/POST/DELETE route on a
    `properties` collection (GET supports `?location=` and `?maxPrice=` filters), a
@@ -82,13 +82,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/quiz-platform.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", "quiz-platform")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "quiz-platform")`. It is a minimal, real Next.js +
    `mongodb`-driver quiz platform under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/DELETE route on a
    `questions` collection, a server-component page that reads the collection, and
@@ -86,13 +86,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/report.md

@@ -4,7 +4,7 @@ when: report, one-pager, summary, brief, whitepaper, case study, formatted docum
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
 summary: Fetch the report template, fill it with the user's content, deploy it, and return the live share URL.
 ---
 
@@ -13,9 +13,9 @@ summary: Fetch the report template, fill it with the user's content, deploy it,
 Detect the intent ("build me a report / one-pager / brief about X") and follow
 this recipe. Do not ask setup questions first; use sensible defaults and build.
 
-1. **Fetch the template.** Call `grid_fetch("template", "report")` to load
+1. **Fetch the template.** Call `grid_get_template("template", "report")` to load
    the self-contained, print-friendly HTML report template.
-2. **(Optional) Fetch the example.** Call `grid_fetch("example", "report")`
+2. **(Optional) Fetch the example.** Call `grid_get_template("example", "report")`
    to see a filled report as a reference for tone and structure.
 3. **Fill the template.** Replace the placeholders with the user's content:
    - The report title, subtitle, and date line.

package/src/corpus/workflows/restaurant-reservations.md

@@ -43,7 +43,7 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Fetch the blueprint and READ AGENTS.md
 
-`grid_fetch("template", "restaurant-reservations")`. This is a **blueprint**,
+`grid_get_template("template", "restaurant-reservations")`. This is a **blueprint**,
 so the deliverable is `cloudgrid.yaml` + `AGENTS.md`, not app code.
 
 **Read `AGENTS.md` before building.** It defines:
@@ -56,7 +56,7 @@ so the deliverable is `cloudgrid.yaml` + `AGENTS.md`, not app code.
 
 ## 4. Scaffold + fill
 
-1. `grid_init` an app `<name>` — creates the entity + `.cloudgrid/link.json`
+1. `grid_create_project` an app `<name>` — creates the entity + `.cloudgrid/link.json`
    and a `cloudgrid.yaml` with an EMPTY `services: {}`. Run `init` FIRST (plug
    needs a linked directory).
 2. Write the app under **`services/web/`** (`path:` is the URL mount, NOT the
@@ -85,9 +85,9 @@ so the deliverable is `cloudgrid.yaml` + `AGENTS.md`, not app code.
 
 ## 5. Config / secrets
 
-- Secret values (Stripe, SendGrid, auth) → `grid_secrets` (the `vault:` block
+- Secret values (Stripe, SendGrid, auth) → `grid_set_secret` (the `vault:` block
   maps them to env vars). Non-secret config (publishable keys, flags) →
-  `grid_env`.
+  `grid_set_env`.
 - Do **NOT** set the DB vars yourself (`DATABASE_MONGODB_URL` / `MONGODB_URL`) —
   the grid injects them.
 
@@ -98,7 +98,7 @@ against dev Mongo. Seed the `menu` collection, test a booking. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy `services/web/` with `grid_plug`. A **runtime deploy is ASYNC**: the
+Deploy `services/web/` with `grid_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.

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

@@ -38,7 +38,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:
@@ -63,7 +63,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", "revenue-dashboard")`. It is a minimal, real
+   `grid_get_template("template", "revenue-dashboard")`. It is a minimal, real
    Next.js + `mongodb`-driver dashboard under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/DELETE route on a `sales`
    collection, a server-component page that computes the total + per-product
@@ -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/saas-marketing.md

@@ -4,7 +4,7 @@ when: SaaS marketing site, product marketing page, features and pricing page, mu
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
 summary: Fetch the saas-marketing template, fill it with the user's product content, deploy it, and return the live share URL.
 ---
 
@@ -16,7 +16,7 @@ it when the request calls for pricing tiers, testimonials, and an FAQ, not just
 hero. For a plain single-section landing page, use `landing-page`. Do not ask
 setup questions first; use sensible defaults and build.
 
-1. **Fetch the template.** Call `grid_fetch("template", "saas-marketing")` to
+1. **Fetch the template.** Call `grid_get_template("template", "saas-marketing")` to
    load the self-contained HTML marketing site.
 2. **Fill the template.** Replace the placeholders with the user's content:
    - The product name, tagline, and hero eyebrow/headline/subheadline.

package/src/corpus/workflows/semantic-search.md

@@ -6,7 +6,7 @@ deploy: runtime
 editions: local
 capabilities_note: "Document search — needs a database (Mongo) for the documents + chunks collections. Two services: a React (Vite) static frontend at / and a FastAPI backend at /backend. Hybrid search = Mongo $text (lexical) + in-app NumPy cosine over chunk embedding arrays (semantic) + metadata filters, blended to the document level. Runtime app, async build, local edition only. Declare needs:{database:true}. NO needs:vector — pgvector runtime role-grant is blocked (#1545), so embeddings live in the Mongo chunks collection and are cosine-ranked in-app. Two refresh paths: the manager 'Refresh now' endpoint AND a scheduled Python type:cron job (services/refresh, daily 03:00 UTC) that vendors the backend app/ modules and reuses indexing.run_sync — both degrade gracefully. Health is green with no secrets; startup ensure_indexes() so $text never 500s on an empty catalog. Pluggable source (dropbox|local|url) + embeddings (OpenAI-compatible) each behind one config point, all secrets from env."
 summary: "Build a document-search app on the grid — index a folder of PDFs/DOCX/TXT/MD, then search by keyword + meaning + metadata, with a grounded answer mode and manager admin. React static frontend at / + FastAPI backend at /backend, backed by grid-shared Mongo. Edition-gate first, scaffold, put the code under services/web/ + services/backend/, declare needs:{database:true} (NO vector #1545), wire the web+backend+refresh services, set the embeddings + source + manager secrets, deploy async, poll to a live URL, then Refresh now (or wait for the daily cron) to index."
-recipe: "edition-gate -> auth+grid -> grid_init -> fetch template + read AGENTS.md -> put code under services/web + services/backend, set cloudgrid.yaml active fields -> grid secrets set (embeddings + source + MANAGER_PASSWORD_HASH) -> optional grid dev -> grid plug (async, poll) -> Refresh now to index -> return live URL"
+recipe: "edition-gate -> auth+grid -> grid_create_project -> fetch template + read AGENTS.md -> put code under services/web + services/backend, set cloudgrid.yaml active fields -> grid secrets set (embeddings + source + MANAGER_PASSWORD_HASH) -> optional grid dev -> grid plug (async, poll) -> Refresh now to index -> return live URL"
 ---
 
 # Workflow: semantic-search
@@ -42,13 +42,13 @@ the **local edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_init` an app `<name>` FIRST — it creates the entity +
+`grid_create_project` an app `<name>` FIRST — it creates the entity +
 `.cloudgrid/link.json` and a starter `cloudgrid.yaml` with empty `services: {}`
 (`plug` needs a linked directory).
 
 ## 4. Fetch the template and READ AGENTS.md
 
-`grid_fetch("template", "semantic-search")`. Read **`AGENTS.md`** before
+`grid_get_template("template", "semantic-search")`. Read **`AGENTS.md`** before
 writing anything — it defines the file tree, the `documents` + `chunks`
 collections + fields, the Mongo injection, the pluggable source adapter, the
 embeddings config point, the secrets, the deploy flow, and the four baked-in
@@ -111,7 +111,7 @@ the cron **vendors** the backend `app/` modules it needs into
 
 Store all of these with `grid secrets set KEY=VALUE` (never commit them; the app
 reads them lazily inside functions, never at import). Non-secret public config →
-`grid_env`. Do NOT set `DATABASE_MONGODB_URL` yourself — the grid injects it.
+`grid_set_env`. Do NOT set `DATABASE_MONGODB_URL` yourself — the grid injects it.
 
 The app starts and passes `GET /backend/health` with **none** of these set;
 search/indexing degrade to a clear "not indexed / missing secret" state.
@@ -123,7 +123,7 @@ 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.

package/src/corpus/workflows/status-page.md

@@ -4,7 +4,7 @@ when: status page, service status, uptime page, incident history, is-it-down pag
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure, status baked into the page. Publishes as an inspiration (instant, works on hosted) via grid_plug.
+capabilities_note: static — no infrastructure, status baked into the page. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
 summary: Fetch the status-page template, fill it with the user's components and incidents, deploy it, and return the live share URL.
 ---
 
@@ -15,7 +15,7 @@ recipe. This is a display-only static page — the status is baked into the mark
 there is no live polling. Do not ask setup questions first; use sensible defaults
 and build.
 
-1. **Fetch the template.** Call `grid_fetch("template", "status-page")` to load
+1. **Fetch the template.** Call `grid_get_template("template", "status-page")` to load
    the self-contained HTML status page (overall banner, component list with
    up/degraded/down pills, per-component uptime bars, incident history).
 2. **Fill the template.** Replace the placeholders with the user's content:

package/src/corpus/workflows/subscription-management.md

@@ -49,18 +49,18 @@ A subscription-management app is a built + deployed container. It requires the
 Fetch the template and read its structure guide — this is the core of the
 workflow:
 
-- `grid_fetch("template", "subscription-management")` — the `cloudgrid.yaml` +
+- `grid_get_template("template", "subscription-management")` — the `cloudgrid.yaml` +
   **`AGENTS.md`**. AGENTS.md has the file tree, the Mongo collections
   (`customers`, `subscriptions`), the CloudGrid injection table, and the Stripe
   change-plan / cancel / billing-portal / webhook wiring. **Read it fully before
   building.**
-- `grid_fetch("template", "app-with-data")` — the proven Next.js + Mongo
+- `grid_get_template("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
 
-`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 write the app under **`services/web/`** and
 set `cloudgrid.yaml` to the active shape below.
@@ -109,12 +109,12 @@ never set `needs:` and `requires:` together (the validator rejects it).
 
 ## 6. Config / secrets
 
-- Stripe secrets → `grid_secrets` (set the vault items `stripe-live-key` and
+- Stripe secrets → `grid_set_secret` (set the vault items `stripe-live-key` and
   `stripe-webhook-secret` that the `vault:` block maps from). The deployer
   injects each as its env var at runtime and under `grid dev`. Add
   `auth-provider-key` too if you use an auth SDK.
 - Non-secret config (Stripe publishable key `NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY`,
-  price ids, auth publishable key) → `grid_env` / `services.web.env`.
+  price ids, auth publishable key) → `grid_set_env` / `services.web.env`.
 - Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` / legacy
   `MONGODB_URL`) — the grid injects them.
 
@@ -125,7 +125,7 @@ and vault secrets 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.

package/src/corpus/workflows/task-manager.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", "task-manager")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "task-manager")`. It is a minimal, real Next.js +
    `mongodb`-driver task manager under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/PATCH/DELETE route on a
    `tasks` collection (PATCH toggles done), a server-component page, and a client
@@ -82,13 +82,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/ticket-system.md

@@ -37,7 +37,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:
@@ -65,7 +65,7 @@ and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
    `services.web`, and `needs.database` uncommented — so it deploys to exactly
    those active fields.
 2. Fetch the template for the Mongo wiring + CRUD shape:
-   `grid_fetch("template", "ticket-system")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "ticket-system")`. It is a minimal, real Next.js +
    `mongodb`-driver app under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/PATCH (status)/DELETE route on a `tickets` collection, a
    server-component page, and a client component.
@@ -82,13 +82,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/time-tracking.md

@@ -38,7 +38,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:
@@ -63,7 +63,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", "time-tracking")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "time-tracking")`. It is a minimal, real Next.js +
    `mongodb`-driver time tracker under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/DELETE route on an `entries`
    collection, a server-component page, and a client form that also renders
@@ -85,13 +85,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/travel-booking.md

@@ -46,12 +46,12 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Read the blueprint, then scaffold
 
-1. Fetch the blueprint: `grid_fetch("template", "travel-booking")`. **Read its
+1. Fetch the blueprint: `grid_get_template("template", "travel-booking")`. **Read its
    `AGENTS.md`** — it is the structure guide (file tree under `services/web/`, the
    `flights` / `hotels` / `bookings` / `trips` collections + the overbooking
    guard, how CloudGrid injects the DB and vault secrets, how to wire Stripe +
    auth, and the trip-reminder-cron design).
-2. `grid_init` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
+2. `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.
 
@@ -88,9 +88,9 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 5. Config (secrets)
 
-- Payment/auth secrets → add the vault items with `grid_secrets` (e.g.
+- Payment/auth secrets → add the vault items with `grid_set_secret` (e.g.
   `stripe-live-key`, `stripe-webhook-secret`, `auth-provider-key`) BEFORE plug so
-  the `vault:` mappings resolve. Non-secret config → `grid_env`.
+  the `vault:` mappings resolve. Non-secret config → `grid_set_env`.
 - Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` / legacy
   `MONGODB_URL`) — the grid injects them.
 
@@ -102,7 +102,7 @@ require it.
 
 ## 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/waitlist.md

@@ -4,7 +4,7 @@ when: waitlist, coming soon, early access, join the list, launch page, sign-up t
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. The email form posts to a configurable mailto/external endpoint; it does NOT store signups. Publishes as an inspiration (instant, works on hosted) via grid_plug.
+capabilities_note: static — no infrastructure. The email form posts to a configurable mailto/external endpoint; it does NOT store signups. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
 summary: Fetch the waitlist template, fill it with the user's launch copy, wire the form to a mailto or external endpoint, deploy it, and return the live share URL.
 ---
 
@@ -22,7 +22,7 @@ NOT store signups anywhere on CloudGrid. To actually **store** waitlist signups
 (`needs: { database: true }`) — that is a CRUD app, coming in the crud-app
 archetype (Wave 1b). Do not claim this static page persists data.
 
-1. **Fetch the template.** Call `grid_fetch("template", "waitlist")` to load
+1. **Fetch the template.** Call `grid_get_template("template", "waitlist")` to load
    the self-contained HTML waitlist page (hero, email form, social-proof counter).
 2. **Fill the template.** Replace the placeholders with the user's content:
    - The product name, coming-soon headline, and subheadline.