@cloudgrid-io/mcp 0.20.13 → 0.20.15

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

@@ -34,8 +34,8 @@ grid_get_template("template", "restaurant-reservations")   # cloudgrid.yaml + AG
 
 Then read `AGENTS.md` (file tree, `menu`/`reservations`/`tables` collections,
 CloudGrid env/vault/deploy wiring, Stripe + auth, cron shape) and build under
-`services/web/`. Deploy: `grid init` → fill → `grid plug` (async — poll to a live
-URL). Local edition only.
+`services/web/`. Deploy: `grid plug` (the first plug auto-creates the entity from
+`cloudgrid.yaml`; async — poll to a live URL). Local edition only.
 
 ## cloudgrid.yaml (active fields)
 

package/src/corpus/templates/semantic-search/AGENTS.md

@@ -200,9 +200,10 @@ This is a built + deployed multi-service app → the **local edition** (Claude
 Desktop / Claude Code) or the CLI; the hosted edition cannot build a runtime
 container.
 
-1. `grid init semantic-search` — creates the entity + `.cloudgrid/link.json`.
-2. Put the code under `services/web/` and `services/backend/`; set `cloudgrid.yaml`
+1. Put the code under `services/web/` and `services/backend/`; set `cloudgrid.yaml`
    to the active fields (web static+build, backend python, `needs:{database:true}`).
+2. `grid plug --no-deploy` — registers the entity from the manifest (honors its
+   `name:`) and writes `.cloudgrid/link.json`, without building yet.
 3. `grid secrets set …` for embeddings + source + `MANAGER_PASSWORD_HASH` (§6).
 4. (Optional) `grid dev` to run locally against injected dev Mongo.
 5. **Build the frontend first:** `(cd services/web && npm install && npm run build)`.

package/src/corpus/templates/semantic-search/README.md

@@ -63,7 +63,7 @@ search / indexing degrade to a clear "not indexed / missing secret" state.
 ## Deploy (manager does this)
 
 ```bash
-grid init semantic-search   # creates the entity + .cloudgrid/link.json
+grid plug --no-deploy       # registers the entity from cloudgrid.yaml + writes .cloudgrid/link.json
 grid secrets set EMBEDDINGS_API_KEY=sk-...   # + source secrets + MANAGER_PASSWORD_HASH
 
 # Build the static frontend BEFORE plug — CloudGrid validates that a

package/src/corpus/templates/semantic-search/index.md

@@ -94,7 +94,8 @@ needs:
 
 ## Configure + deploy
 
-1. `grid init semantic-search` — creates the entity + `.cloudgrid/link.json`.
+1. `grid plug --no-deploy` — registers the entity from `cloudgrid.yaml` (honors
+   its `name:`) and writes `.cloudgrid/link.json`, without building yet.
 2. `grid secrets set EMBEDDINGS_API_KEY=sk-…` plus the source secrets
    (`SOURCE_TYPE` + Dropbox/local/url config) and `MANAGER_PASSWORD_HASH`
    (sha256 hex of the manager password). See `AGENTS.md`.

package/src/corpus/templates/simple-semantic-search/README.md

@@ -11,10 +11,11 @@ the platform holds the pod out of traffic until search works.
 
 Proven by a real end-to-end deploy (live in under 3 minutes, 2026-07-16).
 
-- Deploy: `grid init app <name> --here`, then `grid plug`.
-- The CLI writes `.cloudgrid/link.json` (folder ↔ entity binding) — never
-  hand-author it; `rm -rf .cloudgrid` + re-init to take a copied folder as your
-  own app.
+- Deploy: `grid plug` — the first plug auto-creates the entity from
+  `cloudgrid.yaml` and deploys it.
+- The CLI writes `.cloudgrid/link.json` (folder ↔ entity binding) on that first
+  plug — never hand-author it; `rm -rf .cloudgrid` + re-plug to take a copied
+  folder as your own app.
 - Replace `services/web/src/document.txt` with the content to index.
 - For a multi-service search portfolio (upload UI + refresh cron), use the
   `semantic-search` blueprint instead.

package/src/corpus/templates/simple-semantic-search/index.md

@@ -39,7 +39,8 @@ services/web/src/document.txt       # the content to index — replace with the
 
 ## What the CLI writes for you: `.cloudgrid/link.json`
 
-After `grid init app <name> --here` (or the first `grid plug`), the CLI binds
+On the first `grid plug` (which auto-creates the entity from `cloudgrid.yaml`,
+honoring its `name:`), the CLI binds
 the folder to its grid entity by writing `.cloudgrid/link.json`. It looks like:
 
 ```json
