@cloudgrid-io/mcp 0.20.31 → 0.20.33

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

@@ -173,7 +173,7 @@ known user — otherwise anyone could change anyone's plan.
    publishable key, price ids, auth publishable key) → `grid_set_env` /
    `services.web.env`. Do NOT set `DATABASE_MONGODB_URL` yourself — the grid
    injects it.
-5. `grid_deploy` to deploy. A runtime deploy is **ASYNC** — the first response
+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.
@@ -188,5 +188,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 `grid_deploy`) instead, then stop the runtime
+static pricing/plans page (via `grid_plug`) instead, then stop the runtime
 path.

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

@@ -67,7 +67,7 @@ vault:
 ## Deploy (async, local edition)
 
 `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`
+`services/web/`, set the vault secrets with `grid_set_secret`, `grid_plug`
 (async — poll `grid_status` to a live URL), then register the `/api/webhook`
 URL in Stripe, configure the Billing Portal, and re-plug. Re-plug the same entity
 to update the same URL.

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

@@ -3,7 +3,7 @@
 A single self-contained HTML launch waitlist / coming-soon page: a hero, an email capture form, and a social-proof counter.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `grid_deploy` and works on every
+no external CDNs). It deploys instantly via `grid_plug` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in

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

@@ -5,10 +5,10 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`grid_deploy`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
+To publish this page, use **`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 `grid_deploy`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_get_template("template", "waitlist")` and fill in the user's content.

package/src/corpus/templates/web-app/cloudgrid.yaml

@@ -16,7 +16,7 @@
 # THIS TEMPLATE (web-app): 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_deploy
+# runtime; the fast path is to deploy it as an INSPIRATION via grid_plug
 # (instant, and works on the hosted edition too).
 # ============================================================================
 

package/src/corpus/templates/web-app/index.md

@@ -5,10 +5,10 @@ no `needs:`. State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-To publish this page, use **`grid_deploy`** with the inline `html`: it deploys as an **inspiration** — instant, and works on the **hosted**
+To publish this page, use **`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 `grid_deploy`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_get_template("template", "web-app")` and fill in the user's content.

package/src/corpus/usage.md

@@ -45,7 +45,7 @@ npx skills add cloudgrid-io/skills
 ```
 claude mcp add cloudgrid -- npx -y @cloudgrid-io/mcp
 ```
-- **Find it under `/mcp`.** Exposes tools `grid_deploy`, `grid_login`, …
+- **Find it under `/mcp`.** Exposes tools `grid_plug`, `grid_login`, …
 - Invoke by describing the task; the model calls the tool.
 
 > Where did my install go? `/skills` (skills), `/plugin` (plugin), `/mcp` (MCP).

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

@@ -90,7 +90,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/ai-app.md

@@ -125,7 +125,7 @@ are wired in dev too — and send a test message before deploying. Don't require
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"` with a `poll_url` / entity, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/ai-knowledge-base.md

@@ -129,7 +129,7 @@ Gateway before deploying. Don't require it.
 
 ## 8. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -92,7 +92,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -90,7 +90,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -4,7 +4,7 @@ when: API documentation, API reference, endpoint docs, REST API docs, method/par
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the api-docs template, fill it with the user's endpoints, deploy it, and return the live share URL.
 ---
 

package/src/corpus/workflows/api-service.md

@@ -102,7 +102,7 @@ and hit the endpoints before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"` with a `poll_url` / entity, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/app-with-data.md

@@ -103,7 +103,7 @@ and sanity-check before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"` with a `poll_url` / entity, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — keep the user informed, never a

package/src/corpus/workflows/appointment-booking.md

@@ -128,7 +128,7 @@ claim reminders are live.
 
 ## 9. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/approval-workflow.md

@@ -111,7 +111,7 @@ before deploying. Don't require it.
 
 ## 8. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -102,7 +102,7 @@ This is a blueprint — the structure guide is the deliverable, not copy-paste c
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.
@@ -111,7 +111,7 @@ response is `status: "building"`, NOT a live URL yet.
 ## 8. Wire the Stripe webhook + return the live URL
 
 1. Register `<live-url>/api/webhook` as a webhook endpoint in the Stripe dashboard,
