@vectros-ai/cli 0.5.1 → 0.6.1

package/AUTHORING.md

@@ -80,6 +80,15 @@ A name must be 2–50 chars: a lowercase letter, then lowercase letters / digits
 `bootstrap` shows the same plan and asks for confirmation before minting
 (`--yes` skips the prompt for CI/agents; `--print` previews without minting).
 
+**Provisioning a production context — `--no-seed`.** A blueprint's `seed`
+records are illustrative sample data: handy for a getting-started or demo
+context, but synthetic clutter in a context that will hold real data. Pass
+`bootstrap --no-seed` to provision everything *except* the seed records — the
+schemas, profile and scoped key still apply, and the plan above drops its
+`+ seed` line so the preview matches. (Interactively, a blueprint with seeds
+asks before adding them.) This is distinct from `--blank`, which is
+credential-only and provisions no schemas at all.
+
 ### 4. `blueprint-test` — prove it live, then clean up (needs creds)
 
 `validate`/`plan` are static; `blueprint-test` is the live proof. It **applies** the blueprint to a real
@@ -144,6 +153,9 @@ seed:
   - typeName: thing
     externalId: seed-welcome   # stable → idempotent; re-apply converges
     fields: { title: "Hello" }
+    # Seeds are illustrative sample data. They're applied by default; provision a
+    # production context with `bootstrap --no-seed` to skip them (schemas + key
+    # still apply).
 ```
 
 YAML or JSON are both accepted (chosen by extension). The bundled library is

package/CHANGELOG.md

@@ -3,6 +3,30 @@
 All notable changes to `@vectros-ai/cli` are documented here.
 This project adheres to [Semantic Versioning](https://semver.org).
 
+## 0.6.1 — 2026-06-27
+
+Maintenance — refreshed the bundled Vectros SDK to the current API surface.
+
+### Changed
+
+- Updated the bundled `@vectros-ai/sdk` to **0.30.0**, keeping the CLI aligned
+  with the current Vectros API (and the SDK version the CLI reports). The 0.30.0
+  API adds a document-type search facet (`typeName` now scopes documents as well
+  as records), clearer rate-limit signals (a `429` carries `Retry-After` and
+  `X-RateLimit-*` headers plus a `RATE_LIMITED` error code), and a read-metering
+  section in the usage report. No CLI commands or flags changed.
+
+## 0.6.0 — 2026-06-26
+
+### Added
+
+- `vectros bootstrap --no-seed` — provision a blueprint's schemas, AccessProfile
+  and scoped key **without** its illustrative seed records. The right choice for
+  a **production** context, where a blueprint's sample data is synthetic clutter.
+  Unlike `--blank` (credential-only), the schemas are still created. The plan
+  preview and the run summary both reflect the skip (`Seeded 0 — skipped`), and
+  an interactive run with a seeded blueprint now asks before adding sample data.
+
 ## 0.5.1 — 2026-06-25
 
 Maintenance — refreshed the bundled Vectros SDK to the current API surface.

package/README.md

@@ -47,12 +47,23 @@ VECTROS_BOOTSTRAP_TOKEN=… npx -y @vectros-ai/cli bootstrap \
 npx -y @vectros-ai/cli login
 npx -y @vectros-ai/cli bootstrap --blueprint task-management --yes
 
+# Provision a PRODUCTION context: the blueprint's schemas + key, but NONE of its
+# illustrative sample records.
+npx -y @vectros-ai/cli bootstrap --blueprint task-management --no-seed --yes
+
 # See every flag.
 npx -y @vectros-ai/cli bootstrap --help
 ```
 
 Re-running is idempotent; `--rotate` revokes + re-mints just this machine's key.
 
+A bundled blueprint ships with **sample seed records** so the credential works
+the moment it's minted. For a **production** context that's synthetic clutter:
+`--no-seed` provisions everything else — the schemas, the AccessProfile and the
+scoped key — but creates no sample records, leaving the context clean for real
+data. (Interactively, a blueprint with seeds asks before adding them.) This
+differs from `--blank`, which is credential-only and drops the schemas too.
+
 ## `vectros blueprint` — authoring (creds-free)
 
 Author and inspect blueprints without an account. You'll run these repeatedly,
@@ -107,6 +118,13 @@ mint to a data-plane allowlist (`records` / `schemas` / `search` / `documents`
 billing / admin) or `*` wildcard **hard-rejects** — the CLI mints nothing and
 exits non-zero. There is intentionally **no override flag**.
 
+## Rate limits
+
+`blueprint-test` provisions against the live API, so a large blueprint can brush the per-account
+per-minute rate limit. The CLI surfaces the `429` (with its `Retry-After` hint) directly — rerun
+after the window resets, or split a large blueprint. See the
+[rate limits guide](https://docs.vectros.ai/guides/operations-trust/rate-limits).
+
 ## See also
 
 - [`@vectros-ai/mcp-server`](https://www.npmjs.com/package/@vectros-ai/mcp-server) — the runtime this CLI provisions for.