@cloudgrid-io/mcp 0.16.1 → 0.17.0

package/README.md

@@ -61,49 +61,49 @@ It speaks MCP over stdio. Point any MCP client at the `cloudgrid-mcp` command.
 
 | Tool | Wraps | Notes |
 |---|---|---|
-| `gridctl_plug` | `POST /api/v2/plug` | The unified create/re-plug verb: create a new entity, or update the SAME entity in place with `target_entity_id` (same URL). Source via local `path` (local edition) or inline `artifact_files` (both). |
-| `gridctl_drop` | `POST /api/v2/plug` | Artifact drop. Anonymous, or owned if signed in. Re-drops in a session update the same drop in place; anonymous drops return an `entity_id` + `owner_token` re-plug/claim handle. |
-| `gridctl_claim` | `POST /api/v2/entities/:id/pickup` | Claim an anonymous drop into the signed-in account (the claim token IS the drop's owner token). Direct API. |
-| `gridctl_fork` | `POST /api/v2/runtimes/:id/fork` | Start a new entity from an existing runtime (lineage recorded). Needs sign-in. |
-| `gridctl_download` | `GET /api/v2/runtimes/:id/source` | Signed 15-minute source-bundle URLs. Needs sign-in. |
-| `gridctl_login` | `GET /auth/login` | Start a CLI-free sign-in; returns a URL to open. Direct API. |
-| `gridctl_login_status` | `GET /auth/status` | Finish the sign-in; saves the token to the shared CLI credentials. |
-| `gridctl_visibility` | `PATCH /api/v2/inspirations/<id>` | Change who can see a drop (private, space, authenticated, org, link). Needs sign-in. Direct API; also in the web edition. |
-
-`gridctl_drop`, `gridctl_claim`, `gridctl_visibility`, and the two
-`gridctl_login` tools do not wrap the CLI -- they call the API directly, so they
-also work in the web edition where no CLI exists. `gridctl_login` writes the same
+| `grid_plug` | `POST /api/v2/plug` | The unified create/re-plug verb: create a new entity, or update the SAME entity in place with `target_entity_id` (same URL). Source via local `path` (local edition) or inline `artifact_files` (both). |
+| `grid_drop` | `POST /api/v2/plug` | Artifact drop. Anonymous, or owned if signed in. Re-drops in a session update the same drop in place; anonymous drops return an `entity_id` + `owner_token` re-plug/claim handle. |
+| `grid_claim` | `POST /api/v2/entities/:id/pickup` | Claim an anonymous drop into the signed-in account (the claim token IS the drop's owner token). Direct API. |
+| `grid_fork` | `POST /api/v2/runtimes/:id/fork` | Start a new entity from an existing runtime (lineage recorded). Needs sign-in. |
+| `grid_download` | `GET /api/v2/runtimes/:id/source` | Signed 15-minute source-bundle URLs. Needs sign-in. |
+| `grid_login` | `GET /auth/login` | Start a CLI-free sign-in; returns a URL to open. Direct API. |
+| `grid_login_status` | `GET /auth/status` | Finish the sign-in; saves the token to the shared CLI credentials. |
+| `grid_visibility` | `PATCH /api/v2/inspirations/<id>` | Change who can see a drop (private, space, authenticated, org, link). Needs sign-in. Direct API; also in the web edition. |
+
+`grid_drop`, `grid_claim`, `grid_visibility`, and the two
+`grid_login` tools do not wrap the CLI -- they call the API directly, so they
+also work in the web edition where no CLI exists. `grid_login` writes the same
 `~/.cloudgrid/credentials` the CLI uses, so the two share one identity.
 
 ### CLI-wrapping tools (local edition only)
 
 | Tool | Wraps | Notes |
 |---|---|---|
-| `gridctl_init` | `cloudgrid init` | Register an app or agent; optionally seed a web service. |
-| `gridctl_logs` | `cloudgrid logs` | Snapshot of recent logs. Does not stream. Read-only. |
-| `gridctl_share` | `cloudgrid visibility set` | Set visibility, default link. |
-| `gridctl_feedback` | `cloudgrid feedback list` | Read the org feedback feed. Read-only. |
-| `gridctl_whoami` | `cloudgrid whoami` | Show the signed-in user and active org. Read-only. |
-| `gridctl_use` | `cloudgrid use` | Switch the active org. |
-| `gridctl_logout` | `cloudgrid logout` | Sign out and clear local credentials. Destructive. |
-| `gridctl_status` | `cloudgrid status` | Org dashboard or entity detail. Read-only. |
-| `gridctl_info` | `cloudgrid info` | Entity metadata. Read-only. |
-| `gridctl_get` | `cloudgrid get grids\|entities\|spaces` | List grids, entities, or spaces. Read-only. |
-| `gridctl_describe_grid` | `cloudgrid describe grid <slug>` | Grid detail. Read-only. |
-| `gridctl_pickup` | `cloudgrid pickup <name>` | Download an entity's source and bind the folder. |
-| `gridctl_rename` | `cloudgrid rename` | Rename an entity's display name. |
-| `gridctl_unplug` | `cloudgrid unplug` | Take an entity off the grid. Destructive; requires confirm. |
-| `gridctl_delete` | `cloudgrid delete entity` | Archive an inspiration. Destructive; requires confirm. |
-| `gridctl_rollback` | `cloudgrid rollback` | Rollback to a previous version. |
-| `gridctl_versions` | `cloudgrid versions` | List published versions. Read-only. |
-| `gridctl_env` | `cloudgrid env` | Get, set, or list environment variables. |
-| `gridctl_secrets` | `cloudgrid secrets` | Set or list secret names. Never returns secret values. |
-| `gridctl_scaffold` | `cloudgrid scaffold` | Generate starter files. |
-| `gridctl_doctor` | `cloudgrid doctor` | Run local diagnostics. Read-only. |
-| `gridctl_open` | `cloudgrid open --print` | Return the public URL. Does not open a browser. Read-only. |
-
-`gridctl_share` and `gridctl_visibility` overlap on purpose: `gridctl_share`
-wraps the CLI and defaults to `link`; `gridctl_visibility` is direct API, takes an
+| `grid_init` | `cloudgrid init` | Register an app or agent; optionally seed a web service. |
+| `grid_logs` | `cloudgrid logs` | Snapshot of recent logs. Does not stream. Read-only. |
+| `grid_share` | `cloudgrid visibility set` | Set visibility, default link. |
+| `grid_feedback` | `cloudgrid feedback list` | Read the org feedback feed. Read-only. |
+| `grid_whoami` | `cloudgrid whoami` | Show the signed-in user and active org. Read-only. |
+| `grid_use` | `cloudgrid use` | Switch the active org. |
+| `grid_logout` | `cloudgrid logout` | Sign out and clear local credentials. Destructive. |
+| `grid_status` | `cloudgrid status` | Org dashboard or entity detail. Read-only. |
+| `grid_info` | `cloudgrid info` | Entity metadata. Read-only. |
+| `grid_get` | `cloudgrid get grids\|entities\|spaces` | List grids, entities, or spaces. Read-only. |
+| `grid_describe_grid` | `cloudgrid describe grid <slug>` | Grid detail. Read-only. |
+| `grid_pickup` | `cloudgrid pickup <name>` | Download an entity's source and bind the folder. |
+| `grid_rename` | `cloudgrid rename` | Rename an entity's display name. |
+| `grid_unplug` | `cloudgrid unplug` | Take an entity off the grid. Destructive; requires confirm. |
+| `grid_delete` | `cloudgrid delete entity` | Archive an inspiration. Destructive; requires confirm. |
+| `grid_rollback` | `cloudgrid rollback` | Rollback to a previous version. |
+| `grid_versions` | `cloudgrid versions` | List published versions. Read-only. |
+| `grid_env` | `cloudgrid env` | Get, set, or list environment variables. |
+| `grid_secrets` | `cloudgrid secrets` | Set or list secret names. Never returns secret values. |
+| `grid_scaffold` | `cloudgrid scaffold` | Generate starter files. |
+| `grid_doctor` | `cloudgrid doctor` | Run local diagnostics. Read-only. |
+| `grid_open` | `cloudgrid open --print` | Return the public URL. Does not open a browser. Read-only. |
+
+`grid_share` and `grid_visibility` overlap on purpose: `grid_share`
+wraps the CLI and defaults to `link`; `grid_visibility` is direct API, takes an
 explicit scope, and defaults its target to the session's last drop -- it is the one
 the web edition gets.
 
@@ -113,7 +113,7 @@ All tools carry MCP annotations (`readOnlyHint`, `destructiveHint`,
 ## Test
 
 A smoke test spawns the server with a real MCP client, lists the tools, and calls
-the read-only `gridctl_feedback` tool end to end:
+the read-only `grid_feedback` tool end to end:
 
 ```
 cd mcp-server
@@ -127,5 +127,5 @@ It needs a logged-in CLI on `$PATH`.
 
 - Shells out with `execFile` and an argument array, so there is no shell and no
   injection surface.
-- `gridctl_logs` never uses `--follow`; a streaming call would never return.
+- `grid_logs` never uses `--follow`; a streaming call would never return.
 - Stateless. Each call is one CLI invocation.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cloudgrid-io/mcp",
-  "version": "0.16.1",
+  "version": "0.17.0",
   "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.",
   "type": "module",
   "bin": {

package/src/corpus/capability-map.md

@@ -4,14 +4,14 @@ 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:
 
-- **static → inspiration** (instant, any client / any edition) via `gridctl_drop`.
+- **static → inspiration** (instant, any client / any edition) via `grid_drop`.
 - **anything needing `needs:` → runtime** (async build, **local edition** only)
-  via `gridctl_plug` on a linked folder.
+  via `grid_plug` on a linked folder.
 
-Fetch this doc any time with `gridctl_fetch("doc", "capability-map")`. For the full
+Fetch this doc any time with `grid_fetch("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:
-`gridctl_fetch("doc", "cloudgrid-yaml")`.
+`grid_fetch("doc", "cloudgrid-yaml")`.
 
 ## The 59 templates
 
@@ -137,7 +137,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
-`gridctl_fetch("doc", "cloudgrid-yaml")`.
+`grid_fetch("doc", "cloudgrid-yaml")`.
 
 | `needs:` key | Provides | Injected env var(s) | Status |
 |---|---|---|---|
@@ -173,9 +173,9 @@ engine hint. Cron is NOT a need — it is a **service type** (`type: cron` with
    `api-service`); talks to an LLM → `ai: true` + `database` (`ai-app`); scheduled
    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. Static (`needs: none`) → publish as an inspiration with `gridctl_drop`
+3. Static (`needs: none`) → publish as an inspiration with `grid_drop`
    (instant, any edition). Anything with a `needs:` → runtime, local edition,
-   `gridctl_plug` a linked folder, then poll to a live URL.
+   `grid_plug` 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 `gridctl_fetch("doc", "cloudgrid-yaml")`.
+> Fetch this doc any time with `grid_fetch("doc", "cloudgrid-yaml")`.
 > For matching an intent to a template, see the companion
-> `gridctl_fetch("doc", "capability-map")`.
+> `grid_fetch("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.
 ### Static site → deploys as an inspiration (instant)
 
 A single-file / static bundle. No `needs:`. Publishes instantly via
-`gridctl_drop`, works on any edition (hosted or local).
+`grid_drop`, works on any edition (hosted or local).
 
 ```yaml
 name: landing-page
@@ -540,7 +540,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.
-- **Static single-file pages deploy as inspirations** via `gridctl_drop` — instant,
+- **Static single-file pages deploy as inspirations** via `grid_drop` — instant,
   synchronous, works on the hosted edition and any client.
 - **A `cloudgrid.yaml` with `services:` makes it a runtime** — async build,
   **local edition only** (Claude Desktop/Code or the CLI, not hosted). `plug`
@@ -565,5 +565,5 @@ needs:
 ---
 
 *This doc is the agent-facing distribution of the platform's canonical
-`cloudgrid-yaml-reference.md`. See also `gridctl_fetch("doc", "capability-map")`
+`cloudgrid-yaml-reference.md`. See also `grid_fetch("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 drop later), and `claim_url` (sign in
 before it expires to keep it). This is what the `cloudgrid-drop` skill and the
-`gridctl_drop` MCP tool do for you. It is anonymous and serves inspirations
+`grid_drop` MCP tool 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/install.md

@@ -140,7 +140,7 @@ https://github.com/cloudgrid-io/mcp/releases/latest/download/cloudgrid.mcpb
 
 The bundle carries the full local toolset (including the `cloudgrid` CLI), so deploy
 and secrets tools work without a separate install. Sign in from chat with the
-`gridctl_login` tool on first use.
+`grid_login` tool on first use.
 
 ## For agents
 

package/src/corpus/rules/publish-fallbacks.md

@@ -14,7 +14,7 @@ loops forever.
 
 This is a known platform issue, not a mistake in your request. Do not retry with
 different flag or path permutations — they will all fail the same way. If a
-terminal is available, deploy from the CLI instead (`gridctl plug <path>` or
+terminal is available, deploy from the CLI instead (`grid plug <path>` or
 `cloudgrid plug <path>`). If no terminal is available, stop and tell the user
 this is a known issue and needs the CLI.
 

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 `gridctl_claim` tool does this for you, and remembers the entity id +
+- The MCP `grid_claim` 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-drop.md

@@ -78,7 +78,7 @@ A signed-in drop returns HTTP 202 with `entity_id`, `url`, `slug` + `grid` and n
 not compose it. The org is taken from the `X-CloudGrid-Org` header — there is no
 `org_slug` form field. If the user is a member of several orgs and the header is
 missing, the API replies with the list of orgs to choose from. The MCP
-`gridctl_drop` tool does this automatically when credentials are present.
+`grid_drop` tool does this automatically when credentials are present.
 
 ## Re-plug: update the same URL in place
 
@@ -120,7 +120,7 @@ Rules that matter:
 - An anonymous edit without a valid `owner_token` returns **401**.
 - Anonymous edits count against the same daily anonymous cap as creates.
 - Only re-plug when the user is iterating on an existing artifact. If they want a
-  separate new link, omit `target_entity_id` (the MCP `gridctl_drop` tool's
+  separate new link, omit `target_entity_id` (the MCP `grid_drop` tool's
   `fresh` flag does the same: it forces a new entity instead of updating).
 
 ## After the drop

package/src/corpus/skill-login.md

@@ -81,6 +81,6 @@ made an anonymous drop earlier, this is the moment to offer to claim it.
 
 - Enterprise single sign-on is not supported in this flow yet; those users sign in
   through the Console for now.
-- The MCP server exposes the same flow as `gridctl_login` and
-  `gridctl_login_status`, which handle the polling and the credentials write for
+- The MCP server exposes the same flow as `grid_login` and
+  `grid_login_status`, which handle the polling and the credentials write for
   you.

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 (`gridctl_start`, `gridctl_fetch`, and the
+   hook, and the CloudGrid MCP server (`grid_start`, `grid_fetch`, 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 `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:{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:** `gridctl_fetch("template", "ai-knowledge-base")` → read
+- **Structure guide:** `grid_fetch("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 `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", "api-docs")`, then replace the
+Fetch the template with `grid_fetch("template", "api-docs")`, then replace the
 placeholders:
 
    - The API name, base URL, and auth note.
@@ -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/api-docs/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", "api-docs")` and fill in the user's content.
+`grid_fetch("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:
-`gridctl_fetch("template", "app-with-data")`.
+`grid_fetch("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 `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.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
@@ -161,21 +161,21 @@ you want client accounts.
 
 ## 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. (Leave the `reminders` cron service COMMENTED — see §7.)
-4. Set the secrets: `gridctl_secrets` for `auth-provider-key` (and, if taking
+4. Set the secrets: `grid_secrets` 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)
-   → `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. If taking deposits, once live add the `/api/webhook` URL as the Stripe webhook
@@ -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 `gridctl_drop`) instead, then stop the runtime
+static "book us" landing page (via `grid_drop`) 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:**
-- `gridctl_fetch("template", "appointment-booking")` — 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", "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).
 
 **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 `gridctl_secrets`, and the deployer injects them at runtime. Read lazily;
+   with `grid_secrets`, 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)
 
-`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). If taking deposits, register the
+`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). 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:
-`gridctl_fetch("template", "app-with-data")`, then adapt it to the collections
+`grid_fetch("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. `gridctl_init` an app `<name>` — creates the entity, `.cloudgrid/link.json`,
+1. `grid_init` 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
 
-- `gridctl_fetch("template", "approval-workflow")` → this blueprint:
+- `grid_fetch("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.
-- `gridctl_fetch("template", "app-with-data")` → the concrete Next.js + Mongo
+- `grid_fetch("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 `gridctl_fetch("template", "billing-dashboard")` and read **`AGENTS.md`** — it
+Fetch `grid_fetch("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 `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/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:** `gridctl_fetch("template", "calendar-scheduler")` → read
+- **Structure guide:** `grid_fetch("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 `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", "changelog")`, then replace the
+Fetch the template with `grid_fetch("template", "changelog")`, then replace the
 placeholders:
 
    - The product name and page intro.
@@ -21,7 +21,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/changelog/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", "changelog")` and fill in the user's content.
+`grid_fetch("template", "changelog")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)
 

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

@@ -10,14 +10,14 @@ wire it to your own email service or form endpoint if you want real submissions.
 
 ## 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", "company-website")` and fill in the user's content.
+`grid_fetch("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 gridctl_drop (instant,
+# The fast path deploys the page as an INSPIRATION via grid_drop (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,14 +6,14 @@ Inline CSS + inline JS only (no external scripts, stylesheets, fonts, or CDNs).
 
 ## 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", "company-website")` and fill in the user's content.
+`grid_fetch("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
-`gridctl_fetch("template", "course-platform")`.
+`grid_fetch("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 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/dashboard/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", "dashboard")` and fill in the user's content.
+`grid_fetch("template", "dashboard")` and fill in the user's content.
 
 ## cloudgrid.yaml (reference only)