@cloudgrid-io/mcp 0.17.0 → 0.19.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cloudgrid-io/mcp",
-  "version": "0.17.0",
+  "version": "0.19.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,9 +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 `grid_drop`.
-- **anything needing `needs:` → runtime** (async build, **local edition** only)
-  via `grid_plug` on a linked folder.
+> **One deploy verb: `grid_plug`.** Classify the artifact to pick the shape —
+> ONE self-contained HTML page (CSS+JS inline, images/fonts as data: URIs) →
+> **inspiration**; separate files/folders/assets or any `needs:` → **runtime app**.
+
+- **single self-contained HTML page → inspiration** (instant, any client / any
+  edition) via `grid_plug` with the inline `html` param.
+- **separate files/folders/assets, or anything needing `needs:` → runtime app**
+  (async build, **local edition** only) via `grid_plug` on a linked folder.
 
 Fetch this doc any time with `grid_fetch("doc", "capability-map")`. For the full
 cloudgrid.yaml schema (every field, the `needs:` injection table, the
@@ -173,9 +178,10 @@ 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 `grid_drop`
-   (instant, any edition). Anything with a `needs:` → runtime, local edition,
-   `grid_plug` a linked folder, then poll to a live URL.
+3. One self-contained HTML page (`needs: none`, assets inlined) → publish as an
+   inspiration with `grid_plug` and the inline `html` param (instant, any
+   edition). Separate files/folders/assets, or anything with a `needs:` →
+   runtime, local edition, `grid_plug` a linked folder, then poll to a live URL.
 
 ## FAQ
 

package/src/corpus/cloudgrid-yaml.md

@@ -25,10 +25,11 @@ new yaml with it.
 
 These are the shapes verified against live deploys. Copy one and adapt it.
 
-### Static site → deploys as an inspiration (instant)
+### Single HTML page → deploys as an inspiration (instant)
 
-A single-file / static bundle. No `needs:`. Publishes instantly via
-`grid_drop`, works on any edition (hosted or local).
+One self-contained HTML page (CSS+JS inline, images/fonts as data: URIs). No
+`needs:`. Publishes instantly via `grid_plug` with the inline `html` param,
+works on any edition (hosted or local).
 
 ```yaml
 name: landing-page
@@ -540,8 +541,9 @@ 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 `grid_drop` — instant,
-  synchronous, works on the hosted edition and any client.
+- **A single self-contained HTML page deploys as an inspiration** via `grid_plug`
+  with the inline `html` param — instant, synchronous, works on the hosted edition
+  and any client.
 - **A `cloudgrid.yaml` with `services:` makes it a runtime** — async build,
   **local edition only** (Claude Desktop/Code or the CLI, not hosted). `plug`
   returns `status: building`; poll status until live, then use the returned live

package/src/corpus/cookbook.md

@@ -72,10 +72,10 @@ 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
-`grid_drop` MCP tool do for you. It is anonymous and serves inspirations
-only; a full app needs the signed-in `plug` flow above.
+`owner_token` (keep both to update the page later), and `claim_url` (sign in
+before it expires to keep it). This is what the `cloudgrid:plug` skill and the
+`grid_plug` MCP tool (inline `html` param) do for you. It is anonymous and serves
+inspirations only; a full app needs the signed-in `plug` flow above.
 
 ## Update your drop in place
 

package/src/corpus/install-for-agents.md

@@ -31,11 +31,10 @@ Do not attempt to log in for them. Do not invent an auth flow.
 The skills live in this repo, one directory per skill, each with a `SKILL.md`.
 Load the `SKILL.md` for the action the user wants:
 
-- `skills/drop/SKILL.md` — share an artifact, get a URL (no login needed)
 - `skills/login/SKILL.md` — sign in, with or without the CLI
 - `skills/claim/SKILL.md` — claim an anonymous drop into the account
 - `skills/init/SKILL.md` — scaffold a new app or agent
-- `skills/plug/SKILL.md` — deploy a directory or URL
+- `skills/plug/SKILL.md` — share a single HTML page or deploy a directory/URL, get a URL
 - `skills/logs/SKILL.md` — tail logs
 - `skills/share/SKILL.md` — make an entity shareable
 - `skills/feedback/SKILL.md` — read the feedback feed

package/src/corpus/skill-plug.md

@@ -1,18 +1,81 @@
 ---
-version: 0.2.0
+version: 0.3.0
 name: plug
 description: |
-  Deploy a directory or URL to CloudGrid. Use when the user wants to ship, deploy,
-  publish, or go live with the current project, or turn a URL into a hosted entity.
-  Live in about 30 seconds. Wraps cloudgrid plug.
+  Deploy or share a creation on CloudGrid and get a public URL. Use when the user
+  wants to ship, deploy, publish, share, send a friend a link, or go live — a
+  single HTML page or a full app. One self-contained HTML page publishes instantly
+  as an inspiration (any edition, no login needed); a multi-file app deploys from a
+  directory or URL. Wraps cloudgrid plug.
 argument-hint: "[path-or-url]"
 allowed-tools: Bash
 ---
 
 # CloudGrid Plug
 
-Build and deploy a directory, a path, or a URL. Prints the live URL when it is
-done. This is the center of the build-and-ship loop. Wraps `cloudgrid plug`.
+Deploy or share a creation and get a public URL. This is the one deploy/share verb
+— a single HTML page or a full app — and the center of the build-and-ship loop.
+
+## Classify the artifact first
+
+- **ONE self-contained HTML page** (a single file — CSS+JS inline, images/fonts as
+  data: URIs; the normal hosted output) → an **inspiration**: instant, works on
+  **any edition**, no login required. See "Share a single HTML page" below.
+- **Anything more** — separate files/folders, a real `assets/` dir, separate
+  `.css`/`.js`, multiple pages, a SPA build — **or** any data/server/LLM/cron need
+  → a **runtime app**: `cloudgrid plug` on a linked folder, **local edition only**,
+  async build. See "Deploy an app" below.
+
+## Share a single HTML page (the fast path)
+
+No account and no CLI needed — that is the point: anyone can publish a page. Write
+the page to a single self-contained HTML file (a full document starting with
+`<!doctype html>` or `<html>`; wrap a fragment in a minimal document). HTML is
+capped at 2 MB for anonymous publishes. Then POST it to the unified plug endpoint:
+
+```
+curl -sS -X POST https://api.cloudgrid.io/api/v2/plug \
+  -F "artifact=@/path/to/index.html;type=text/html"
+```
+
+The response is JSON (HTTP 201 anonymous). Read these fields:
+
+- `url` — the live link, composed by the server. Use it verbatim; never compose a
+  URL from the slug yourself.
+- `entity_id` — the durable handle for updating this page later (see re-plug below).
+- `owner_token` — a JWT proving you made this page. It authorizes an anonymous
+  re-plug and doubles as the claim token; its lifetime matches the expiry (default
+  7 days). Persist it with `entity_id` and `url`.
+- `claim_url` / `claim_message` — the link + nudge to sign in and keep it past expiry.
+
+Signed in, publish into your own grid instead (owned, no claim needed):
+
+```
+JWT=$(jq -r .jwt ~/.cloudgrid/credentials 2>/dev/null)
+ORG=$(grep -E '^\s*active_org_slug:' ~/.cloudgrid/config.yaml | awk '{print $2}')
+curl -sS -X POST https://api.cloudgrid.io/api/v2/plug \
+  -H "Authorization: Bearer $JWT" -H "X-CloudGrid-Org: $ORG" \
+  -F "artifact=@/path/to/index.html;type=text/html"
+```
+
+The MCP `grid_plug` tool does all of this for you: pass the page as its inline
+`html` param (it materializes one `index.html` and handles anon/claim/re-plug).
+
+### Re-plug: update the same URL in place
+
+`/api/v2/plug` is a unified create-or-update endpoint. The switch is the
+`target_entity_id` form field: absent → create (new URL); present → update the
+SAME entity (same slug, same URL, new content). Anonymously, prove ownership with
+the `owner_token`; signed in, use your normal auth headers. Every anonymous edit
+REFRESHES the `owner_token` (store the newest) and resets the expiry. Editing an
+archived/expired page returns **409 `EDIT_REJECTED`** — it never silently creates.
+
+Print the `url` on its own line so it can be copied in one go. A single page is an
+**inspiration only** — a full app needs the deploy flow below.
+
+## Deploy an app
+
+Wraps `cloudgrid plug`. Prints the live URL when it is done.
 
 ## Step 0 — Bootstrap
 

package/src/corpus/skills-readme.md

@@ -37,9 +37,9 @@ behalf: scaffold, deploy, tail logs, share, read feedback. Everything here is fr
    CLI-wrapping tools). The MCP auto-starts when the plugin is enabled — no
    separate `claude mcp add` needed.
 
-   The skills show under `/plugin` and `/skills` as `cloudgrid:drop`,
-   `cloudgrid:login`, … — or just say what you want ("drop this HTML to
-   CloudGrid") and the right one triggers.
+   The skills show under `/plugin` and `/skills` as `cloudgrid:plug`,
+   `cloudgrid:login`, … — or just say what you want ("share this HTML page as a
+   link") and the right one triggers.
 
    Or install with the `gh skill` extension:
 
@@ -48,7 +48,7 @@ behalf: scaffold, deploy, tail logs, share, read feedback. Everything here is fr
    ```
 
    Other agents (Cursor, Cline, Gemini CLI): `npx skills add cloudgrid-io/skills`.
-   They install as `drop`, `plug`, … — the CloudGrid brand comes from the plugin
+   They install as `plug`, `login`, … — the CloudGrid brand comes from the plugin
    namespace, which those agents don't have.
 
    Claude Desktop, claude.ai, ChatGPT, and every route in one place: [USAGE.md](USAGE.md).
@@ -56,21 +56,21 @@ behalf: scaffold, deploy, tail logs, share, read feedback. Everything here is fr
 ## Share something in one step, no login
 
 ```
-/cloudgrid:drop index.html
+/cloudgrid:plug index.html
 ```
 
-`cloudgrid:drop` publishes an HTML page or file and hands back a public URL. No
-account, no CLI. The link lasts 7 days, and you can sign in later to keep it.
+`cloudgrid:plug` publishes a single HTML page (or deploys a full app) and hands
+back a public URL. For a single page: no account, no CLI — the link lasts 7 days,
+and you can sign in later to keep it.
 
 ## Skills
 
 | Skill | Invoke | What it does |
 |---|---|---|
-| `drop` | `/cloudgrid:drop` | Share an HTML page or file, get a public URL. Login optional. |
 | `login` | `/cloudgrid:login` | Sign in to CloudGrid, with or without the CLI. |
 | `claim` | `/cloudgrid:claim` | Claim an anonymous drop into your account after signing in. |
 | `init` | `/cloudgrid:init` | Scaffold a new app or agent. |
-| `plug` | `/cloudgrid:plug` | Deploy a directory or URL. Live in about 30 seconds. |
+| `plug` | `/cloudgrid:plug` | Share a single HTML page (login optional) or deploy a directory/URL. Get a public URL. |
 | `logs` | `/cloudgrid:logs` | Tail logs for an entity. |
 | `share` | `/cloudgrid:share` | Make an entity shareable and print its URL. |
 | `feedback` | `/cloudgrid:feedback` | Read the feedback feed. |

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

@@ -3,7 +3,7 @@
 A single self-contained HTML API reference: a sidebar endpoint list, per-endpoint method badges (GET / POST / PUT / DELETE), a params table, and request / response examples in code blocks.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `grid_drop` 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/api-docs/index.md

@@ -5,11 +5,10 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-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**
+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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "api-docs")` and fill in the user's content.

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

@@ -188,7 +188,7 @@ An appointment-booking app is a built + deployed runtime container, so it
 requires the **local edition** (Claude Desktop / Claude Code) or the CLI. The
 **hosted** edition (Claude Web / hosted MCP) is inline-only and can only publish
 static pages — it CANNOT build this app. On hosted, say so plainly and offer a
-static "book us" landing page (via `grid_drop`) instead, then stop the runtime
+static "book us" landing page (via `grid_plug`) instead, then stop the runtime
 path.
 
 ## 7. Reminders (cron — PENDING platform issue #1543)

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

@@ -3,7 +3,7 @@
 A single self-contained HTML changelog / release-notes page: reverse-chronological versioned entries, each with a date and tagged change items (added / fixed / changed / removed).
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `grid_drop` 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/changelog/index.md

@@ -5,11 +5,10 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-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**
+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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "changelog")` and fill in the user's content.

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