-   copy its `whsec_…` secret into the vault, and re-`grid_deploy` the SAME entity
+   copy its `whsec_…` secret into the vault, and re-`grid_plug` the SAME entity
    if you changed the `vault:` mapping (same URL).
 2. Give the user the live dashboard URL — that is the deliverable. To iterate,
    re-plug the SAME entity so it updates the same URL.

package/src/corpus/workflows/blog-cms.md

@@ -92,7 +92,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/booking-system.md

@@ -104,7 +104,7 @@ require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/calendar-scheduler.md

@@ -121,7 +121,7 @@ secrets) before deploying. Don't require it.
 
 ## 9. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/changelog.md

@@ -4,7 +4,7 @@ when: changelog, release notes, what's new, product updates page, version histor
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the changelog template, fill it with the user's release entries, deploy it, and return the live share URL.
 ---
 

package/src/corpus/workflows/company-website.md

@@ -4,7 +4,7 @@ when: company website, business site, corporate site, about-us site, small-busin
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the company-website template, fill it with the user's content across hero/about/services/team/contact, deploy it, and return the live share URL.
 ---
 

package/src/corpus/workflows/course-platform.md

@@ -112,7 +112,7 @@ rules:
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/crm.md

@@ -89,7 +89,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/dashboard.md

@@ -4,7 +4,7 @@ when: dashboard, metrics, KPIs, stats page, status board, charts, analytics view
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure, data is baked into the page. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure, data is baked into the page. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the dashboard template, fill it with the user's metrics and inline charts, deploy it, and return the live share URL.
 ---
 

package/src/corpus/workflows/directory.md

@@ -89,7 +89,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -4,8 +4,8 @@ when: multi-page documentation SITE, developer docs portal, knowledge base, help
 needs: none
 deploy: static build
 editions: local
-capabilities_note: a built, multi-page static documentation site (Astro Starlight) — sidebar nav, client-side search, and llms.txt / llms-full.txt generated on every build. No infrastructure (no needs:). Because it BUILDS from multiple files, it deploys async and needs the local edition; the hosted MCP cannot build it. Served at the entity root via grid_deploy.
-summary: Scaffold an Astro Starlight docs site from the docs-app template, fill in the content, build it, deploy the folder with grid_deploy (async → poll to a live URL), then ask the user what visibility they want. llms.txt / llms-full.txt are generated automatically.
+capabilities_note: a built, multi-page static documentation site (Astro Starlight) — sidebar nav, client-side search, and llms.txt / llms-full.txt generated on every build. No infrastructure (no needs:). Because it BUILDS from multiple files, it deploys async and needs the local edition; the hosted MCP cannot build it. Served at the entity root via grid_plug.
+summary: Scaffold an Astro Starlight docs site from the docs-app template, fill in the content, build it, deploy the folder with grid_plug (async → poll to a live URL), then ask the user what visibility they want. llms.txt / llms-full.txt are generated automatically.
 ---
 
 # Workflow: docs-app
@@ -98,7 +98,7 @@ looks for `services/site/` and fails with "Service directory not found". No
 
 ## 6. Build + deploy (async)
 
