@cloudgrid-io/mcp 0.20.4 → 0.20.6

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

@@ -4,7 +4,7 @@ when: single-page docs, a quick guide/manual/README-as-a-page, small knowledge b
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure, content baked into the page. Publishes as an inspiration (instant, works on hosted) via grid_plug.
+capabilities_note: static — no infrastructure, content baked into the page. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
 summary: Fetch the docs-site template, fill it with the user's documentation, deploy it, and return the live share URL.
 ---
 
@@ -14,7 +14,7 @@ Detect the intent ("build me a docs site / documentation for X") and follow this
 recipe. For a REST API endpoint reference specifically, use `api-docs`. Do not
 ask setup questions first; use sensible defaults and build.
 
-1. **Fetch the template.** Call `grid_fetch("template", "docs-site")` to load
+1. **Fetch the template.** Call `grid_get_template("template", "docs-site")` to load
    the self-contained HTML docs layout (sidebar nav, content column, code blocks,
    client-side search box).
 2. **Fill the template.** Replace the placeholders with the user's content:

package/src/corpus/workflows/erp.md

@@ -45,7 +45,7 @@ requires the **local edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Fetch the blueprint + read AGENTS.md
 
-`grid_fetch("template", "erp")`. It returns `cloudgrid.yaml`, `AGENTS.md` (the
+`grid_get_template("template", "erp")`. It returns `cloudgrid.yaml`, `AGENTS.md` (the
 structure guide), and the README — **no app code**. Read `AGENTS.md` end to end
 before writing anything: it defines the `services/web/` file tree, the Mongo
 collections + fields per module, how CloudGrid injects the DB and the
@@ -56,7 +56,7 @@ all four at once.
 
 ## 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 (a) build the app under **`services/web/`**
 following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
@@ -97,8 +97,8 @@ following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
 ## 6. Config
 
 - Create the vault items the `vault:` block references (the auth provider's
-  backend key and the Stripe secret key) — `grid_secrets` / vault UI. Never
-  commit them. Publishable/front-end auth keys → `grid_env`.
+  backend key and the Stripe secret key) — `grid_set_secret` / vault UI. Never
+  commit them. Publishable/front-end auth keys → `grid_set_env`.
 - Register the deployed `/api/finance/webhook` URL as the Stripe webhook endpoint
   once the app is live.
 - Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` or the
@@ -111,7 +111,7 @@ vault env vars 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/event-board.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", "event-board")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "event-board")`. It is a minimal, real Next.js +
    `mongodb`-driver event board under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/DELETE route on an `events`
    collection, a server-component page that reads events sorted by date, 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/expense-tracker.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", "expense-tracker")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "expense-tracker")`. It is a minimal, real Next.js +
    `mongodb`-driver expense tracker under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/DELETE route on an `expenses`
    collection, a server-component page, and a client form with a table + totals
@@ -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/feature-request-board.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", "feature-request-board")`. It is a minimal, real
+   `grid_get_template("template", "feature-request-board")`. It is a minimal, real
    Next.js + `mongodb`-driver board under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/PATCH/DELETE route on a
    `requests` collection (PATCH does an atomic `$inc` upvote), a server-component
@@ -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/financial-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", "financial-dashboard")`. It is a minimal, real
+   `grid_get_template("template", "financial-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 an `entries`
    collection, a server-component page that computes income/expense/net totals,
@@ -84,13 +84,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/forum.md

@@ -58,11 +58,11 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Read the blueprint, then scaffold
 
-1. **Fetch the blueprint: `grid_fetch("template", "forum")`** and read
+1. **Fetch the blueprint: `grid_get_template("template", "forum")`** and read
    `AGENTS.md` — it defines the file tree, the `threads` / `posts` / `users`
    collections + fields, the nesting model, and the CloudGrid wiring. This is the
    spec you build to.
-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. Then write the app under
    **`services/web/`** and fill `cloudgrid.yaml` to the shape below.
@@ -108,14 +108,14 @@ Mention that the user can `grid dev` to run locally against the injected Mongo
 
 ## 6. Config
 
-- Auth-provider keys / secrets → the `vault:` block + `grid_secrets`. Non-secret
-  config → `grid_env`.
+- Auth-provider keys / secrets → the `vault:` block + `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/hr-portal.md