@@ -10,11 +10,10 @@ wire it to your own email service or form endpoint if you want real submissions.
 
 ## How it deploys
 
-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**
+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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "company-website")` and fill in the user's content.

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

@@ -11,7 +11,7 @@
 # ignored by the parser, so the file deploys to exactly the active fields.
 #
 # company-website is a STATIC template (type: static, path: /) with no needs.
-# The fast path deploys the page as an INSPIRATION via grid_drop (instant,
+# The fast path deploys the page as an INSPIRATION via grid_plug (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,11 +6,10 @@ Inline CSS + inline JS only (no external scripts, stylesheets, fonts, or CDNs).
 
 ## How it deploys
 
-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**
+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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "company-website")` and fill in the user's content.

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

@@ -16,7 +16,7 @@
 # THIS TEMPLATE (dashboard): a single self-contained static page. The active fields
 # are exactly name + services.web{type: static, path: /}; there are no needs.
 # This cloudgrid.yaml is the reference for plugging it as an OWNED static
-# runtime; the fast path is to deploy it as an INSPIRATION via grid_drop
+# 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/dashboard/index.md

@@ -5,11 +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_drop`** (or `grid_plug` 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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "dashboard")` and fill in the user's content.

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

@@ -16,7 +16,7 @@
 # THIS TEMPLATE (deck): a single self-contained static page. The active fields
 # are exactly name + services.web{type: static, path: /}; there are no needs.
 # This cloudgrid.yaml is the reference for plugging it as an OWNED static