-Deploy the folder with `grid_deploy`. The platform (Cloud Build) runs `npm run
+Deploy the folder with `grid_plug`. The platform (Cloud Build) runs `npm run
 build` for you and serves the `dist/` output — you do NOT need to build first. A build deploy is **ASYNC**: the first response is
 `status: "building"` with a `poll_url` / entity, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.

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

@@ -4,7 +4,7 @@ when: single-page docs, a quick guide/manual/README-as-a-page, small knowledge b
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure, content baked into the page. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure, content baked into the page. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the docs-site template, fill it with the user's documentation, deploy it, and return the live share URL.
 ---
 

package/src/corpus/workflows/erp.md

@@ -112,7 +112,7 @@ vault env vars before deploying. Don't require it.
 
 ## 8. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/event-board.md

@@ -90,7 +90,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/expense-tracker.md

@@ -90,7 +90,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/feature-request-board.md

@@ -93,7 +93,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -91,7 +91,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/forum.md

@@ -116,7 +116,7 @@ Mention that the user can `grid dev` to run locally against the injected Mongo
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/hr-portal.md

@@ -103,7 +103,7 @@ vault env vars before deploying. Don't require it.
 
 ## 8. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/internal-tools-portal.md

@@ -113,7 +113,7 @@ vault env vars before deploying. Don't require it.
 
 ## 8. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/inventory.md

@@ -89,7 +89,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/invoice.md

@@ -89,7 +89,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/job-board.md

@@ -89,7 +89,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/kanban.md

@@ -90,7 +90,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -4,7 +4,7 @@ when: landing page, marketing page, product page, hero page, coming-soon, waitli
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the landing-page template, fill it with the user's content, deploy it, and return the live share URL.
 ---
 

package/src/corpus/workflows/lms.md

@@ -100,7 +100,7 @@ needs:
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/marketplace.md

@@ -110,7 +110,7 @@ secrets before deploying. Don't require it.
 
 ## 8. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -114,7 +114,7 @@ and vault secrets before deploying. Don't require it.
 
 ## 8. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -92,7 +92,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -96,7 +96,7 @@ This is a blueprint — the structure guide is the deliverable, not copy-paste c
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.
@@ -105,7 +105,7 @@ response is `status: "building"`, NOT a live URL yet.
 ## 8. Wire the Stripe webhook + return the live URL
 
 1. Register `<live-url>/api/webhook` as a webhook endpoint in the Stripe
-   dashboard, copy its `whsec_…` secret into the vault, and re-`grid_deploy` the
+   dashboard, copy its `whsec_…` secret into the vault, and re-`grid_plug` the
    SAME entity if you changed the `vault:` mapping (same URL).
 2. Give the user the live store URL — that is the deliverable. To iterate, re-plug
    the SAME entity so it updates the same URL.

package/src/corpus/workflows/portfolio.md

@@ -4,7 +4,7 @@ when: portfolio, personal site, freelancer site, my work, showcase, resume site,
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the portfolio template, fill it with the user's projects and bio, deploy it, and return the live share URL.
 ---
 

package/src/corpus/workflows/presentation.md

@@ -4,7 +4,7 @@ when: slides, deck, pitch, presentation, slideshow.
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the deck template, fill it with the user's content, deploy it, and return the live share URL.
 ---
 

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

@@ -93,7 +93,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

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

@@ -4,7 +4,7 @@ when: product launch page, launch announcement, new product page, we just launch
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the product-launch template, fill it with the user's product/launch content, deploy it, and return the live share URL.
 ---
 

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

@@ -94,7 +94,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/property-listings.md

@@ -89,7 +89,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/quiz-platform.md

@@ -93,7 +93,7 @@ before deploying. Don't require it.
 
 ## 7. Deploy (async)
 
-Deploy the folder with `grid_deploy`. A **runtime deploy is ASYNC**: the first
+Deploy the folder with `grid_plug`. A **runtime deploy is ASYNC**: the first
 response is `status: "building"`, NOT a live URL yet.
 - Poll `grid_status` (or the returned poll_url) until the entity is live.
 - Surface a liveness signal while it builds — never a bare silent wait.

package/src/corpus/workflows/report.md

@@ -4,7 +4,7 @@ when: report, one-pager, summary, brief, whitepaper, case study, formatted docum
 needs: none
 deploy: inspiration
 editions: all
-capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_deploy.
+capabilities_note: static — no infrastructure. Publishes as an inspiration (instant, works on hosted) via grid_plug.
 summary: Fetch the report template, fill it with the user's content, deploy it, and return the live share URL.
 ---