@@ -43,7 +43,7 @@ A persistent, auth-gated app is a built + deployed container. It requires the
 
 ## 3. Fetch the blueprint + read AGENTS.md
 
-`grid_fetch("template", "hr-portal")`. It returns `cloudgrid.yaml`, `AGENTS.md`
+`grid_get_template("template", "hr-portal")`. It returns `cloudgrid.yaml`, `AGENTS.md`
 (the structure guide), and the README — **no app code**. Read `AGENTS.md` end to
 end before writing anything: it defines the `services/web/` file tree, the Mongo
 collections + fields, how CloudGrid injects the DB and vault-backed auth keys, how
@@ -51,7 +51,7 @@ to wire employee/admin auth, and the deploy steps.
 
 ## 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 (a) build the app under **`services/web/`**
 following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
@@ -90,8 +90,8 @@ following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
 ## 6. Config
 
 - Create the vault items the `vault:` block references (the auth provider's
-  secret + publishable keys) — `grid_secrets` / vault UI. Never commit them.
-- Non-secret config → `grid_env`.
+  secret + publishable keys) — `grid_set_secret` / vault UI. Never commit them.
+- 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.
 
@@ -102,7 +102,7 @@ vault env vars 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/internal-tools-portal.md

@@ -45,7 +45,7 @@ A persistent, auth-gated app is a built + deployed container. It requires the
 
 ## 3. Fetch the blueprint + read AGENTS.md
 
-`grid_fetch("template", "internal-tools-portal")`. It returns `cloudgrid.yaml`,
+`grid_get_template("template", "internal-tools-portal")`. It returns `cloudgrid.yaml`,
 `AGENTS.md` (the structure guide), and the README — **no app code**. Read
 `AGENTS.md` end to end before writing anything: it defines the `services/web/`
 file tree, the Mongo collections + fields, the tool registry, how CloudGrid injects
@@ -54,7 +54,7 @@ deploy steps.
 
 ## 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 (a) build the app under **`services/web/`**
 following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
@@ -99,9 +99,9 @@ following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
 ## 6. Config
 
 - Create the vault items the `vault:` block references (the auth provider's
-  secret + publishable keys, plus any per-tool API secrets) — `grid_secrets` /
+  secret + publishable keys, plus any per-tool API secrets) — `grid_set_secret` /
   vault UI. Never commit them.
-- Non-secret config → `grid_env`.
+- 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.
 
@@ -112,7 +112,7 @@ vault env vars 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/inventory.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", "inventory")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "inventory")`. 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 (adjust qty)/DELETE route on an `items` 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/invoice.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", "invoice")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "invoice")`. 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/DELETE route on an `invoices` 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/job-board.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", "job-board")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "job-board")`. 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 `jobs` 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/kanban.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:
@@ -62,7 +62,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", "kanban")`. It is a minimal, real Next.js +
+   `grid_get_template("template", "kanban")`. It is a minimal, real Next.js +
    `mongodb`-driver board under `services/web/`: a lazy client in
    `services/web/lib/db.js`, an App-Router GET/POST/PATCH/DELETE route on a
    `cards` collection (PATCH moves a card between columns), a server-component
@@ -73,7 +73,7 @@ and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
    runtime.
    - **Put the DB connection behind a lazy getter — never read the connection
      string at module top level, or `next build` fails.**
-   - (Optional) fetch `grid_fetch("example", "kanban")` for a richer filled
+   - (Optional) fetch `grid_get_template("example", "kanban")` for a richer filled
      reference to imitate.
 
 ## 5. (Optional) Run locally
@@ -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/landing-page.md

