@cloudgrid-io/mcp 0.20.3 → 0.20.5

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@cloudgrid-io/mcp",
-  "version": "0.20.3",
-  "description": "MCP server for CloudGrid. Three editions: a local stdio server (full toolset), a hosted web server (light, CLI-free toolset), and a public docs server (search_cloudgrid_documentation) over MCP Streamable HTTP.",
+  "version": "0.20.5",
+  "description": "Use CloudGrid via MCP to brainstorm, build, deploy, and improve apps, games, websites, dashboards, and tools and get a live URL - templates, recipes, managed databases and AI, instant single-page publish, and full-app deploys, for developers and non-technical users. Three editions: local stdio (full toolset), hosted web (light, CLI-free), and a public docs-search server, over MCP.",
   "type": "module",
   "bin": {
     "cloudgrid-mcp": "src/index.js"
@@ -27,6 +27,8 @@
     "test:content": "node test/content-handling.test.mjs",
     "test:self-healing": "node test/self-healing.test.mjs",
     "test:grid-picker": "node test/grid-picker.test.mjs",
+    "test:plug-timeout": "node test/plug-timeout.test.mjs",
+    "test:manifest-confirm": "node test/manifest-confirm.test.mjs",
     "test:drift-guard": "node test/drift-guard.mjs",
     "smoke:drop": "node test/smoke-drop.mjs",
     "smoke:login": "node test/smoke-login.mjs",

package/src/corpus/capability-map.md

@@ -4,19 +4,19 @@ This is the index an LLM uses to turn a user request into the right CloudGrid
 template, the way Superpowers matches a skill's `when:`. Match the request to a
 template by its `when:` triggers, adopt that template's `needs:`, then deploy:
 
-> **One deploy verb: `grid_plug`.** Classify the artifact to pick the shape —
+> **One deploy verb: `grid_deploy`.** Classify the artifact to pick the shape —
 > ONE self-contained HTML page (CSS+JS inline, images/fonts as data: URIs) →
 > **inspiration**; separate files/folders/assets or any `needs:` → **runtime app**.
 
 - **single self-contained HTML page → inspiration** (instant, any client / any
-  edition) via `grid_plug` with the inline `html` param.
+  edition) via `grid_deploy` with the inline `html` param.
 - **separate files/folders/assets, or anything needing `needs:` → runtime app**
-  (async build, **local edition** only) via `grid_plug` on a linked folder.
+  (async build, **local edition** only) via `grid_deploy` on a linked folder.
 
-Fetch this doc any time with `grid_fetch("doc", "capability-map")`. For the full
+Fetch this doc any time with `grid_get_template("doc", "capability-map")`. For the full
 cloudgrid.yaml schema (every field, the `needs:` injection table, the
 requires-vs-needs caveat, validation rules), fetch the companion reference:
-`grid_fetch("doc", "cloudgrid-yaml")`.
+`grid_get_template("doc", "cloudgrid-yaml")`.
 
 ## The 60 templates
 
@@ -143,7 +143,7 @@ chunks in Mongo and cosine-rank in-app until it lands.
 `needs:` is a MAP declaring infrastructure capabilities. Values are `true` or an
 engine hint. Cron is NOT a need — it is a **service type** (`type: cron` with
 `schedule` + `timezone`). See the full cloudgrid.yaml reference §5–§6 via
-`grid_fetch("doc", "cloudgrid-yaml")`.
+`grid_get_template("doc", "cloudgrid-yaml")`.
 
 | `needs:` key | Provides | Injected env var(s) | Status |
 |---|---|---|---|