-# runtime; the fast path is to deploy it as an INSPIRATION via grid_drop
+# 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/deck/index.md

@@ -5,11 +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_drop`** (or `grid_plug` 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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "deck")` and fill in the user's content.

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

@@ -3,7 +3,7 @@
 A single self-contained HTML documentation site: a sidebar nav, a scrolling content column with headings and code blocks, and a client-side search box that filters the nav. No backend.
 
 Static inspiration — a single self-contained `index.html` (inline CSS and JS,
-no external CDNs). It deploys instantly via `grid_drop` 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/docs-site/index.md

@@ -5,11 +5,10 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-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**
+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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "docs-site")` and fill in the user's content.

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

@@ -16,7 +16,7 @@
 # THIS TEMPLATE (landing-page): a single self-contained static page. The active fields
 # are exactly name + services.web{type: static, path: /}; there are no needs.
 # This cloudgrid.yaml is the reference for plugging it as an OWNED static
-# runtime; the fast path is to deploy it as an INSPIRATION via grid_drop
+# 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/landing-page/index.md

@@ -5,11 +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_drop`** (or `grid_plug` 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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "landing-page")` and fill in the user's content.

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

@@ -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 `grid_drop`) instead, then stop the runtime path.
+paywall-landing page (via `grid_plug`) instead, then stop the runtime path.

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

@@ -3,7 +3,7 @@
 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 `grid_drop` 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/portfolio/index.md

@@ -5,11 +5,10 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-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**
+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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "portfolio")` and fill in the user's content.

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

