@vectros-ai/cli 0.6.8 → 0.9.0

package/CHANGELOG.md

@@ -3,6 +3,91 @@
 All notable changes to `@vectros-ai/cli` are documented here.
 This project adheres to [Semantic Versioning](https://semver.org).
 
+## 0.9.0
+
+### Added
+
+- **Ownership scopes across the provisioning verbs.** `role create` gains
+  `--data-scope <json>` to confine a role's clause to owned data (e.g.
+  `'{"userId":["${{ self.userId }}"]}'` for per-request "records I own", or
+  `'{"scope:org":["<orgId>", null]}'` for one org's data plus scope-less records).
+  `access grant` and `vectros join` gain `--org <orgId>` (and `access grant` the
+  general `--identity-overrides <json>`), placing the principal under an
+  organization for the context so its key can write org/team-scoped data — a
+  credential can only stamp ownership its identity carries.
+- **`vectros access explain`** — renders what a principal's binding actually
+  grants: the clause list plus a concrete access matrix (your private records, a
+  teammate's shared records, another team's, scope-less content, …) evaluated
+  under the documented matching rules — per-dimension match, AND across a
+  clause's keys, UNION across clauses, and the `null` opt-in for scope-less
+  items. Answers "who can see what?" before any data exists, and catches the
+  classic one-clause mis-authoring that silently denies teammates' shared
+  records.
+- **`vectros join` + the multi-principal keyring** — `vectros join <context>
+  (--role <r> | --actions <csv>) [--as me|usr_<id>] [--alias <name>]` enrolls a
+  principal in a context in one step: it grants the role, issues a scoped key,
+  and stores that key as a named keyring entry, then makes it the active
+  identity. Several identities can now live side by side. `vectros switch
+  <alias>` (or `vectros keyring use <alias>`) flips the active one; `vectros
+  keyring list` shows them all with the active one marked; `vectros keyring show
+  [--format env|raw]` reveals the active key (e.g. `--format env` prints
+  `VECTROS_API_KEY=…` to export into the MCP server); `vectros keyring remove
+  <alias>` drops one. Re-joining an alias whose key is still held is idempotent
+  (it re-activates without churning the key); it only rotates when the local
+  secret is missing.
+- **Keys are encrypted at rest** — keyring secrets are stored AES-256-GCM
+  encrypted under a machine-derived key, rather than in plaintext. (An OS-native
+  secret store is a planned follow-up for login/hardware-gated protection.)
+- **Bundled blueprints updated to `0.7.0`** — `agentic-sdlc` gains governed agent
+  memory (enroll with `vectros join agentic-sdlc --role member`), and the blueprint
+  format gains `accessProfile.identityOverrides` + per-seed `scopes`, which
+  `bootstrap`/`blueprint-test` apply. **Full detail in the `@vectros-ai/blueprints`
+  changelog** — this entry is an overview; the schema, role, and format specifics
+  live there.
+
+## 0.8.1 — 2026-07-10
+
+### Changed
+
+- **Dependency maintenance** — repinned the bundled `@vectros-ai/sdk` to `0.34.0`
+  (additive `scopes` read-back on record/document/folder responses, plus webhooks).
+  The CLI bundles the SDK into its published binary, so this is a rebuild against the
+  current SDK; no CLI behavior changes.
+
+## 0.8.0
+
+### Added
+
+- **Blueprint identity resolution** — a blueprint can now declare a top-level
+  `identities:` block (tenant-wide principals: `user`, `org`, or `client`) and reference
+  them with `${{ identities.<name> }}` tokens in ownership and data-scope positions
+  (schema `userId`/`orgId`/`clientId`, access-profile and role `dataScope`). At apply
+  time (`vectros bootstrap` / `vectros blueprint-test`) each declared identity is ensured
+  (idempotent by `externalId`) and every token is substituted with the principal's
+  resolved id — so a blueprint can provision data owned by, or a credential scoped to,
+  specific principals. `vectros blueprint validate` / `plan` accept an identity-using
+  blueprint offline (linting that every reference is declared) and defer resolution to
+  apply time; the plan preview discloses the identities that will be ensured. Declared
+  identities are tenant-global and are never removed by `blueprint-test` teardown.
+
+## 0.7.0 — 2026-07-08
+
+### Added
+
+- **`--tenant test|live` on `context create`, `context list`, and `context get`** —
+  pick the tenant a context is created in / read from (default `live`), mirroring the
+  flag `context destroy` and `blueprint-test` already carried. Previously these verbs
+  always targeted the live tenant, so a context on the test tenant could neither be
+  created, read, nor listed from the CLI.
+- **`vectros context destroy <contextId>`** — permanently destroy an app context and
+  everything in it (records, documents, folders, schemas, roles, access profiles; the
+  context's scoped keys are revoked up front). The teardown is irreversible and runs
+  asynchronously on the server (the context reports `purging` until the drain
+  completes). Two safety rails: interactively you must re-type the context id to
+  confirm; `--force` skips the prompt and is required when stdin is not a terminal.
+  `--tenant test|live` picks the tenant the context lives in (default `live`).
+  Authenticates as the account owner — no root API key required.
+
 ## 0.6.8 — 2026-07-05
 
 ### Changed

package/README.md

@@ -130,6 +130,13 @@ after the window resets, or split a large blueprint. See the
 - [`@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.
 
+## Security & trust
+
+Vectros enforces per-customer, fail-closed isolation and least-privilege scoped keys, with a
+tamper-evident audit and version history. Customer-facing surfaces are hardened through extensive
+adversarial security review. For the full trust posture, drawn plainly with its boundaries, see the
+[compliance and trust guide](https://docs.vectros.ai/guides/operations-trust/compliance).
+
 ## License
 
 Apache-2.0. See the LICENSE file.