@cloudgrid-io/mcp 0.16.2 → 0.17.0

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 gridctl_drop
+# runtime; the fast path is to deploy it as an INSPIRATION via grid_drop
 # (instant, and works on the hosted edition too).
 # ============================================================================
 

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

@@ -5,14 +5,14 @@ no `needs:`. State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`gridctl_drop`** (or `gridctl_plug` with the inline
+To publish this page, use **`grid_drop`** (or `grid_plug` 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 `gridctl_drop`.
+runtime (async, local edition only); the fast path is `grid_drop`.
 
 The fillable HTML is the real template — fetch it with
-`gridctl_fetch("template", "deck")` and fill in the user's content.
+`grid_fetch("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 `gridctl_drop` and works on every
+no external CDNs). It deploys instantly via `grid_drop` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in
 
-Fetch the template with `gridctl_fetch("template", "docs-site")`, then replace the
+Fetch the template with `grid_fetch("template", "docs-site")`, then replace the
 placeholders:
 
    - The project/doc name and the sidebar section links.
@@ -22,7 +22,7 @@ stylesheets, fonts, or large embedded media.
 ## Deploy
 
 - Hosted MCP edition: call the drop tool with the HTML.
-- Local MCP / CLI edition: write the HTML to a file and run `gridctl plug`.
+- Local MCP / CLI edition: write the HTML to a file and run `grid plug`.
 
 It deploys as an inspiration and returns a live share URL right away. Re-deploy
 with the same entity id to update the same URL.

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

@@ -5,14 +5,14 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`gridctl_drop`** (or `gridctl_plug` with the inline
+To publish this page, use **`grid_drop`** (or `grid_plug` 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 `gridctl_drop`.
+runtime (async, local edition only); the fast path is `grid_drop`.
 
 The fillable HTML is the real template — fetch it with
-`gridctl_fetch("template", "docs-site")` and fill in the user's content.
+`grid_fetch("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
-  `gridctl_secrets` / the org vault — do not commit keys.
+  `grid_secrets` / 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.
@@ -167,19 +167,19 @@ inline a key in code or `env:`.
 A forum is a runtime (built + deployed container) app — **local edition**
 (Claude Desktop / Claude Code / CLI), async build.
 
-1. `gridctl_login_status` → `gridctl_login` if needed. Respect the grid picker
+1. `grid_login_status` → `grid_login` if needed. Respect the grid picker
    (ask which grid if the user has more than one).
-2. `gridctl_init` an app `<name>` — creates the entity + `.cloudgrid/link.json`
+2. `grid_init` 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: `gridctl_secrets` (or the org vault) for the provider
+4. Set the auth secrets: `grid_secrets` (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. `gridctl_plug` to deploy. A runtime deploy is **ASYNC** — the first response
-   is `status: building`, not a live URL. Poll `gridctl_status` (or the returned
+6. `grid_plug` 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.
 7. Only once live, return the deployed app URL. Re-plug the SAME entity to update

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:** `gridctl_fetch("template", "forum")` returns this
+**Fetch the bundle:** `grid_fetch("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 `gridctl_fetch("template", "hr-portal")`. It returns
+Fetch this blueprint with `grid_fetch("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 `gridctl_fetch("template", "internal-tools-portal")`. It
+Fetch this blueprint with `grid_fetch("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 gridctl_drop
+# runtime; the fast path is to deploy it as an INSPIRATION via grid_drop
 # (instant, and works on the hosted edition too).
 # ============================================================================
 

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

@@ -5,14 +5,14 @@ no `needs:`. State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`gridctl_drop`** (or `gridctl_plug` with the inline
+To publish this page, use **`grid_drop`** (or `grid_plug` 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 `gridctl_drop`.
+runtime (async, local edition only); the fast path is `grid_drop`.
 
 The fillable HTML is the real template — fetch it with
-`gridctl_fetch("template", "landing-page")` and fill in the user's content.
+`grid_fetch("template", "landing-page")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

@@ -8,7 +8,7 @@ Next.js + Mongo app with role-based (instructor/student) auth.
 **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
-`gridctl_fetch("template", "lms")`.
+`grid_fetch("template", "lms")`.
 
 **Key rules:**
 

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

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

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

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

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

@@ -9,7 +9,7 @@ rules — they are what make it deploy.
 
 The proven persistent shape is `app-with-data` (Next.js + Mongo). This blueprint
 extends it with auth + Stripe. Fetch that template for the Mongo lazy-client and
-App-Router API pattern: `gridctl_fetch("template", "app-with-data")`.
+App-Router API pattern: `grid_fetch("template", "app-with-data")`.
 
 ## 1. File tree
 
@@ -78,7 +78,7 @@ A user is a member when a `memberships` doc for their `authId` has
     STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
     AUTH_PROVIDER_KEY: auth-provider-key
   ```
-  Set the vault items ONCE with `gridctl_secrets` (or `grid secrets set`), then
+  Set the vault items ONCE with `grid_secrets` (or `grid secrets set`), then
   the deployer injects each as the named env var (`process.env.STRIPE_KEY`, etc.)
   at runtime and under `grid dev`. Do NOT commit keys; do NOT set them in
   `services.web.env` (that block is for non-secret config only). Read them
@@ -130,21 +130,21 @@ A user is a member when a `memberships` doc for their `authId` has
 
 ## 5. Deploy steps
 
-1. `gridctl_login_status` → `gridctl_login` if needed. Respect the grid picker
+1. `grid_login_status` → `grid_login` if needed. Respect the grid picker
    (ask which grid if the user has more than one).
-2. `gridctl_init` an app `<name>` FIRST — it creates the entity, writes
+2. `grid_init` an app `<name>` FIRST — it creates the entity, writes
    `.cloudgrid/link.json`, and a `cloudgrid.yaml` with empty `services: {}`.
    `plug` needs a linked directory.
 3. Write the app under `services/web/` and set `cloudgrid.yaml` to the active
    shape: `name` + `services.web{type: nextjs, path: /}` + `needs:{database:true}`
    + the `vault:` block.
-4. Set the secrets: `gridctl_secrets` for `stripe-live-key`,
+4. Set the secrets: `grid_secrets` for `stripe-live-key`,
    `stripe-webhook-secret`, `auth-provider-key` (the vault item keys the
    `vault:` block maps from). Non-secret config (publishable auth key, price id)
-   → `gridctl_env` / `services.web.env`. Do NOT set `DATABASE_MONGODB_URL`
+   → `grid_env` / `services.web.env`. Do NOT set `DATABASE_MONGODB_URL`
    yourself — the grid injects it.
-5. `gridctl_plug` to deploy. A runtime deploy is **ASYNC** — the first response
-   is `status: building`, not a live URL. Poll `gridctl_status` (or the returned
+5. `grid_plug` 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.
 6. Once live, add the `/api/webhook` URL as the Stripe webhook endpoint and copy
@@ -157,4 +157,4 @@ A membership site is a built + deployed runtime container, so it requires the
 **local edition** (Claude Desktop / Claude Code) or the CLI. The **hosted**
 edition (Claude Web / hosted MCP) is inline-only and can only publish static
 pages — it CANNOT build this app. On hosted, say so plainly and offer a static
-paywall-landing page (via `gridctl_drop`) instead, then stop the runtime path.
+paywall-landing page (via `grid_drop`) instead, then stop the runtime path.

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

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

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

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

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

@@ -3,12 +3,12 @@
 A single self-contained HTML personal / freelancer portfolio: a hero intro, an about section, a skills list, a projects grid, and a contact section.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `gridctl_drop` and works on every
+no external CDNs). It deploys instantly via `grid_drop` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in
 
-Fetch the template with `gridctl_fetch("template", "portfolio")`, then replace the
+Fetch the template with `grid_fetch("template", "portfolio")`, then replace the
 placeholders:
 
    - The person's name, role/title, and short intro.
@@ -23,7 +23,7 @@ stylesheets, fonts, or large embedded media.
 ## Deploy
 
 - Hosted MCP edition: call the drop tool with the HTML.
-- Local MCP / CLI edition: write the HTML to a file and run `gridctl plug`.
+- Local MCP / CLI edition: write the HTML to a file and run `grid plug`.
 
 It deploys as an inspiration and returns a live share URL right away. Re-deploy
 with the same entity id to update the same URL.

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

@@ -5,14 +5,14 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`gridctl_drop`** (or `gridctl_plug` with the inline
+To publish this page, use **`grid_drop`** (or `grid_plug` 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 `gridctl_drop`.
+runtime (async, local edition only); the fast path is `grid_drop`.
 
 The fillable HTML is the real template — fetch it with
-`gridctl_fetch("template", "portfolio")` and fill in the user's content.
+`grid_fetch("template", "portfolio")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

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

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

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

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

@@ -8,14 +8,14 @@ client-side.
 
 ## How it deploys
 
-To publish this page, use **`gridctl_drop`** (or `gridctl_plug` with the inline
+To publish this page, use **`grid_drop`** (or `grid_plug` 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 `gridctl_drop`.
+runtime (async, local edition only); the fast path is `grid_drop`.
 
 The fillable HTML is the real template — fetch it with
-`gridctl_fetch("template", "product-launch")` and fill in the user's content
+`grid_fetch("template", "product-launch")` and fill in the user's content
 (product name, hero copy, countdown target, features, offer, quotes). Keep it a
 single self-contained file: inline SVG / `data:` URIs only, no external scripts,
 stylesheets, fonts, or CDNs.

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

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

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

@@ -5,14 +5,14 @@ no `needs:`. State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`gridctl_drop`** (or `gridctl_plug` with the inline
+To publish this page, use **`grid_drop`** (or `grid_plug` 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 `gridctl_drop`.
+runtime (async, local edition only); the fast path is `grid_drop`.
 
 The fillable HTML is the real template — fetch it with
-`gridctl_fetch("template", "report")` and fill in the user's content.
+`grid_fetch("template", "report")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

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

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

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

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

@@ -3,12 +3,12 @@
 A single self-contained HTML SaaS marketing site (hero, features, pricing tiers, testimonials, FAQ, and a closing call to action). Richer than the landing-page template.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `gridctl_drop` and works on every
+no external CDNs). It deploys instantly via `grid_drop` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in
 
-Fetch the template with `gridctl_fetch("template", "saas-marketing")`, then replace the
+Fetch the template with `grid_fetch("template", "saas-marketing")`, then replace the
 placeholders:
 
    - The product name, tagline, and hero eyebrow/headline/subheadline.
@@ -24,7 +24,7 @@ stylesheets, fonts, or large embedded media.
 ## Deploy
 
 - Hosted MCP edition: call the drop tool with the HTML.
-- Local MCP / CLI edition: write the HTML to a file and run `gridctl plug`.
+- Local MCP / CLI edition: write the HTML to a file and run `grid plug`.
 
 It deploys as an inspiration and returns a live share URL right away. Re-deploy
 with the same entity id to update the same URL.

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

@@ -5,14 +5,14 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`gridctl_drop`** (or `gridctl_plug` with the inline
+To publish this page, use **`grid_drop`** (or `grid_plug` 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 `gridctl_drop`.
+runtime (async, local edition only); the fast path is `grid_drop`.
 
 The fillable HTML is the real template — fetch it with
-`gridctl_fetch("template", "saas-marketing")` and fill in the user's content.
+`grid_fetch("template", "saas-marketing")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

@@ -3,12 +3,12 @@
 A single self-contained HTML service status page: an overall banner, a component list with up / degraded / down pills, per-component uptime bars, and an incident history log. Status is baked into the page.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `gridctl_drop` and works on every
+no external CDNs). It deploys instantly via `grid_drop` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in
 
-Fetch the template with `gridctl_fetch("template", "status-page")`, then replace the
+Fetch the template with `grid_fetch("template", "status-page")`, then replace the
 placeholders:
 
    - The overall status banner text and state class (`ok` / `degraded` / `down`).
@@ -22,7 +22,7 @@ stylesheets, fonts, or large embedded media.
 ## Deploy
 
 - Hosted MCP edition: call the drop tool with the HTML.
-- Local MCP / CLI edition: write the HTML to a file and run `gridctl plug`.
+- Local MCP / CLI edition: write the HTML to a file and run `grid plug`.
 
 It deploys as an inspiration and returns a live share URL right away. Re-deploy
 with the same entity id to update the same URL.

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

@@ -5,14 +5,14 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`gridctl_drop`** (or `gridctl_plug` with the inline
+To publish this page, use **`grid_drop`** (or `grid_plug` 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 `gridctl_drop`.
+runtime (async, local edition only); the fast path is `grid_drop`.
 
 The fillable HTML is the real template — fetch it with
-`gridctl_fetch("template", "status-page")` and fill in the user's content.
+`grid_fetch("template", "status-page")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

@@ -18,7 +18,7 @@ The two share the same Stripe + Mongo wiring.
 The proven persistent shape is `app-with-data` (Next.js + Mongo). This blueprint
 extends it with Stripe subscriptions + the Billing Portal. Fetch that template
 for the Mongo lazy-client and App-Router API pattern:
-`gridctl_fetch("template", "app-with-data")`.
+`grid_fetch("template", "app-with-data")`.
 
 ## 1. File tree
 
@@ -89,7 +89,7 @@ client for plan/status — read this (kept current by the webhook).
     STRIPE_KEY: stripe-live-key
     STRIPE_WEBHOOK_SECRET: stripe-webhook-secret
   ```
-  Set the vault items ONCE with `gridctl_secrets` (or `grid secrets set`), then
+  Set the vault items ONCE with `grid_secrets` (or `grid secrets set`), then
   the deployer injects each as the named env var (`process.env.STRIPE_KEY`, etc.)
   at runtime and under `grid dev`. Do NOT commit keys; do NOT set them in
   `services.web.env` (that block is for non-secret config only). Read them lazily
@@ -158,22 +158,22 @@ known user — otherwise anyone could change anyone's plan.
 
 ## 5. Deploy steps
 
-1. `gridctl_login_status` → `gridctl_login` if needed. Respect the grid picker
+1. `grid_login_status` → `grid_login` if needed. Respect the grid picker
    (ask which grid if the user has more than one).
-2. `gridctl_init` an app `<name>` FIRST — it creates the entity, writes
+2. `grid_init` an app `<name>` FIRST — it creates the entity, writes
    `.cloudgrid/link.json`, and a `cloudgrid.yaml` with empty `services: {}`.
    `plug` needs a linked directory.
 3. Write the app under `services/web/` and set `cloudgrid.yaml` to the active
    shape: `name` + `services.web{type: nextjs, path: /}` + `needs:{database:true}`
    + the `vault:` block.
-4. Set the secrets: `gridctl_secrets` for `stripe-live-key`,
+4. Set the secrets: `grid_secrets` for `stripe-live-key`,
    `stripe-webhook-secret` (and `auth-provider-key` if you use an auth SDK) — the
    vault item keys the `vault:` block maps from. Non-secret config (Stripe
-   publishable key, price ids, auth publishable key) → `gridctl_env` /
+   publishable key, price ids, auth publishable key) → `grid_env` /
    `services.web.env`. Do NOT set `DATABASE_MONGODB_URL` yourself — the grid
    injects it.
-5. `gridctl_plug` to deploy. A runtime deploy is **ASYNC** — the first response
-   is `status: building`, not a live URL. Poll `gridctl_status` (or the returned
+5. `grid_plug` 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.
 6. Once live, add the `/api/webhook` URL as the Stripe webhook endpoint, copy
@@ -187,5 +187,5 @@ A subscription-management app is a built + deployed runtime container, so it
 requires the **local edition** (Claude Desktop / Claude Code) or the CLI. The
 **hosted** edition (Claude Web / hosted MCP) is inline-only and can only publish
 static pages — it CANNOT build this app. On hosted, say so plainly and offer a
-static pricing/plans page (via `gridctl_drop`) instead, then stop the runtime
+static pricing/plans page (via `grid_drop`) instead, then stop the runtime
 path.