@vectros-ai/cli 0.13.0 → 0.15.0

package/AUTHORING.md

@@ -78,7 +78,11 @@ 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).
+(`--yes` skips the prompt for CI/agents). ⚠️ **`--no-merge` is NOT a dry run** — it still
+mints/reconciles for real; it only changes where the resulting credential goes, printing the MCP
+config snippet to stdout instead of merging it into your client's config file. To preview without
+touching your account, stop at `blueprint plan` (offline) — `bootstrap`, with or without `--no-merge`,
+always applies.
 
 **Provisioning a production context — `--no-seed`.** A blueprint's `seed`
 records are illustrative sample data: handy for a getting-started or demo
@@ -120,7 +124,10 @@ contextId: mcp          # 3-31 chars, lowercase-start. The app-context the key b
 schemas:
   - typeName: thing   # immutable after first apply
     displayName: Thing
-    indexMode: HYBRID    # HYBRID (default) | SEMANTIC | TEXT
+    indexMode: HYBRID    # HYBRID | SEMANTIC | TEXT | NONE (store-only).
+                         # Omitting it does NOT mean HYBRID: a record schema with no
+                         # indexMode resolves to NONE, and a document schema with none
+                         # is rejected. Declare the mode you want.
     fields:
       - fieldId: title
         fieldType: string       # string | number | boolean | date | enum | array | object | reference
@@ -159,6 +166,20 @@ seed:
     # 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).
