@vectros-ai/cli 0.5.0

package/AUTHORING.md

@@ -0,0 +1,241 @@
+# Authoring Vectros blueprints
+
+A **blueprint** is a versioned, reviewed bundle for one use case: a schema set
++ a **least-privilege** AccessProfile + a service principal + optional seed
+data, all with stable identifiers so applying it twice converges instead of
+duplicating. `vectros bootstrap --blueprint <file>` applies it to provision a
+ready-to-use data model + a narrow `ssk_*` scoped key — no root key, no manual
+admin steps.
+
+This guide is the authoring loop. Everything here except `bootstrap` is
+**creds-free and offline** — you can iterate on a blueprint with no account.
+
+> The examples use the bare `vectros` binary — install it once with
+> `npm i -g @vectros-ai/cli`, or prefix any command with `npx -y @vectros-ai/cli`
+> (no install, but slower per call — fine for a one-off, tedious for the loop).
+
+## The loop
+
+```
+vectros blueprint init my-thing        # 1. scaffold a starter
+# …edit ./my-thing.blueprint.yaml…
+vectros blueprint validate ./my-thing.blueprint.yaml   # 2. structural + scope-gate + lint (offline)
+vectros blueprint plan     ./my-thing.blueprint.yaml   # 3. preview what it provisions (offline)
+vectros blueprint-test     ./my-thing.blueprint.yaml --env staging  # 4. prove it live (creds; auto-teardown)
+vectros bootstrap --blueprint ./my-thing.blueprint.yaml # 5. apply for real (needs a bridge token)
+```
+
+Steps 1–3 are **creds-free and offline**. Step 4 (`blueprint-test`) and step 5 (`bootstrap`) hit a live
+environment — sign in once first with `vectros login` (`vectros whoami` shows the active session;
+`vectros logout` clears it), or pass `--token`.
+
+### 1. `init` — scaffold
+
+```
+vectros blueprint init my-thing                 # → ./my-thing.blueprint.yaml (commented template)
+vectros blueprint init my-tasks --from task-management   # copy the closest bundled exemplar
+vectros blueprint init my-thing --out ./bp.yaml --force  # custom path / overwrite
+```
+
+The default scaffold is a heavily-commented YAML starter — the comments *are*
+the docs. `--from <bundled>` copies a real bundled blueprint (run
+`vectros blueprint list` to see them) so you start from a working example.
+A name must be 2–50 chars: a lowercase letter, then lowercase letters / digits
+/ dashes (it's the stable idempotency key).
+
+### 2. `validate` — the inner-loop check (no creds)
+
+`validate` runs three layers and exits non-zero on any failure:
+
+1. **Structural** — the file parses against the blueprint schema (readable
+   `path: message` errors, e.g. `schemas[0].fields[1]: Required`).
+2. **Scope gate** — the requested `allowedActions` are data-plane only. This is
+   the trust boundary: control-plane scopes (`keys`, `profiles`,
+   `users`, `admin`, …) and the `*` wildcard are **hard-rejected, no override**.
+   A forked or hand-written blueprint gets the *identical* gate a bundled one
+   does — it can never escalate.
+3. **Lint** — semantic checks: duplicate `fieldId`, a `lookupField` naming a
+   field that doesn't exist, a `seed` for a typeName with no schema (errors);
+   `enumValues` on an incompatible type, and the dataScope null-sentinel nudge
+   (warnings — they print but don't fail).
+
+`validate` accepts a file path **or** a bundled blueprint name.
+
+### 3. `plan` — preview before you mint
+
+`plan` validates, then prints a terraform-style preview of exactly what
+`bootstrap` would provision — schemas, context, principal, profile, key, seed —
+**without minting anything**:
+
+```
+  Plan for blueprint 'my-thing' (v1.0.0) → context 'mcp':
+    + schema 'thing' (2 fields, HYBRID) lookup: [externalId]
+    + context 'mcp' (MCP — my-thing)
+    + principal 'my-thing-sp' (SERVICE)
+    + profile scopes [records:r, records:c, records:u, search:r, schemas:r] (data-plane ✓)
+    + key my-thing-<machine> (mint 1 scoped ssk_*)
+    + seed 1 record(s)
+```
+
+`bootstrap` shows the same plan and asks for confirmation before minting
+(`--yes` skips the prompt for CI/agents; `--print` previews without minting).
+
+### 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
+environment, **asserts** the result — the app-context + every schema read back, and the freshly minted
+`ssk_*` authenticates as a scoped key carrying exactly the actions you requested — then **tears down**
+everything it created:
+
+```
+vectros login                                            # sign in once (or pass --token)
+vectros blueprint-test ./my-thing.blueprint.yaml --env staging
+vectros blueprint-test task-management --keep            # leave the graph in place to inspect it
+```
+
+Teardown is the default and runs even if an assertion fails. It is **created-only** — a pre-apply
+snapshot means it never deletes a schema or AccessProfile that already existed, so it's safe to point at
+a shared staging tenant. (It does **not** delete the app-context: that's idempotent and reused.) Exit
+`0` = applied + every assertion passed; `1` = an assertion failed or apply errored; `2` = no credential,
+or the blueprint asked for control-plane scope (the same gate `validate` enforces). Run this before you
+ship a blueprint — it catches an unusable or mis-scoped credential that the offline checks can't.
+
+## The format, field by field
+
+```yaml
+name: my-thing          # stable id + idempotency key. Re-running NEVER duplicates.
+version: 1.0.0
+description: One line describing what this blueprint provisions.
+contextId: mcp          # 3-31 chars, lowercase-start. The app-context the key binds to.
+
+schemas:
+  - typeName: thing   # immutable after first apply
+    displayName: Thing
+    indexMode: HYBRID    # HYBRID (default) | SEMANTIC | TEXT
+    fields:
+      - fieldId: title
+        fieldType: string       # string | number | boolean | date | enum | array | object | reference
+        required: true
+        searchable: true        # contributes to full-text + semantic search
+        filterable: false       # available as a query filter
+        validation: { minLength: 1, maxLength: 200 }   # server-enforced (ValidationRules)
+        renderHints: { label: Title, widget: text, order: 1, displayField: true }   # UI hints (displayField = the headline column)
+      - fieldId: externalId
+        fieldType: string
+        required: true
+    lookupFields: [title]        # extra O(1) exact-match lookup indexes (max 10);
+                                 # object form { fieldName, unique?, rangeEnabled?,
+                                 # sortBy?, allowOverflow? } for constraints/range.
+                                 # externalId has a built-in finder — don't list it.
+    capabilities: { auditHistory: true }   # default true; surfaced for a self-documenting audit posture
+
+accessProfile:
+  allowedActions: [records:r, records:c, records:u, search:r, schemas:r]
+  # dataScope binds the key to specific owners. Include `null` to ALSO grant
+  # tenant-level (shared) records — without it the key sees ONLY the listed
+  # owners' records, not shared/seed data:
+  # dataScope: { orgId: [<org-uuid>, null] }
+
+servicePrincipal:
+  externalId: my-thing-sp   # stable; the principal the profile + key bind to
+  displayName: My Thing
+
+seed:
+  - typeName: thing
+    externalId: seed-welcome   # stable → idempotent; re-apply converges
+    fields: { title: "Hello" }
+```
+
+YAML or JSON are both accepted (chosen by extension). The bundled library is
+authored in TypeScript; YAML is the authoring affordance for your own.
+
+### Choosing lookup indexes — a permanent decision
+
+`lookupFields` are how you reach records *directly* — by exact value, by an
+ordered range, by prefix — without running a search. The shape you give each one
+is **migration-locked**: once a schema is live, you cannot change a lookup field's
+index shape, *even by removing and re-adding the field* (the platform answers
+"use a new field name for different range behavior"). So decide deliberately,
+before customers build on the schema. Three knobs, each permanent:
+
+- **Equality vs. `rangeEnabled`.** Default is **equality** — exact match, and the
+  right choice for ids, foreign keys, status enums, and categories (you want
+  "all records with `status = new`", not a range of statuses). Set
+  **`rangeEnabled: true`** only for values you query as an *order* — dates,
+  sequence numbers, scores, versions — to get `from`/`to`/`prefix` queries
+  ("created in 2026-06", "due this week"). Range lookups are billed at the
+  range-index rate.
+  - *Watch the ordering:* range/prefix order is **lexical**. ISO-8601 dates sort
+    chronologically (safe). An ordinal **enum** like `priority: low|…|urgent`
+    sorts alphabetically (`high < low < medium < urgent`) — **not** by severity —
+    so leave ordinal enums as equality, or model them as numbers.
+
+- **The 7-slot equality budget.** Each schema has **7 fast equality-lookup
+  slots**. Equality lookups consume them in declaration order; the ownership ids
+  and `externalId` ride their own first-class slots and do **not** count.
+  `rangeEnabled` lookups use a relationship row instead of a slot, so they don't
+  count against the 7 either. An 8th equality lookup is **rejected** unless you
+  set `allowOverflow: true` on it, which accepts a higher-cost secondary index.
+  Keep equality lookups lean.
+
+- **`sortBy` — the order results come back in.** For an *equality* lookup,
+  `sortBy` sets the listing order: `createdAt` (default), `lastUpdated`, or a
+  declared field. *Trap:* sorting by an **optional** payload field silently drops
+  records that don't have it from that lookup — and it's locked. Use `createdAt`/
+  `lastUpdated` (always present) unless every record is guaranteed to carry the
+  field.
+
+**Sensitive fields can still be looked up — by exact match only.** A
+`sensitive` field is HMAC'd into a per-tenant **blind index**, so you *can* list
+it in `lookupFields` for exact find-by-value (e.g. find an intake by client name)
+without the value ever being stored in the clear or entering the search index. A
+blind hash is not orderable, so a sensitive lookup **cannot** be `rangeEnabled`,
+and no lookup's `sortBy` may name a sensitive field (the platform rejects both).
+
+### Reference fields — typed links between record types
+
+A `reference` field is a foreign key to another record. It needs **both** the
+target type and the surface it lives on (the same `typeName` can exist on more
+than one surface, so the surface disambiguates which lookup resolves the link):
+
+```yaml
+- fieldId: establishedByDecision
+  fieldType: reference
+  targetTypeName: decision      # the typeName it points at
+  targetSurface: record         # record | document | user | org | client (REQUIRED)
+  targetField: externalId       # the target's UNIQUE lookup to match (defaults to externalId)
+  cardinality: one              # one (a single id) | many (an array of ids)
+```
+
+The link resolves within the same context, and the target must **exist when the
+referencing record is written** (write-time existence is enforced by default) —
+so if you seed a referencing record, seed its target first. To query "which X
+reference Y", add the reference field to `lookupFields` as an equality lookup
+(there is no reverse-reference index on this surface).
+
+### The scope gate — what you can and can't request
+
+The gate allows only **data-plane** resources:
+`records`, `schemas`, `search`, `documents`, `folders`, `inference`.
+Operations are `c|r|u|d`, combinable (`records:cru`), with a per-resource
+wildcard (`records:*`). Anything else — control-plane resources or the bare
+`*` — is rejected, and there is **intentionally no override flag**. This is
+*why* it's safe to apply a blueprint you didn't write: the binary is the trust
+boundary, not the file.
+
+### The idempotency contract
+
+Re-applying a blueprint **converges, never duplicates**, because everything has
+a stable id: `name` (the blueprint), `typeName` (schemas), the service
+principal's `externalId`, the per-machine key name, and each seed record's
+`externalId`. Bump `version` when you evolve a blueprint. (Note: schema
+`typeName` is immutable after first apply.)
+
+## Distribution
+
+- **Bundled** — reviewed, versioned blueprints shipped in the library
+  (`vectros blueprint list`). Apply by name: `--blueprint task-management`.
+- **Local / file** — your own, applied by path: `--blueprint ./my-thing.yaml`.
+  The "copy & own" path. Same scope gate, no new trust surface.
+
+Apache-2.0

package/CHANGELOG.md

@@ -0,0 +1,20 @@
+# Changelog
+
+All notable changes to `@vectros-ai/cli` are documented here.
+This project adheres to [Semantic Versioning](https://semver.org).
+
+## 0.5.0 — 2026-06-20
+
+Initial public release of the `vectros` provisioning CLI.
+
+### Added
+
+- `vectros bootstrap` — provision a least-privilege MCP credential (a scoped
+  `ssk_*` key plus its matching data-plane AccessProfile, and optionally a
+  blueprint) in one command, without your root key.
+- `vectros blueprint` — author and inspect blueprints offline (`init`,
+  `validate`, `plan`, `list`); no credentials required.
+- `vectros blueprint-test` — apply a blueprint to a live environment, assert it
+  provisioned a working credential, then tear it down.
+- PKCE browser login and a documented verb catalog. Every command supports
+  `--help`; the authoring loop is documented in `AUTHORING.md`.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Vectros
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,114 @@
+# @vectros-ai/cli
+
+The Vectros provisioning CLI — the `vectros` binary. Two command groups:
+
+- **`vectros bootstrap`** — provision a least-privilege MCP credential (+ optional blueprint).
+- **`vectros blueprint`** — author + inspect blueprints (`init` / `validate` / `plan` / `list`), creds-free.
+- **`vectros blueprint-test`** — apply a blueprint to a live env, assert it provisioned a working credential, then tear it down.
+
+```bash
+npx -y @vectros-ai/cli bootstrap          # provision a credential
+npx -y @vectros-ai/cli blueprint --help   # the authoring commands
+```
+
+Every command has `--help`. The authoring loop is documented in
+[AUTHORING.md](./AUTHORING.md).
+
+## `vectros bootstrap`
+
+Provisions a **least-privilege** Vectros credential for the
+[`@vectros-ai/mcp-server`](https://www.npmjs.com/package/@vectros-ai/mcp-server)
+in one command — **without your root key** and without manual admin-app steps.
+It:
+
+- mints a scoped key (`ssk_*`) for **this machine** (independently rotatable),
+- creates the matching AccessProfile — **data-plane only**,
+- optionally scaffolds a use-case **blueprint** (e.g. `task-management`: a
+  schema + seed data), and
+- safe-merges the `vectros` server entry into your MCP client config
+  (`claude_desktop_config.json` — Claude Desktop, Cursor, Cline), backing up
+  the original first. Pass `--client code` to target **Claude Code** instead:
+  it merges the project `.mcp.json` and prints the equivalent `claude mcp add`
+  command.
+
+```bash
+# Interactive — pick a blueprint (or a blank read-only credential), sign in once.
+npx -y @vectros-ai/cli bootstrap
+
+# Scripted / agent — token in the env, no prompts.
+VECTROS_BOOTSTRAP_TOKEN=… npx -y @vectros-ai/cli bootstrap \
+  --blueprint task-management --yes
+
+# Login once, then bootstrap unattended — no token needed; --yes reuses your
+# stored `vectros login` session.
+npx -y @vectros-ai/cli login
+npx -y @vectros-ai/cli bootstrap --blueprint task-management --yes
+
+# See every flag.
+npx -y @vectros-ai/cli bootstrap --help
+```
+
+Re-running is idempotent; `--rotate` revokes + re-mints just this machine's key.
+
+## `vectros blueprint` — authoring (creds-free)
+
+Author and inspect blueprints without an account. You'll run these repeatedly,
+so install once and drop the `npx` prefix (`npm i -g @vectros-ai/cli`, or prefix
+each command with `npx -y @vectros-ai/cli`). The inner loop:
+
+```bash
+vectros blueprint init my-thing                      # scaffold a commented YAML starter
+#   …edit ./my-thing.blueprint.yaml…
+vectros blueprint validate ./my-thing.blueprint.yaml # structural + scope-gate + lint
+vectros blueprint plan     ./my-thing.blueprint.yaml # preview what bootstrap would provision
+vectros bootstrap --blueprint ./my-thing.blueprint.yaml   # apply it
+```
+
+- `init` — write a starter (`--from <bundled>` copies an exemplar; `--out`, `--force`).
+- `validate` — structural parse → scope gate → linter. Accepts a file **or** a bundled name.
+- `plan` — validate, then a terraform-style preview; mints nothing.
+- `list` — the bundled library.
+
+Full guide: [AUTHORING.md](./AUTHORING.md). Format reference:
+[`@vectros-ai/blueprints`](https://www.npmjs.com/package/@vectros-ai/blueprints).
+
+## `vectros blueprint-test` — verify it actually provisions (creds-required)
+
+`validate`/`plan` check a blueprint statically; `blueprint-test` proves it
+end-to-end against a live environment. It **applies** the blueprint, **asserts**
+the result (the app-context + each schema are readable back, and the freshly
+minted `ssk_*` authenticates as a scoped key with the requested actions), then
+**tears down** what it created — schemas, the AccessProfile, seed records, and
+the key. Teardown is *created-only*: anything that already existed before the run
+is left untouched, so it's safe to point at a shared staging tenant.
+
+```bash
+# Apply → assert → teardown against staging (sign in first, or pass --token).
+vectros blueprint-test ./my-thing.blueprint.yaml --env staging
+
+# Leave the provisioned graph in place to inspect it.
+vectros blueprint-test task-management --keep
+```
+
+Exit `0` = applied and every assertion passed; `1` = an assertion failed or apply
+errored; `2` = no credential, or the blueprint requested control-plane scope.
+The app-context is intentionally **not** deleted (it's idempotent and reused).
+
+## The scope gate (the trust boundary)
+
+Blueprints are **untrusted input** (agent- or community-authored) and the
+CLI runs under an elevated ephemeral bridge token. So the trust boundary is
+**this binary, not the blueprint**: a hardcoded **scope gate** bounds every
+mint to a data-plane allowlist (`records` / `schemas` / `search` / `documents`
+/ `folders` / `inference`). Any control-plane scope (keys / profiles / users /
+billing / admin) or `*` wildcard **hard-rejects** — the CLI mints nothing and
+exits non-zero. There is intentionally **no override flag**.
+
+## See also
+
+- [`@vectros-ai/mcp-server`](https://www.npmjs.com/package/@vectros-ai/mcp-server) — the runtime this CLI provisions for.
+- [`@vectros-ai/blueprints`](https://www.npmjs.com/package/@vectros-ai/blueprints) — the curated use-case library the CLI applies.
+
+## License
+
+Apache-2.0. See the LICENSE file.