@@ -4,7 +4,7 @@ when: landing page, marketing page, product page, hero page, coming-soon, waitli
 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 landing-page template, fill it with the user's content, deploy it, and return the live share URL.
 ---
 
@@ -13,9 +13,9 @@ summary: Fetch the landing-page template, fill it with the user's content, deplo
 Detect the intent ("build me a landing page / marketing page for X") and follow
 this recipe. Do not ask setup questions first; use sensible defaults and build.
 
-1. **Fetch the template.** Call `grid_fetch("template", "landing-page")` to
+1. **Fetch the template.** Call `grid_get_template("template", "landing-page")` to
    load the self-contained HTML landing-page template.
-2. **(Optional) Fetch the example.** Call `grid_fetch("example", "landing-page")`
+2. **(Optional) Fetch the example.** Call `grid_get_template("example", "landing-page")`
    to see a filled landing page as a reference for tone and structure.
 3. **Fill the template.** Replace the placeholders with the user's content:
    - The product name, hero headline, and subheadline.

package/src/corpus/workflows/lms.md

@@ -44,7 +44,7 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 ## 3. Read the blueprint
 
 Fetch the structure guide and read it before writing anything:
-`grid_fetch("template", "lms")`. `AGENTS.md` is the CloudGrid-specific spec for
+`grid_get_template("template", "lms")`. `AGENTS.md` is the CloudGrid-specific spec for
 this app — the file tree under `services/web/`, the Mongo collections
 (users/courses/modules/lessons/assignments/enrollments/progress/submissions/grades),
 how the grid injects Mongo + the vault auth secret, the instructor/student role
@@ -53,7 +53,7 @@ you build it from the guide.
 
 ## 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 (a) write the app under **`services/web/`**
 per the AGENTS.md tree, and (b) fill `cloudgrid.yaml` to the shape below.
@@ -91,15 +91,15 @@ needs:
 
 ## 6. Config
 
-- Secrets → `grid_secrets` (e.g. `grid secrets set auth-provider-key`;
+- Secrets → `grid_set_secret` (e.g. `grid secrets set auth-provider-key`;
   `stripe-live-key`/`stripe-webhook-secret` only for paid courses). Non-secret
-  config → `grid_env` (e.g. the auth publishable key).
+  config → `grid_set_env` (e.g. the auth publishable key).
 - 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/marketplace.md

@@ -40,7 +40,7 @@ requires the **local edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Fetch the blueprint and READ AGENTS.md
 
-`grid_fetch("template", "marketplace")`. The deliverable is the **`AGENTS.md`
+`grid_get_template("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,
@@ -54,7 +54,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:
@@ -97,7 +97,7 @@ Generate the files under `services/web/` per the guide:
 - 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 → `grid_env`.
+  `grid secrets set auth-provider-key …`. Non-secret public config → `grid_set_env`.
 - Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` / legacy
   `MONGODB_URL`) — the grid injects them.
 
@@ -108,7 +108,7 @@ 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/membership-site.md

@@ -43,17 +43,17 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 Fetch the template and read its structure guide — this is the core of the
 workflow:
 
-- `grid_fetch("template", "membership-site")` — the `cloudgrid.yaml` +
+- `grid_get_template("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.**
-- `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.
@@ -98,11 +98,11 @@ never set `needs:` and `requires:` together (the validator rejects it).
 
 ## 6. Config / secrets
 
-- Stripe + auth secrets → `grid_secrets` (set the vault items `stripe-live-key`,
+- Stripe + auth secrets → `grid_set_secret` (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) →
-  `grid_env` / `services.web.env`.
+  `grid_set_env` / `services.web.env`.
 - Do **NOT** set the DB connection vars yourself (`DATABASE_MONGODB_URL` / legacy
   `MONGODB_URL`) — the grid injects them.
 
@@ -113,7 +113,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/monitoring-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", "monitoring-dashboard")`. It is a minimal, real
+   `grid_get_template("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
@@ -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.