@@ -55,20 +56,22 @@ the folder to its grid entity by writing `.cloudgrid/link.json`. It looks like:
 ```
 
 **Never hand-author or copy this file** — the CLI writes it, and every value is
-minted at init time (the slug gets a 4-hex suffix). Two practical consequences:
+minted when the entity is first registered (the slug gets a 4-hex suffix). Two
+practical consequences:
 
 - A folder **with** `.cloudgrid/link.json` is bound: `grid plug` UPDATES that
   entity. To fork someone else's project into your own app, `rm -rf .cloudgrid`
-  (and remove any `name:` you don't own from `cloudgrid.yaml`), then
-  `grid init app <your-name> --here` for a fresh identity.
+  (and remove any `name:` you don't own from `cloudgrid.yaml`) — the next
+  `grid plug` mints a fresh identity.
 - `link.json` is why identity does NOT belong in `cloudgrid.yaml` — the
   manifest describes the app; the link binds the folder.
 
 ## Deploy
 
 ```bash
-grid init app <name> --here     # once, registers the entity + writes .cloudgrid/link.json
-grid plug                       # build + deploy, async — live URL in ~2-3 min
+grid plug                       # first plug registers the entity from cloudgrid.yaml
+                                # + writes .cloudgrid/link.json, then builds + deploys
+                                # (async — live URL in ~2-3 min)
 grid visibility set <slug> link # default is grid-only (403 outside the org)
 ```
 

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

@@ -160,9 +160,10 @@ known user — otherwise anyone could change anyone's plan.
 
 1. `grid_login_status` → `grid_login` if needed. Respect the grid picker
    (ask which grid if the user has more than one).
-2. `grid_create_project` an app `<name>` FIRST — it creates the entity, writes
-   `.cloudgrid/link.json`, and a `cloudgrid.yaml` with empty `services: {}`.
-   `plug` needs a linked directory.
+2. `grid_create_project` an app `<name>` — it scaffolds the project folder and
+   a `cloudgrid.yaml` with empty `services: {}`. No server entity exists yet —
+   the first plug auto-creates it from the manifest (honoring its `name:`) and
+   writes `.cloudgrid/link.json`.
 3. Write the app under `services/web/` and set `cloudgrid.yaml` to the active
    shape: `name` + `services.web{type: nextjs, path: /}` + `needs:{database:true}`
    + the `vault:` block.

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

@@ -152,12 +152,11 @@ webhook signing secret as `STRIPE_WEBHOOK_SECRET`; read both lazily in
 
 ## 5. Deploy steps
 
-1. `grid init` — scaffolds the entity + `.cloudgrid/link.json`; writes a
-   `cloudgrid.yaml` with an empty `services: {}`. Run this FIRST (plug needs a
-   linked directory).
-2. Fill it in: build the files under `services/web/` and set `cloudgrid.yaml` to
+1. Build the files under `services/web/` and set `cloudgrid.yaml` to
    this template's shape (`services.web` nextjs + `needs: { database: true }` +
    the `vault:` block).
+2. `grid plug --no-deploy` — registers the entity from the manifest (honors its
+   `name:`) and writes `.cloudgrid/link.json`, without building yet.
 3. `grid secrets set stripe-live-key <sk_live_…>` and the other vault items
    (`stripe-webhook-secret`, `auth-provider-key`), so the `vault:` mappings
    resolve at deploy.

package/src/corpus/templates/travel-booking/index.md

@@ -70,8 +70,8 @@ The heart of this blueprint. Read it before building. It covers:
 4. **Auth + payments wiring** — provider SDK from `AUTH_PROVIDER_KEY`; Stripe
    checkout + signature-verified webhook from `STRIPE_KEY` /
    `STRIPE_WEBHOOK_SECRET`.
-5. **Deploy steps** — `grid init` → fill → `grid secrets set` → `grid plug` →
-   poll to live.
+5. **Deploy steps** — write the files → `grid plug --no-deploy` →
+   `grid secrets set` → `grid plug` → poll to live.
 6. **Edition note** — runtime app → local edition only (hosted is static-only).
 7. **Trip-reminder cron** — intended shape + the platform-issue-#1543 PENDING note
    and stopgap.

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

@@ -39,9 +39,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

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

@@ -41,9 +41,9 @@ Persistent apps are owned entities.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST.
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
 
 You then do two things: (a) write the app under **`services/web/`**, and (b) fill
 in `cloudgrid.yaml` to the shape below (`services.web` type `nextjs` + `needs: {

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

@@ -65,9 +65,11 @@ There is no app code to copy — you generate it from the guide.
 
 ## 4. Scaffold + fill cloudgrid.yaml
 
-`grid_create_project` an app `<name>` FIRST (creates the entity + `.cloudgrid/link.json`
-and a starter `cloudgrid.yaml` with empty `services:{}`; `plug` needs a linked
-directory). Then put the app under **`services/web/`** and set `cloudgrid.yaml` to
+`grid_create_project` an app `<name>` — it scaffolds the project folder and a
+starter `cloudgrid.yaml` with empty `services:{}` (no server entity yet; the
+first `grid plug` auto-creates it from the manifest, honoring its `name:`, and
+writes `.cloudgrid/link.json`). Then put the app under **`services/web/`** and
+set `cloudgrid.yaml` to
 the blueprint's active fields:
 
 ```yaml

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

@@ -40,9 +40,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

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

@@ -39,9 +39,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

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

@@ -42,9 +42,9 @@ Persistent services are owned entities.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST.
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
 
 You then do two things: (a) write the service under **`services/api/`**, and (b)
 fill in `cloudgrid.yaml` to the shape below (`services.api` type `node` + `needs:

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

@@ -43,9 +43,9 @@ Persistent apps are owned entities.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>` (the default `--type` is fine). `init` creates
-the entity + `.cloudgrid/link.json` and writes a `cloudgrid.yaml` with an EMPTY
-`services: {}`. `plug` needs a linked directory, so run `init` FIRST.
+`grid_create_project` an app `<name>` (the default `--type` is fine). It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
 
 You then do two things: (a) write the app under **`services/web/`**, and (b) fill
 in `cloudgrid.yaml` to the shape below (`services.web` + `needs: { database: true }`).

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

@@ -54,9 +54,10 @@ workflow:
 
 ## 4. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then write the app under **`services/web/`** and
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then write the app under **`services/web/`** and
 set `cloudgrid.yaml` to the active shape below.
 
 ## 5. Build the app following AGENTS.md

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

@@ -55,9 +55,10 @@ route, server page).
 
 ## 4. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**
 following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
 
 ## 5. Build the app + wire Mongo

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

@@ -43,9 +43,9 @@ A persistent billing dashboard is a built + deployed container. It requires the
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST.
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
 
 ## 4. Fetch the blueprint and read AGENTS.md
 

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

@@ -39,9 +39,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

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

@@ -52,9 +52,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
    `services` / `availabilityRules` / `bookings` collections + the double-booking
    guard, how CloudGrid injects the DB and vault secrets, how to wire Stripe +
    auth, and the reminder-cron design).
-2. `grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-   and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a
-   linked directory, so run `init` FIRST.
+2. `grid_create_project` an app `<name>`. It scaffolds the project folder and
+   writes a `cloudgrid.yaml` with an EMPTY `services: {}`. No server entity
+   exists yet — the first `grid plug` auto-creates it from the manifest
+   (honoring its `name:`) and writes `.cloudgrid/link.json`.
 
 ## 4. Build the app + set cloudgrid.yaml
 

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

@@ -56,9 +56,11 @@ There is no app code to copy — you generate it from the guide.
 
 ## 4. Scaffold + fill cloudgrid.yaml
 
-`grid_create_project` an app `<name>` FIRST (creates the entity + `.cloudgrid/link.json`
-and a starter `cloudgrid.yaml` with empty `services:{}`; `plug` needs a linked
-directory). Then put the app under **`services/web/`** and set `cloudgrid.yaml` to
+`grid_create_project` an app `<name>` — it scaffolds the project folder and a
+starter `cloudgrid.yaml` with empty `services:{}` (no server entity yet; the
+first `grid plug` auto-creates it from the manifest, honoring its `name:`, and
+writes `.cloudgrid/link.json`). Then put the app under **`services/web/`** and
+set `cloudgrid.yaml` to
 the blueprint's active fields:
 
 ```yaml

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

@@ -57,9 +57,10 @@ contains AGENTS.md — the CloudGrid-specific spec you must follow:
 
 ## 4. Scaffold + fill cloudgrid.yaml
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. Run `init` FIRST —
-`plug` needs a linked directory. Then set `cloudgrid.yaml` to the shape below and
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes
+a `cloudgrid.yaml` with an EMPTY `services: {}`. No server entity exists yet —
+the first `grid plug` auto-creates it from the manifest (honoring its `name:`)
+and writes `.cloudgrid/link.json`. Then set `cloudgrid.yaml` to the shape below and
 write the app under **`services/web/`** (`path: /` is the URL mount, NOT the
 filesystem path).
 

package/src/corpus/workflows/crm.md

@@ -38,9 +38,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

package/src/corpus/workflows/directory.md

@@ -39,9 +39,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

package/src/corpus/workflows/erp.md

@@ -56,9 +56,10 @@ all four at once.
 
 ## 4. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) build the app under **`services/web/`**
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) build the app under **`services/web/`**
 following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
 
 ## 5. Build the app + set cloudgrid.yaml

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

@@ -38,9 +38,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

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

@@ -38,9 +38,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

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

@@ -39,9 +39,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

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

@@ -39,9 +39,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

package/src/corpus/workflows/forum.md

@@ -62,10 +62,11 @@ edition** (Claude Desktop / Claude Code) or the CLI.
    `AGENTS.md` — it defines the file tree, the `threads` / `posts` / `users`
    collections + fields, the nesting model, and the CloudGrid wiring. This is the
    spec you build to.
-2. `grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-   and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a
-   linked directory, so run `init` FIRST. Then write the app under
-   **`services/web/`** and fill `cloudgrid.yaml` to the shape below.
+2. `grid_create_project` an app `<name>`. It scaffolds the project folder and
+   writes a `cloudgrid.yaml` with an EMPTY `services: {}`. No server entity
+   exists yet — the first `grid plug` auto-creates it from the manifest
+   (honoring its `name:`) and writes `.cloudgrid/link.json`. Then write the app
+   under **`services/web/`** and fill `cloudgrid.yaml` to the shape below.
 
 ## 4. Build the app + wire Mongo, auth, moderation
 

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

@@ -51,9 +51,10 @@ to wire employee/admin auth, and the deploy steps.
 
 ## 4. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) build the app under **`services/web/`**
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) build the app under **`services/web/`**
 following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
 
 ## 5. Build the app + set cloudgrid.yaml

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