@@ -34,13 +34,12 @@ 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 **`grid_drop`** (or `grid_plug` with the
-inline HTML): you get a live share URL right away. Re-dropping the same entity
+(Claude Web) as well as local. Use **`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 `grid_drop`.
+fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `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
-# grid_drop (instant, and works on the hosted edition too).
+# grid_plug (instant, and works on the hosted edition too).
 # ============================================================================
 
 

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

@@ -8,11 +8,10 @@ client-side.
 
 ## How it deploys
 
-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**
+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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "product-launch")` and fill in the user's content

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 grid_drop
+# 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/report/index.md

@@ -5,11 +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_drop`** (or `grid_plug` 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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "report")` and fill in the user's content.

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

@@ -3,7 +3,7 @@
 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 `grid_drop` 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/saas-marketing/index.md

@@ -5,11 +5,10 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-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**
+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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "saas-marketing")` and fill in the user's content.

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

@@ -3,7 +3,7 @@
 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 `grid_drop` 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/status-page/index.md

@@ -5,11 +5,10 @@ State (if any) lives only in memory and is lost on refresh.
 
 ## How it deploys
 
-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**
+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_drop`.
+runtime (async, local edition only); the fast path is `grid_plug`.
 
 The fillable HTML is the real template — fetch it with
 `grid_fetch("template", "status-page")` and fill in the user's content.

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

@@ -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 `grid_drop`) instead, then stop the runtime
+static pricing/plans page (via `grid_plug`) instead, then stop the runtime
 path.

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_drop` and works on every
+no external CDNs). It deploys instantly via `grid_plug` and works on every
 CloudGrid edition, including hosted.
 
 ## Fill it in