@cloudgrid-io/mcp 0.19.2 → 0.20.2

package/README.md

@@ -9,7 +9,7 @@ It ships in two editions from one codebase:
 - **Web (hosted HTTP)** — a light, CLI-free toolset (drop, claim, login,
   visibility) for web clients like claude.ai. See [REMOTE.md](REMOTE.md).
 
-The local edition wraps the `cloudgrid` CLI for authenticated operations (the CLI
+The local edition wraps the `grid` CLI for authenticated operations (the CLI
 handles auth, org context, and error formatting) and calls the API directly for the
 drop, claim, and login tools.
 
@@ -33,10 +33,10 @@ Install and log in to the CLI:
 
 ```
 npm install -g @cloudgrid-io/cli
-cloudgrid login
+grid login
 ```
 
-The server reads no credentials directly. It runs `cloudgrid`, which uses its own
+The server reads no credentials directly. It runs `grid`, which uses its own
 stored credentials at `~/.cloudgrid/credentials`.
 
 ## Run
@@ -55,6 +55,16 @@ npm start
 
 It speaks MCP over stdio. Point any MCP client at the `cloudgrid-mcp` command.
 
+### QA session log (optional)
+
+Set `CLOUDGRID_QA_SLACK_WEBHOOK` to an **internal / private** Slack incoming-webhook
+URL to receive a per-session QA log (`log-<Client>-<transport>-mcp.txt`) when a
+session goes live, fails, or is abandoned. The log carries the user's first
+message (when the host forwards it) and identity details, so the target channel
+MUST be internal. Unset → the feature is fully dark (nothing captured, nothing
+posted). `CLOUDGRID_QA_IDLE_MS` overrides the abandoned-idle window (default
+900000 = 15 min).
+
 ## Tools
 
 ### Direct-API tools (both editions)
@@ -79,28 +89,28 @@ also work in the web edition where no CLI exists. `grid_login` writes the same
 
 | Tool | Wraps | Notes |
 |---|---|---|
-| `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_init` | `grid init` | Register an app or agent; optionally seed a web service. |
+| `grid_logs` | `grid logs` | Snapshot of recent logs. Does not stream. Read-only. |
+| `grid_share` | `grid visibility set` | Set visibility, default link. |
+| `grid_feedback` | `grid feedback list` | Read the org feedback feed. Read-only. |
+| `grid_whoami` | `grid whoami` | Show the signed-in user and active org. Read-only. |
+| `grid_use` | `grid use` | Switch the active org. |
+| `grid_logout` | `grid logout` | Sign out and clear local credentials. Destructive. |
+| `grid_status` | `grid status` | Org dashboard or entity detail. Read-only. |
+| `grid_info` | `grid info` | Entity metadata. Read-only. |
+| `grid_get` | `grid get grids\|entities\|spaces` | List grids, entities, or spaces. Read-only. |
+| `grid_describe_grid` | `grid describe grid <slug>` | Grid detail. Read-only. |
+| `grid_pickup` | `grid pickup <name>` | Download an entity's source and bind the folder. |
+| `grid_rename` | `grid rename` | Rename an entity's display name. |
+| `grid_unplug` | `grid unplug` | Take an entity off the grid. Destructive; requires confirm. |
+| `grid_delete` | `grid delete entity` | Archive an inspiration. Destructive; requires confirm. |
+| `grid_rollback` | `grid rollback` | Rollback to a previous version. |
+| `grid_versions` | `grid versions` | List published versions. Read-only. |
+| `grid_env` | `grid env` | Get, set, or list environment variables. |
+| `grid_secrets` | `grid secrets` | Set or list secret names. Never returns secret values. |
+| `grid_scaffold` | `grid scaffold` | Generate starter files. |
+| `grid_doctor` | `grid doctor` | Run local diagnostics. Read-only. |
+| `grid_open` | `grid 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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cloudgrid-io/mcp",
-  "version": "0.19.2",
+  "version": "0.20.2",
   "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": {
@@ -17,6 +17,7 @@
     "start:web": "node src/web.js",
     "smoke": "node test/smoke.mjs",
     "test:plug-wire": "node test/plug-wire.test.mjs",
+    "test:session-log": "node test/session-logger.test.mjs",
     "test:error-reporting": "node test/error-reporting.test.mjs",
     "test:source": "node test/source-fetch.test.mjs",
     "test:app-with-data": "node test/app-with-data.test.mjs",

package/src/auth.js

@@ -1,6 +1,6 @@
 // CLI-free sign-in against CloudGrid's existing OAuth backend.
 //
-// The flow is the same one `cloudgrid login` uses, driven without the CLI:
+// The flow is the same one `grid login` uses, driven without the CLI:
 //   1. pick a UUID `code`
 //   2. user opens GET /auth/login?code=<code> and signs in with Google
 //   3. poll GET /auth/status?code=<code> until it returns the signed JWT (once)

package/src/cli-shim.mjs

@@ -19,7 +19,7 @@
 // It also strips ELECTRON_RUN_AS_NODE from the environment: the variable has
 // done its job once this file is executing, and letting it leak further would
 // break anything Electron-based the CLI spawns later (e.g. a browser opened
-// for `cloudgrid login` would silently boot as a headless Node process).
+// for `grid login` would silently boot as a headless Node process).
 
 import { pathToFileURL } from "node:url";
 

package/src/corpus/capability-map.md

@@ -18,13 +18,14 @@ cloudgrid.yaml schema (every field, the `needs:` injection table, the
 requires-vs-needs caveat, validation rules), fetch the companion reference:
 `grid_fetch("doc", "cloudgrid-yaml")`.
 
-## The 59 templates
+## The 60 templates
 
 | Intent (match on `when:`) | Template | `needs:` | Deploy | Edition |
 |---|---|---|---|---|
 | landing page, marketing/product/hero page, coming-soon, link-in-bio, event page — a single-section page | `landing-page` | none | inspiration (instant) | all |
 | SaaS marketing site, product marketing page, features + pricing page — multi-section with pricing tiers, testimonials, FAQ | `saas-marketing` | none | inspiration (instant) | all |
-| documentation site, docs, developer docs, guide, manual, knowledge base — prose docs with sidebar + search | `docs-site` | none | inspiration (instant) | all |
+| single-page docs, a quick guide/manual/README-as-a-page, small knowledge base — prose with sidebar + search baked into ONE HTML file (instant, works on hosted). For a multi-page site you'll keep editing, use `docs-app` | `docs-site` | none | inspiration (instant) | all |
+| multi-page documentation site you'll keep editing, developer docs portal, knowledge base, help center — sidebar + full-text search + agent-readable llms.txt, built with Astro Starlight (separate content files, not one page). For a quick single page, use `docs-site` | `docs-app` | none | static build | local |
 | API documentation, API reference, endpoint docs, REST API docs — method badges, params tables, request/response examples | `api-docs` | none | inspiration (instant) | all |
 | status page, service status, uptime page, incident history, is-it-down page — display-only, status baked in | `status-page` | none | inspiration (instant) | all |
 | changelog, release notes, what's new, product updates, version history | `changelog` | none | inspiration (instant) | all |

package/src/corpus/cli-reference.md

@@ -42,39 +42,39 @@ brew install cloudgrid-io/tap/cloudgrid
 npm install -g @cloudgrid-io/cli
 ```
 
-**Manual** — download the latest from [Releases](https://github.com/cloudgrid-io/cli/releases), extract, and put `cloudgrid` on your `$PATH`.
+**Manual** — download the latest from [Releases](https://github.com/cloudgrid-io/cli/releases), extract, and put `grid` on your `$PATH`.
 
-Verify: `cloudgrid --version` and `cloudgrid doctor`. The shorthand `cg` works for every command.
+Verify: `grid --version` and `grid doctor`.
 
 ## Quickstart
 
 ```
-cloudgrid login          # Google OAuth in the browser
-cloudgrid whoami         # confirm user + active org
-cloudgrid plug           # build + deploy the current directory, prints the live URL
-cloudgrid open           # open it in the browser
+grid login          # Google OAuth in the browser
+grid whoami         # confirm user + active org
+grid plug           # build + deploy the current directory, prints the live URL
+grid open           # open it in the browser
 ```
 
-No account needed to try a one-off share: `cloudgrid plug ./index.html` drops a public link.
+No account needed to try a one-off share: `grid plug ./index.html` drops a public link.
 
 ## Examples
 
 ```
 # Scaffold and deploy a Node app
-cloudgrid init app my-api --type node
-cd my-api && cloudgrid plug
+grid init app my-api --type node
+cd my-api && grid plug
 
 # Deploy the current directory and tail its logs
-cloudgrid plug
-cloudgrid logs --since 10m
+grid plug
+grid logs --since 10m
 
 # Make a deploy public, then read feedback
-cloudgrid visibility set my-api link
-cloudgrid feedback
+grid visibility set my-api link
+grid feedback
 
 # Switch org, list what's on the grid
-cloudgrid use atomic
-cloudgrid grid
+grid use atomic
+grid grid
 ```
 
 ## Commands
@@ -122,7 +122,7 @@ Common per-command:
 npm update -g @cloudgrid-io/cli      # npm
 brew upgrade cloudgrid               # homebrew
 ```
-`cloudgrid doctor` warns when a newer version is available.
+`grid doctor` warns when a newer version is available.
 
 ## Uninstall
 
@@ -134,9 +134,9 @@ rm -rf ~/.cloudgrid                  # remove stored credentials + config
 
 ## Troubleshooting
 
-- **`cloudgrid: command not found`** — ensure the npm global bin (or Homebrew bin) is on `$PATH`; re-run the installer.
-- **Auth errors / 401** — `cloudgrid login` again; check `cloudgrid whoami` shows the expected org, switch with `cloudgrid use <org>`.
-- **Deploy fails** — run `cloudgrid doctor`; check `cloudgrid logs` and `cloudgrid status <name>` for the trace.
+- **`grid: command not found`** — ensure the npm global bin (or Homebrew bin) is on `$PATH`; re-run the installer.
+- **Auth errors / 401** — `grid login` again; check `grid whoami` shows the expected org, switch with `grid use <org>`.
+- **Deploy fails** — run `grid doctor`; check `grid logs` and `grid status <name>` for the trace.
 
 ## Support
 

package/src/corpus/cookbook.md

@@ -9,7 +9,7 @@ The CLI is installed and you are logged in:
 
 ```
 npm install -g @cloudgrid-io/cli
-cloudgrid login
+grid login
 ```
 
 ## The build-and-ship loop
@@ -23,27 +23,27 @@ init  ->  plug  ->  logs  ->  share  ->  feedback
 Register a new app and seed a static web service:
 
 ```
-cloudgrid init app my-thing --type static
+grid init app my-thing --type static
 ```
 
 `--type` accepts `node`, `nextjs`, `python`, or `static`. For an agent, use
-`cloudgrid init agent my-thing`.
+`grid init agent my-thing`.
 
 ### 2. Deploy
 
 From the project directory, deploy it:
 
 ```
-cloudgrid plug
+grid plug
 ```
 
-`cloudgrid plug` also takes a path or a URL. It builds and deploys, then prints the
+`grid plug` also takes a path or a URL. It builds and deploys, then prints the
 live URL. This usually takes about 30 seconds.
 
 ### 3. Watch the logs
 
 ```
-cloudgrid logs my-thing --follow
+grid logs my-thing --follow
 ```
 
 Drop `--follow` for a one-time tail. `--since 5m` limits how far back to read.
@@ -53,13 +53,13 @@ Drop `--follow` for a one-time tail. `--since 5m` limits how far back to read.
 Make the entity reachable by anyone with the link. The command prints the URL:
 
 ```
-cloudgrid visibility set my-thing link
+grid visibility set my-thing link
 ```
 
 ### 5. Read feedback
 
 ```
-cloudgrid feedback list
+grid feedback list
 ```
 
 ## Share an artifact with no account
@@ -98,10 +98,10 @@ the drop's expiry. Editing an archived or expired drop returns 409
 
 - **Ship an existing directory:** `plug`
 - **Deploy a URL as an inspiration:** `plug https://example.com`
-- **Refresh discovery metadata after a change:** `cloudgrid brain refresh my-thing --wait`
+- **Refresh discovery metadata after a change:** `grid brain refresh my-thing --wait`
 
 ## Notes
 
 - Every command uses the active org and linked entity when you omit the name. Run
-  `cloudgrid whoami` to see the active context.
+  `grid whoami` to see the active context.
 - These skills wrap the CLI. Anything the CLI can do, a skill can drive.

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

@@ -5,10 +5,10 @@ order. Stop and ask the user only where a step says to.
 
 ## 1. Ensure the CLI is present
 
-Check whether `cloudgrid` is on `$PATH`:
+Check whether `grid` is on `$PATH`:
 
 ```
-cloudgrid --version
+grid --version
 ```
 
 If that fails, install it:
@@ -20,10 +20,10 @@ npm install -g @cloudgrid-io/cli
 ## 2. Ensure the user is logged in
 
 ```
-cloudgrid whoami
+grid whoami
 ```
 
-If that fails, tell the user to run `cloudgrid login` and wait for them to confirm.
+If that fails, tell the user to run `grid login` and wait for them to confirm.
 Do not attempt to log in for them. Do not invent an auth flow.
 
 ## 3. Confirm the skills are available
@@ -44,7 +44,7 @@ Load the `SKILL.md` for the action the user wants:
 
 Each `SKILL.md` carries its own steps. Follow them exactly. The common rules:
 
-- Wrap only the `cloudgrid` CLI. Do not call the API directly.
+- Wrap only the `grid` CLI. Do not call the API directly.
 - Detect the user's language from their first message and reply in it. Keep
   technical flags in English.
 - Print results concisely: URLs and short summaries. Never dump raw JSON or IDs.

package/src/corpus/install.md

@@ -5,14 +5,14 @@ cover the CLI prerequisite, then each agent.
 
 ## Prerequisite: the CloudGrid CLI
 
-Every skill drives the `cloudgrid` CLI. Install it once and log in:
+Every skill drives the `grid` CLI. Install it once and log in:
 
 ```
 npm install -g @cloudgrid-io/cli
-cloudgrid login
+grid login
 ```
 
-`cloudgrid whoami` confirms you are logged in.
+`grid whoami` confirms you are logged in.
 
 ## Add the skills
 
@@ -124,7 +124,7 @@ The MCP server is published separately as
 npx -y @cloudgrid-io/mcp
 ```
 
-It wraps the same `cloudgrid` CLI and uses the same credentials, so no extra login
+It wraps the same `grid` CLI and uses the same credentials, so no extra login
 is needed. Remote-capable clients can point at `https://mcp.cloudgrid.io/mcp`
 instead. See [USAGE.md](USAGE.md) for per-client snippets.
 
@@ -138,7 +138,7 @@ Desktop: Settings, Extensions, Install from file):
 https://github.com/cloudgrid-io/mcp/releases/latest/download/cloudgrid.mcpb
 ```
 
-The bundle carries the full local toolset (including the `cloudgrid` CLI), so deploy
+The bundle carries the full local toolset (including the `grid` CLI), so deploy
 and secrets tools work without a separate install. Sign in from chat with the
 `grid_login` tool on first use.
 

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

@@ -14,8 +14,8 @@ 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 (`grid plug <path>` or
-`cloudgrid plug <path>`). If no terminal is available, stop and tell the user
+terminal is available, deploy from the CLI instead (`grid plug <path>`).
+If no terminal is available, stop and tell the user
 this is a known issue and needs the CLI.
 
 ## 429 anonymous cap

package/src/corpus/skill-brain.md

@@ -4,7 +4,7 @@ name: brain
 description: |
   Refresh a CloudGrid entity's Grid Brain metadata. Use when the user wants to
   re-classify an entity, regenerate its description, tags, or diagram, or update
-  how it appears in discovery after a change. Wraps cloudgrid brain refresh.
+  how it appears in discovery after a change. Wraps grid brain refresh.
 argument-hint: "[name]"
 allowed-tools: Bash
 ---
@@ -13,12 +13,12 @@ allowed-tools: Bash
 
 Re-run the Grid Brain hooks for an entity to re-classify its description, tags, and
 diagram. Use this after a change so discovery reflects the current state. Wraps
-`cloudgrid brain refresh`.
+`grid brain refresh`.
 
 ## Step 0 — Bootstrap
 
-1. If `cloudgrid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
-2. If `cloudgrid whoami` fails: ask the user to run `cloudgrid login`. Wait for
+1. If `grid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
+2. If `grid whoami` fails: ask the user to run `grid login`. Wait for
    confirmation.
 
 ## UX rules
@@ -30,7 +30,7 @@ diagram. Use this after a change so discovery reflects the current state. Wraps
 ## How to run it
 
 ```
-cloudgrid brain refresh my-thing --wait
+grid brain refresh my-thing --wait
 ```
 
 `--wait` polls until the refresh finishes, up to about 60 seconds. Without it, the
@@ -46,4 +46,4 @@ Other flags:
 
 The refresh reports each hook: classify (description and tags), identification, and
 the diagram. Summarize the outcome in one line, for example "Re-classified with 3
-tags." Suggest `cloudgrid status <name>` if the user wants the full updated entity.
+tags." Suggest `grid status <name>` if the user wants the full updated entity.

package/src/corpus/skill-claim.md

@@ -21,7 +21,7 @@ re-homes the drop into the user's grid, so its public URL changes from
 ## Step 0 — sign in first
 
 Claiming needs an identity. If the user is not signed in, run the `cloudgrid:login`
-skill (or `cloudgrid login` with the CLI) first.
+skill (or `grid login` with the CLI) first.
 
 ## What you need
 

package/src/corpus/skill-feedback.md

@@ -4,19 +4,19 @@ name: feedback
 description: |
   Read the CloudGrid feedback feed. Use when the user wants to see feedback, check
   what people said, review reactions, or read recent feedback events for their org.
-  Wraps cloudgrid feedback list.
+  Wraps grid feedback list.
 argument-hint: "[--since 7d]"
 allowed-tools: Bash
 ---
 
 # CloudGrid Feedback
 
-List recent feedback events for the active org. Wraps `cloudgrid feedback list`.
+List recent feedback events for the active org. Wraps `grid feedback list`.
 
 ## Step 0 — Bootstrap
 
-1. If `cloudgrid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
-2. If `cloudgrid whoami` fails: ask the user to run `cloudgrid login`. Wait for
+1. If `grid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
+2. If `grid whoami` fails: ask the user to run `grid login`. Wait for
    confirmation.
 
 ## UX rules
@@ -28,7 +28,7 @@ List recent feedback events for the active org. Wraps `cloudgrid feedback list`.
 ## How to run it
 
 ```
-cloudgrid feedback list
+grid feedback list
 ```
 
 The feed is scoped to the active org. It is not filtered by entity. Useful flags:
@@ -44,6 +44,6 @@ when there are many. Surface the ones that look like bugs or blockers first.
 
 ## Note: reading vs sending
 
-This skill reads the feed. `cloudgrid feedback "<message>"` does the opposite: it
+This skill reads the feed. `grid feedback "<message>"` does the opposite: it
 sends feedback to the CloudGrid team. Do not send feedback unless the user clearly
 asks to report something.

package/src/corpus/skill-init.md

@@ -4,7 +4,7 @@ name: init
 description: |
   Scaffold a new CloudGrid app or agent. Use when the user wants to start a new
   project, create a new entity, set up a new app or agent, or seed a web service
-  (node, nextjs, python, or static) before deploying. Wraps cloudgrid init.
+  (node, nextjs, python, or static) before deploying. Wraps grid init.
 argument-hint: "[app|agent] [name]"
 allowed-tools: Bash
 ---
@@ -12,12 +12,12 @@ allowed-tools: Bash
 # CloudGrid Init
 
 Register a new app or agent in the active org and, optionally, seed a web service
-to deploy. Wraps `cloudgrid init`. After this, `cloudgrid:plug` deploys it.
+to deploy. Wraps `grid init`. After this, `cloudgrid:plug` deploys it.
 
 ## Step 0 — Bootstrap
 
-1. If `cloudgrid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
-2. If `cloudgrid whoami` fails: ask the user to run `cloudgrid login`. Wait for
+1. If `grid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
+2. If `grid whoami` fails: ask the user to run `grid login`. Wait for
    confirmation.
 
 ## UX rules
@@ -47,25 +47,25 @@ Optional, only if the user implies them:
 Register an app and seed a static site:
 
 ```
-cloudgrid init app my-thing --type static
+grid init app my-thing --type static
 ```
 
 Register an agent:
 
 ```
-cloudgrid init agent my-helper
+grid init agent my-helper
 ```
 
 Register without seeding any files (you will add your own):
 
 ```
-cloudgrid init app my-thing
+grid init app my-thing
 ```
 
 ## After init
 
 Tell the user the entity is registered and what is next: `cd` into the directory
-(if seeded) and run `cloudgrid plug` to deploy. Hand off to `cloudgrid:plug`.
+(if seeded) and run `grid plug` to deploy. Hand off to `cloudgrid:plug`.
 
 ## References
 

package/src/corpus/skill-login.md

@@ -18,10 +18,10 @@ There are two paths. Pick the first that fits.
 
 ## Path 1 — the CLI is installed
 
-If `cloudgrid` is on `$PATH`, this is the simplest and safest:
+If `grid` is on `$PATH`, this is the simplest and safest:
 
 ```
-cloudgrid login
+grid login
 ```
 
 It opens the browser, handles the OAuth flow, and stores the token. Stop here.
@@ -74,7 +74,7 @@ uses (`~/.cloudgrid/credentials`), so the two share one identity.
 
 ## After login
 
-Confirm the user is signed in (`cloudgrid whoami` if the CLI is present). If they
+Confirm the user is signed in (`grid whoami` if the CLI is present). If they
 made an anonymous drop earlier, this is the moment to offer to claim it.
 
 ## Notes

package/src/corpus/skill-logs.md

@@ -4,19 +4,19 @@ name: logs
 description: |
   Tail logs for a CloudGrid entity. Use when the user wants to see logs, watch
   output, follow a running app, debug a deploy, or check why something is failing.
-  Wraps cloudgrid logs.
+  Wraps grid logs.
 argument-hint: "[name]"
 allowed-tools: Bash
 ---
 
 # CloudGrid Logs
 
-Stream or tail logs from an entity's pods. Wraps `cloudgrid logs`.
+Stream or tail logs from an entity's pods. Wraps `grid logs`.
 
 ## Step 0 — Bootstrap
 
-1. If `cloudgrid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
-2. If `cloudgrid whoami` fails: ask the user to run `cloudgrid login`. Wait for
+1. If `grid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
+2. If `grid whoami` fails: ask the user to run `grid login`. Wait for
    confirmation.
 
 ## UX rules
@@ -30,7 +30,7 @@ Stream or tail logs from an entity's pods. Wraps `cloudgrid logs`.
 Tail the recent logs for an entity by name:
 
 ```
-cloudgrid logs my-thing
+grid logs my-thing
 ```
 
 With no name, it uses the entity linked to the current directory.

package/src/corpus/skill-plug.md

@@ -6,7 +6,7 @@ description: |
   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.
+  directory or URL. Wraps grid plug.
 argument-hint: "[path-or-url]"
 allowed-tools: Bash
 ---
@@ -23,7 +23,7 @@ Deploy or share a creation and get a public URL. This is the one deploy/share ve
   **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**,
+  → a **runtime app**: `grid plug` on a linked folder, **local edition only**,
   async build. See "Deploy an app" below.
 
 ## Share a single HTML page (the fast path)
@@ -75,12 +75,12 @@ Print the `url` on its own line so it can be copied in one go. A single page is
 
 ## Deploy an app
 
-Wraps `cloudgrid plug`. Prints the live URL when it is done.
+Wraps `grid plug`. Prints the live URL when it is done.
 
 ## Step 0 — Bootstrap
 
-1. If `cloudgrid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
-2. If `cloudgrid whoami` fails: ask the user to run `cloudgrid login`. Wait for
+1. If `grid` is not on `$PATH`: `npm install -g @cloudgrid-io/cli`
+2. If `grid whoami` fails: ask the user to run `grid login`. Wait for
    confirmation.
 
 ## UX rules
@@ -95,7 +95,7 @@ Wraps `cloudgrid plug`. Prints the live URL when it is done.
 Most of the time, run it from the project directory with no arguments:
 
 ```
-cloudgrid plug
+grid plug
 ```
 
 It uses the entity linked to the directory, builds, deploys, and prints the URL.
@@ -103,9 +103,9 @@ A first deploy usually takes about 30 seconds; larger builds take longer.
 
 Other shapes:
 
-- **A specific path:** `cloudgrid plug ./site`
-- **A URL as an inspiration:** `cloudgrid plug https://example.com`
-- **Bind to an existing entity first:** `cloudgrid plug --existing <entity-id>`
+- **A specific path:** `grid plug ./site`
+- **A URL as an inspiration:** `grid plug https://example.com`
+- **Bind to an existing entity first:** `grid plug --existing <entity-id>`
 
 If this is the user's first deploy in the org, the CLI may ask which org to use.
 Pass `--org <slug>` to skip that prompt.