@@ -54,9 +54,10 @@ deploy steps.
 
 ## 4. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) build the app under **`services/web/`**
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) build the app under **`services/web/`**
 following `AGENTS.md`, and (b) fill `cloudgrid.yaml` to the shape below.
 
 ## 5. Build the app + set cloudgrid.yaml

package/src/corpus/workflows/inventory.md

@@ -37,9 +37,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

package/src/corpus/workflows/invoice.md

@@ -37,9 +37,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

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

@@ -37,9 +37,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).
 

package/src/corpus/workflows/kanban.md

@@ -37,9 +37,10 @@ edition** (Claude Desktop / Claude Code) or the CLI.
 
 ## 3. Scaffold
 
-`grid_create_project` an app `<name>`. `init` creates the entity + `.cloudgrid/link.json`
-and writes a `cloudgrid.yaml` with an EMPTY `services: {}`. `plug` needs a linked
-directory, so run `init` FIRST. Then (a) write the app under **`services/web/`**,
+`grid_create_project` an app `<name>`. It scaffolds the project folder and writes a `cloudgrid.yaml` with an EMPTY
+`services: {}`. No server entity exists yet — the first `grid plug` auto-creates
+it from the manifest (honoring its `name:`) and writes `.cloudgrid/link.json`.
+Then (a) write the app under **`services/web/`**,
 and (b) fill `cloudgrid.yaml` to the shape below (`services.web` + `needs:
 { database: true }`).