@@ -180,9 +180,9 @@ engine hint. Cron is NOT a need — it is a **service type** (`type: cron` with
    work → a `type: cron` service (Python/Node, supported on 0.14.0). (Held for now:
    RAG's ideal `vector: pgvector`, #1545 — store embeddings in Mongo until it lands.)
 3. One self-contained HTML page (`needs: none`, assets inlined) → publish as an
-   inspiration with `grid_plug` and the inline `html` param (instant, any
+   inspiration with `grid_deploy` and the inline `html` param (instant, any
    edition). Separate files/folders/assets, or anything with a `needs:` →
-   runtime, local edition, `grid_plug` a linked folder, then poll to a live URL.
+   runtime, local edition, `grid_deploy` a linked folder, then poll to a live URL.
 
 ## FAQ
 

package/src/corpus/cloudgrid-yaml.md

@@ -5,9 +5,9 @@
 > of that reference — practically complete, not a verbatim dump. **Keep in sync**
 > with the upstream: when the platform reference changes, update this doc.
 >
-> Fetch this doc any time with `grid_fetch("doc", "cloudgrid-yaml")`.
+> Fetch this doc any time with `grid_get_template("doc", "cloudgrid-yaml")`.
 > For matching an intent to a template, see the companion
-> `grid_fetch("doc", "capability-map")`.
+> `grid_get_template("doc", "capability-map")`.
 
 `cloudgrid.yaml` is the manifest at the **root of your project** that defines your
 entity (an app or an agent). It declares the services your entity runs, the
@@ -28,7 +28,7 @@ These are the shapes verified against live deploys. Copy one and adapt it.
 ### Single HTML page → deploys as an inspiration (instant)
 
 One self-contained HTML page (CSS+JS inline, images/fonts as data: URIs). No
-`needs:`. Publishes instantly via `grid_plug` with the inline `html` param,
+`needs:`. Publishes instantly via `grid_deploy` with the inline `html` param,
 works on any edition (hosted or local).
 
 ```yaml
@@ -541,7 +541,7 @@ Bake these into any yaml you author:
   it**; use `needs:` instead.
 - **`needs:` and `requires:` together are HARD-REJECTED** by the validator ("use
   one or the other"). So author **`needs:`-only** — never set both.
-- **A single self-contained HTML page deploys as an inspiration** via `grid_plug`
+- **A single self-contained HTML page deploys as an inspiration** via `grid_deploy`
   with the inline `html` param — instant, synchronous, works on the hosted edition
   and any client.
 - **A `cloudgrid.yaml` with `services:` makes it a runtime** — async build,
@@ -567,5 +567,5 @@ needs:
 ---
 
 *This doc is the agent-facing distribution of the platform's canonical
-`cloudgrid-yaml-reference.md`. See also `grid_fetch("doc", "capability-map")`
+`cloudgrid-yaml-reference.md`. See also `grid_get_template("doc", "capability-map")`
 for matching a user intent to a template + the `needs:` injection status.*

package/src/corpus/cookbook.md

@@ -74,7 +74,7 @@ curl -sS -X POST https://api.cloudgrid.io/api/v2/plug \
 The response includes `url` (the live link — use it verbatim), `entity_id`,
 `owner_token` (keep both to update the page later), and `claim_url` (sign in
 before it expires to keep it). This is what the `cloudgrid:plug` skill and the
-`grid_plug` MCP tool (inline `html` param) do for you. It is anonymous and serves
+`grid_deploy` MCP tool (inline `html` param) do for you. It is anonymous and serves
 inspirations only; a full app needs the signed-in `plug` flow above.
 
 ## Update your drop in place

package/src/corpus/skill-claim.md

@@ -69,5 +69,5 @@ new_expires_at, role_granted: "owner", ... }`.
 ## Notes
 
 - One pickup claims one entity. To claim several, repeat with each entity id + token.
-- The MCP `grid_claim` tool does this for you, and remembers the entity id +
+- The MCP `grid_claim_anonymous_deploy` tool does this for you, and remembers the entity id +
   token from the last anonymous drop so you can claim with no arguments.

package/src/corpus/skill-plug.md

@@ -58,7 +58,7 @@ curl -sS -X POST https://api.cloudgrid.io/api/v2/plug \
   -F "artifact=@/path/to/index.html;type=text/html"
 ```
 
-The MCP `grid_plug` tool does all of this for you: pass the page as its inline
+The MCP `grid_deploy` tool does all of this for you: pass the page as its inline
 `html` param (it materializes one `index.html` and handles anon/claim/re-plug).
 
 ### Re-plug: update the same URL in place

package/src/corpus/skills-readme.md

@@ -33,7 +33,7 @@ behalf: scaffold, deploy, tail logs, share, read feedback. Everything here is fr
    ```
 
    One install wires up everything: the skills, the SessionStart orientation
-   hook, and the CloudGrid MCP server (`grid_start`, `grid_fetch`, and the
+   hook, and the CloudGrid MCP server (`grid_start`, `grid_get_template`, and the
    CLI-wrapping tools). The MCP auto-starts when the plugin is enabled — no
    separate `claude mcp add` needed.
 

package/src/corpus/templates/ai-knowledge-base/AGENTS.md

@@ -208,7 +208,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:{ai:true,

package/src/corpus/templates/ai-knowledge-base/index.md

@@ -11,7 +11,7 @@ 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", "ai-knowledge-base")` → read
+- **Structure guide:** `grid_get_template("template", "ai-knowledge-base")` → read
   **`AGENTS.md`** (file tree, Mongo collections, CloudGrid injection table, the
   RAG loop, the pgvector #1545 note, optional auth/payments, deploy steps).
 

package/src/corpus/templates/api-docs/README.md

@@ -3,12 +3,12 @@
 A single self-contained HTML API reference: a sidebar endpoint list, per-endpoint method badges (GET / POST / PUT / DELETE), a params table, and request / response examples in code blocks.
 
 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", "api-docs")`, then replace the
+Fetch the template with `grid_get_template("template", "api-docs")`, then replace the
 placeholders:
 
    - The API name, base URL, and auth note.

package/src/corpus/templates/api-docs/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", "api-docs")` and fill in the user's content.
+`grid_get_template("template", "api-docs")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

@@ -12,7 +12,7 @@ what make it deploy.
 The proven persistent shape is `app-with-data` (Next.js + Mongo). This blueprint
 extends it with auth, availability/slot logic, and optional Stripe deposits.
 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
 
@@ -102,7 +102,7 @@ clients racing for the same slot cannot both win.
     STRIPE_KEY: stripe-live-key                  # only if you take deposits
     STRIPE_WEBHOOK_SECRET: stripe-webhook-secret # only if you take deposits
   ```
-  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.AUTH_PROVIDER_KEY`,
   `process.env.STRIPE_KEY`, …) at runtime and under `grid dev`. Do NOT commit
   keys; do NOT set secrets in `services.web.env` (that block is for non-secret
@@ -163,18 +163,18 @@ you want client accounts.
 
 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. (Leave the `reminders` cron service COMMENTED — see §7.)
-4. Set the secrets: `grid_secrets` for `auth-provider-key` (and, if taking
+4. Set the secrets: `grid_set_secret` for `auth-provider-key` (and, if taking
    deposits, `stripe-live-key`, `stripe-webhook-secret` — the vault item keys the
    `vault:` block maps from). Non-secret config (auth publishable key, price ids)
-   → `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.
@@ -188,7 +188,7 @@ An appointment-booking 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 "book us" landing page (via `grid_plug`) instead, then stop the runtime
+static "book us" landing page (via `grid_deploy`) instead, then stop the runtime
 path.
 
 ## 7. Reminders (cron — PENDING platform issue #1543)

package/src/corpus/templates/appointment-booking/index.md

@@ -10,8 +10,8 @@ the providers/services/slot rules, then deploy (async — poll to a live URL).
 Local edition only.
 
 **Fetch the bundle:**
-- `grid_fetch("template", "appointment-booking")` — 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", "appointment-booking")` — 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:**
 
@@ -26,7 +26,7 @@ Local edition only.
    the getter, never at module top level (top-level read fails `next build`).
 4. **Secrets via the `vault:` block** → env vars. `AUTH_PROVIDER_KEY` (and, for
    deposits, `STRIPE_KEY` / `STRIPE_WEBHOOK_SECRET`) map to vault items; set them
-   with `grid_secrets`, and the deployer injects them at runtime. Read lazily;
+   with `grid_set_secret`, and the deployer injects them at runtime. Read lazily;
    do not commit keys or put secrets in `services.web.env`.
 5. **No double-booking.** `appointments` is the source of truth for "taken";
    compute open slots as availability minus booked, re-check at write time, and
@@ -65,8 +65,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). If taking deposits, register the
 `/api/webhook` URL in Stripe and re-plug. Re-plug the same entity to update the
 same URL.

package/src/corpus/templates/approval-workflow/AGENTS.md

@@ -9,7 +9,7 @@ then build the Next.js + Mongo app on the grid following the shape below.
 The proven base shape is `app-with-data` (Next.js + Mongo, App Router, lazy DB
 getter). This blueprint extends it with a state machine, roles, and
 notifications. Fetch that template for the concrete Mongo/CRUD wiring:
-`grid_fetch("template", "app-with-data")`, then adapt it to the collections
+`grid_get_template("template", "app-with-data")`, then adapt it to the collections
 here.
 
 ## 1. File tree
@@ -146,7 +146,7 @@ routes and the UI agree on what is legal.
 
 ## 6. Deploy steps
 
-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 because
    `plug` needs a linked directory.
 2. Fill `cloudgrid.yaml` to this blueprint's shape (copy this template's file):

package/src/corpus/templates/approval-workflow/index.md

@@ -14,14 +14,14 @@ machine, and CloudGrid wiring, then build the app under `services/web/`.
 
 ## Fetch bundle
 
-- `grid_fetch("template", "approval-workflow")` → this blueprint:
+- `grid_get_template("template", "approval-workflow")` → this blueprint:
   - `AGENTS.md` — file tree, Mongo collections (`users`, `requests`, `steps`,
     `audit`), the state machine, auth/payments wiring, deploy steps, edition note.
   - `cloudgrid.yaml` — the full-annotated reference with only `name`,
     `services.web { type: nextjs, path: / }`, and `needs: { database: true }`
     active, plus a commented `vault:` block for `AUTH_PROVIDER_KEY`.
   - `README.md` — one-paragraph what/why.
-- `grid_fetch("template", "app-with-data")` → the concrete Next.js + Mongo
+- `grid_get_template("template", "app-with-data")` → the concrete Next.js + Mongo
   CRUD wiring (lazy `lib/db.js`, App Router route, server page) to adapt from.
 
 ## Key rules

package/src/corpus/templates/billing-dashboard/index.md

@@ -80,7 +80,7 @@ needs:
 
 ## Build it
 
-Fetch `grid_fetch("template", "billing-dashboard")` and read **`AGENTS.md`** — it
+Fetch `grid_get_template("template", "billing-dashboard")` and read **`AGENTS.md`** — it
 has the checkout + webhook + usage 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/calendar-scheduler/AGENTS.md

@@ -200,7 +200,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/calendar-scheduler/index.md

@@ -11,7 +11,7 @@ following it.
 `AGENTS.md`. Fetch the bundle, read `AGENTS.md`, then generate the files under
 `services/web/` and deploy.
 
-- **Structure guide:** `grid_fetch("template", "calendar-scheduler")` → read
+- **Structure guide:** `grid_get_template("template", "calendar-scheduler")` → read
   **`AGENTS.md`** (file tree, Mongo collections, CloudGrid injection table,
   optional auth/payments layers, the cron reminder shape blocked on #1543, deploy
   steps, edition note).

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

@@ -3,12 +3,12 @@
 A single self-contained HTML changelog / release-notes page: reverse-chronological versioned entries, each with a date and tagged change items (added / fixed / changed / removed).
 
 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", "changelog")`, then replace the
+Fetch the template with `grid_get_template("template", "changelog")`, then replace the
 placeholders:
 
    - The product name and page intro.

package/src/corpus/templates/changelog/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", "changelog")` and fill in the user's content.
+`grid_get_template("template", "changelog")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

package/src/corpus/templates/company-website/README.md

@@ -10,13 +10,13 @@ wire it to your own email service or form endpoint if you want real submissions.
 
 ## 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", "company-website")` and fill in the user's content.
+`grid_get_template("template", "company-website")` and fill in the user's content.
 
 ## How to adapt
 

package/src/corpus/templates/company-website/cloudgrid.yaml

@@ -11,7 +11,7 @@
 # ignored by the parser, so the file deploys to exactly the active fields.
 #
 # company-website is a STATIC template (type: static, path: /) with no needs.
-# The fast path deploys the page as an INSPIRATION via grid_plug (instant,
+# The fast path deploys the page as an INSPIRATION via grid_deploy (instant,
 # works on hosted). This cloudgrid.yaml is the reference for plugging it as an
 # OWNED static runtime; the active fields are exactly: name + services.web.
 #

package/src/corpus/templates/company-website/index.md

@@ -6,13 +6,13 @@ Inline CSS + inline JS only (no external scripts, stylesheets, fonts, or CDNs).
 
 ## 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", "company-website")` and fill in the user's content.
+`grid_get_template("template", "company-website")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

package/src/corpus/templates/course-platform/index.md

@@ -7,7 +7,7 @@ Next.js + Mongo app with auth and payments.
 **This is a blueprint, not app code.** It ships the correct `cloudgrid.yaml` and
 an `AGENTS.md` structure guide. Read `AGENTS.md`, then build the app under
 `services/web/` following it. Fetch the guide with
-`grid_fetch("template", "course-platform")`.
+`grid_get_template("template", "course-platform")`.
 
 **Key rules:**
 

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

@@ -16,7 +16,7 @@
 # THIS TEMPLATE (dashboard): 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/dashboard/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", "dashboard")` and fill in the user's content.
+`grid_get_template("template", "dashboard")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

@@ -16,7 +16,7 @@
 # THIS TEMPLATE (deck): 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/deck/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", "deck")` and fill in the user's content.
+`grid_get_template("template", "deck")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

package/src/corpus/templates/docs-site/README.md

@@ -3,12 +3,12 @@
 A single self-contained HTML documentation site: a sidebar nav, a scrolling content column with headings and code blocks, and a client-side search box that filters the nav. No backend.
 
 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", "docs-site")`, then replace the
+Fetch the template with `grid_get_template("template", "docs-site")`, then replace the
 placeholders:
 
    - The project/doc name and the sidebar section links.

package/src/corpus/templates/docs-site/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", "docs-site")` and fill in the user's content.
+`grid_get_template("template", "docs-site")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

@@ -104,7 +104,7 @@ dev` and runtime.
   injects that vault item as `process.env.ENV_VAR`. This blueprint maps
   `AUTH_PROVIDER_SECRET_KEY` and `AUTH_PROVIDER_PUBLISHABLE_KEY`. Rename the env
   keys to whatever the provider SDK expects (see §4) and set the vault items with
-  `grid_secrets` / the org vault — do not commit keys.
+  `grid_set_secret` / the org vault — do not commit keys.
 - **AI (optional)** — if you add `needs: { ai: true }` (e.g. auto-moderation or
   summarize-thread), the grid injects **`AI_GATEWAY_URL`**; call it via
   `@cloudgrid-io/ai`. Not required for the base forum.
@@ -169,16 +169,16 @@ A forum is a runtime (built + deployed container) app — **local edition**
 
 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>` — 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. Write the app under `services/web/` per §1, then fill `cloudgrid.yaml` to the
    active shape: `name`, `services.web { type: nextjs, path: / }`, `needs:
    { database: true }`, and the `vault:` mappings for the auth keys.
-4. Set the auth secrets: `grid_secrets` (or the org vault) for the provider
+4. Set the auth secrets: `grid_set_secret` (or the org vault) for the provider
    keys. Do NOT set `DATABASE_MONGODB_URL` — the grid injects it.
 5. (Optional) `grid dev` to run locally against injected Mongo before shipping.
-6. `grid_plug` to deploy. A runtime deploy is **ASYNC** — the first response
+6. `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
    spinner.

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

@@ -7,7 +7,7 @@ moderation, on Next.js + grid-shared MongoDB, auth via a hosted provider
 under `services/web/` following it. The shape mirrors the proven `app-with-data`
 template (lazy Mongo getter, App-Router routes, `needs: { database: true }`).
 
-**Fetch the bundle:** `grid_fetch("template", "forum")` returns this
+**Fetch the bundle:** `grid_get_template("template", "forum")` returns this
 directory — `cloudgrid.yaml`, `AGENTS.md` (the structure guide), and this file.
 
 **Key rules:**

package/src/corpus/templates/hr-portal/index.md

@@ -28,7 +28,7 @@ Runtime app → **local edition only**, async deploy (poll to a live URL).
 
 ## Fetch bundle
 
-Fetch this blueprint with `grid_fetch("template", "hr-portal")`. It returns
+Fetch this blueprint with `grid_get_template("template", "hr-portal")`. It returns
 `cloudgrid.yaml`, `AGENTS.md` (the structure guide), and this README — no app
 code. Follow `AGENTS.md` to build, then `grid init → fill → grid plug → poll`.
 

package/src/corpus/templates/internal-tools-portal/index.md

@@ -34,7 +34,7 @@ Runtime app → **local edition only**, async deploy (poll to a live URL).
 
 ## Fetch bundle
 
-Fetch this blueprint with `grid_fetch("template", "internal-tools-portal")`. It
+Fetch this blueprint with `grid_get_template("template", "internal-tools-portal")`. It
 returns `cloudgrid.yaml`, `AGENTS.md` (the structure guide), and this README — no
 app code. Follow `AGENTS.md` to build, then `grid init → fill → grid plug → poll`.
 

package/src/corpus/templates/landing-page/cloudgrid.yaml

@@ -16,7 +16,7 @@
 # THIS TEMPLATE (landing-page): 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/landing-page/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", "landing-page")` and fill in the user's content.
+`grid_get_template("template", "landing-page")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)