+
+issuers:
+  - issuerId: auth0-prod       # your slug; 3-31 chars, lowercase letter first
+    issuer: "https://your-tenant.us.auth0.com/"
+    jwksUri: "https://your-tenant.us.auth0.com/.well-known/jwks.json"
+    audience: "https://api.your-app.example.com"   # globally unique per (issuer, audience)
+    contextId: my-thing        # which app context an exchanged token targets
+    # Optional trusted third-party IdP issuers (BYO-IdP token exchange). Applied
+    # in the BOOTSTRAP-token phase, alongside app-context/service-principal
+    # creation — NOT the same phase as schemas/accessProfile/roles above (see
+    # BLUEPRINT_FIELD_PHASES, exported by @vectros-ai/blueprints). Registration
+    # is create-once: re-applying an already-registered issuerId leaves it
+    # unchanged — there's no update, so an edited jwksUri/audience on a live
+    # issuer won't take effect via re-apply.
 ```
 
 YAML or JSON are both accepted (chosen by extension). The bundled library is
@@ -277,7 +298,10 @@ reference Y", add the reference field to `lookupFields` as an equality lookup
 ### The scope gate — what you can and can't request
 
 The gate allows only **data-plane** resources:
-`records`, `schemas`, `search`, `documents`, `folders`, `inference`.
+`records`, `schemas`, `search`, `documents`, `folders`, `inference`, `entities`
+(per-namespace identity-entity CRUD — `org`/`client`/any namespace you
+registered — ownership-gated the same way as `records`; it grants no
+authority over the namespace *registry* itself, which stays root-key-only).
 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

package/CHANGELOG.md

@@ -3,6 +3,131 @@
 All notable changes to `@vectros-ai/cli` are documented here.
 This project adheres to [Semantic Versioning](https://semver.org).
 
+## 0.15.0
+
+### Added
+
+- **`bootstrap` can register trusted third-party IdP issuers via a blueprint's
+  new `issuers:` block** (requires `@vectros-ai/blueprints` 0.12.0+). Each entry
+  (`issuerId`, `issuer`, `jwksUri`, `audience`, `contextId`, optional `subClaim`/
+  `emailClaim`) is applied in the bootstrap-token phase — alongside app-context
+  and service-principal creation — using the same owner-only authority that
+  creates the app context itself, never an ordinary partner-grantable scope.
+  `vectros blueprint plan` names this phase explicitly in the preview.
+
+- **`vectros blueprint-test` now verifies a declared `issuers:` entry actually
+  registered and is readable back**, the same live-credential proof it already
+  gives schemas and roles. One limitation, surfaced explicitly in the run's
+  report rather than silently: the platform has no way to remove a registered
+  issuer yet, so (unlike every other resource `blueprint-test` provisions)
+  issuer registrations are not torn down after the test run.
+
+### Fixed
+
+- **`key rotate` no longer silently mints a second key when `--name` defaults
+  to `'default'` and the real key you meant to rotate is named something
+  else** (e.g. a `bootstrap`-minted key, which is never named `'default'`).
+  It now refuses when the default name matches no active key but another
+  active key already exists for the same principal/context, naming the
+  other key(s) so you can re-run with the right `--name` — or `--force-new`
+  to mint a new one alongside them anyway. Previously this minted an
+  unrelated key with no error or warning, leaving the original — possibly
+  the reason you were rotating — still active.
+
+- **`bootstrap --blueprint <file>` now accepts `--set name=value` / `--values
+  <file>`** for a file blueprint's declared `inputs:`, matching what `vectros
+  blueprint validate`/`plan` already supported. Previously there was no way
+  to apply a blueprint with a required, no-default input via `bootstrap` at
+  all — the flags simply didn't exist on that command. Supplying either flag
+  against a bundled or `--blank` blueprint (which have no `inputs:` to set)
+  is now a clear usage error rather than a silent no-op.
+
+- **The bootstrap scope gate no longer treats `entities` (identity-entity
+  CRUD — `org`/`client`/any namespace you registered) as control-plane.**
+  It's ordinary tenant data, ownership-gated the same way as `records` —
+  creating or reading an entity grants no additional access by itself. This
+  had blocked provisioning any blueprint role that manages its own
+  entities (e.g. a user creating their own org). The namespace *registry*
+  itself (registering a new namespace type) is unaffected and stays
+  root-key-only, correctly rejected by the gate as before.
+
+- **The displayed/stored environment (`whoami`, `keyring list`/`doctor`, `blueprint-test`'s
+  banner) now reflects the base URL a command actually resolved and sent requests to, not
+  a hidden flag default.** The two diverge whenever `VECTROS_API_BASE_URL`/`--base-url`
+  alone selects the environment (the common shape when targeting staging without also
+  passing `--env staging`) — previously this echoed the wrong environment label next to a
+  key or session that was actually minted/used against a different one.
+
+### Changed
+
+- **Dependency maintenance** — repinned the bundled `@vectros-ai/sdk` to `0.39.0` (the
+  trusted BYO-IdP issuer registry and RFC 8693 token exchange, `exists-by-email`, and the
+  scoped-token TTL cap narrowed to 1 hour). The CLI bundles the SDK into its published
+  binary, so this is a rebuild against its current version.
+
+## 0.14.0
+
+### Security
+
+- **`bootstrap` no longer stores your minted `ssk_*` in plaintext.** The key
+  goes to this machine's OS credential store (or an encrypted file where none
+  is available); your MCP client config references it by alias only
+  (`VECTROS_KEYRING_ALIAS`), never the raw secret. **Breaking:** a config
+  merged by an older CLI keeps working, but a fresh `bootstrap` run now
+  produces the alias-only shape — if you scripted against the printed
+  snippet's `VECTROS_API_KEY` field, it's `VECTROS_KEYRING_ALIAS` now.
+
+- **`--print` is renamed `--no-merge`, with no back-compat alias.** It was
+  never a dry run — it always applies for real and only changes where the
+  result goes. It still applies; it just skips writing your client's config
+  file. For a true preview, use `blueprint plan`.
+
+### Added
+
+- **`key issue --to-keyring` and `key rotate --to-keyring` store the minted secret
+  instead of printing it.** Until now the mint verbs could only *emit* a key, so on
+  a desktop the only place to put it was the MCP client's config file, in plaintext.
+  `--to-keyring` writes it to this machine's OS credential store where one is in use,
+  and to the encrypted file under `~/.vectros/secrets` otherwise — telling you which
+  of the two took it either way, because only one of them is login-gated. The key is
+  never printed to a terminal, a pipe or a transcript. Anything that resolves a
+  credential through `vectros keyring show --format raw` — the MCP server included
+  — then reads it with no `VECTROS_API_KEY` set anywhere.
+
+  `--alias <name>` names the entry (default: the context id) and `--no-activate`
+  stores it without making it the active identity. Emitting stays the **default**:
+  it is the right behaviour for a headless server, where a secrets manager
+  distributes the key and nothing should persist it locally. The two destinations
+  are mutually exclusive — `--to-keyring` with `--format raw|env|json` is rejected
+  before anything is minted, rather than storing the key and printing it anyway.
+
+  `rotate --to-keyring` proves the store will accept a write *before* it revokes
+  the old key, so a machine that cannot hold a secret fails with your existing
+  credential intact.
+
+### Fixed
+
+- **`bootstrap --plan` no longer claims `HYBRID` for a schema that declares no
+  `indexMode`.** The plan rendered an absent mode as `HYBRID`, but nothing
+  substitutes that default — the value is forwarded untouched, and the platform
+  then resolves an absent mode to `NONE` (store-only, never searchable) on a record
+  schema, and rejects a document schema that declares none. So the plan promised a
+  searchable type and the apply produced a store-only one, or previewed a request
+  the API would refuse. The plan now names the real outcome in both cases.
+
+### Changed
+
+- **A blueprint may now declare `indexMode: NONE`** (store-only: kept and looked up, never
+  searchable). The mode has always been accepted by the platform, and `bootstrap`/`validate`/`plan`
+  rejected it earlier than that — structural validation runs against this CLI's own bundled copy of
+  the blueprint format, which predated the value. That copy now carries it, so a blueprint declaring
+  `NONE` validates and applies. This governs blueprints loaded **from a file** as much as bundled
+  ones: both funnel through the same structural parse.
+
+- **`blueprint init` scaffold and `AUTHORING.md`** document the full `indexMode` set including
+  `NONE`, and warn that omitting the field does not mean `HYBRID` — a record schema with no mode of
+  its own resolves to `NONE`, and a document schema with none is rejected.
+
 ## 0.13.0
 
 ### Added

package/README.md

@@ -115,7 +115,9 @@ The app-context is intentionally **not** deleted (it's idempotent and reused).
 A machine can hold several Vectros identities (one per context or principal).
 The keyring stores them as named entries plus one **active** pointer, so you can
 switch between them without re-issuing keys. `vectros join <context>` adds an
-entry and activates it; `vectros switch <alias>` flips the active one.
+entry and activates it; `vectros key issue`/`key rotate` add one when passed
+`--to-keyring` (which stores the new secret instead of printing it); `vectros switch
+<alias>` flips the active one.
 
 ```bash
 vectros keyring list                 # the entries; * marks the active one
@@ -186,9 +188,10 @@ 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**.
+/ `folders` / `inference` / `entities`). Any control-plane scope (keys /
+profiles / users / billing / admin / namespaces) or `*` wildcard
+**hard-rejects** — the CLI mints nothing and exits non-zero. There is
+intentionally **no override flag**.
 
 ## Rate limits