@vectros-ai/cli 0.6.1 → 0.6.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -3,6 +3,69 @@
3
3
  All notable changes to `@vectros-ai/cli` are documented here.
4
4
  This project adheres to [Semantic Versioning](https://semver.org).
5
5
 
6
+ ## 0.6.5 — 2026-07-01
7
+
8
+ ### Added
9
+
10
+ - **Find your own user id without hunting for it.** `vectros whoami` now shows
11
+ **`your user id`** (`usr_<...>`), and `vectros access grant`/`revoke`/`list`/`get`
12
+ accept **`--principal me`** as an alias for your own user — so joining yourself to
13
+ a context is a one-liner with no id lookup:
14
+ `vectros access grant --principal me --context <ctx> --role <role>`.
15
+ Resolution is client-side (your login's email matched against the tenant's users);
16
+ if it can't be resolved, `whoami` shows `—` and `--principal me` prints how to pass
17
+ the id explicitly (`vectros identity list --type user`).
18
+
19
+ ## 0.6.4 — 2026-06-29
20
+
21
+ ### Fixed
22
+
23
+ - **`vectros bootstrap` now propagates a changed schema on re-apply.** When you
24
+ re-run bootstrap against a context whose schema already exists, the CLI reconciles
25
+ the existing schema to your blueprint's current shape — additive fields, lookups,
26
+ render hints, and the `active` flag are applied — instead of silently keeping the
27
+ old shape. A migration-locked change (a lookup field's `rangeEnabled`/`sortBy`/
28
+ `sensitive`, or the schema `typeName`) is reported as a clear error rather than
29
+ being quietly ignored. A re-apply whose shape is unchanged is a no-op.
30
+
31
+ ### Changed
32
+
33
+ - Updated the bundled `@vectros-ai/sdk` to **0.31.0**, keeping the CLI aligned with
34
+ the current Vectros API. Create endpoints now report whether a resource was newly
35
+ created and accept an opt-in `upsert` to reconcile an existing one; the schema
36
+ reconcile above is built on it.
37
+
38
+ ## 0.6.3 — 2026-06-28
39
+
40
+ ### Changed
41
+
42
+ - Updated the bundled `@vectros-ai/blueprints` to **0.6.1**, which adds the
43
+ `agentic-sdlc` blueprint — a whole-SDLC system of record (nine schemas,
44
+ content vs structure, cross-surface knowledge graph). Now available by name:
45
+ `vectros bootstrap --blueprint agentic-sdlc`.
46
+
47
+ ## 0.6.2 — 2026-06-28
48
+
49
+ ### Added
50
+
51
+ - `vectros bootstrap --tenant test|live` (and the `--test` shorthand) — provision
52
+ the blueprint's credential against your **test** tenant for a dry run before
53
+ pointing real data at the same setup. The tenant rides the key (`ssk_test_*` vs
54
+ `ssk_live_*`), so the generated MCP/client config is otherwise identical.
55
+ Defaults to `live`.
56
+ - **Bootstrap now seeds documents, not just records.** A blueprint seed entry
57
+ declares its surface — `surface: record` (the default) or `surface: document`
58
+ (a text-ingested document with a `title` and `text`, plus optional structured
59
+ `fields`). A seed graph can span both surfaces: a record's `reference` can point
60
+ at a seeded document by `externalId` (and vice versa), so a blueprint that mixes
61
+ records and documents comes up as a live, linked graph at bootstrap. The plan
62
+ preview and `blueprint test` (apply + teardown) both handle the document surface.
63
+
64
+ ### Changed
65
+
66
+ - Updated the bundled `@vectros-ai/blueprints` to **0.6.0** (the surface-tagged
67
+ seed format above).
68
+
6
69
  ## 0.6.1 — 2026-06-27
7
70
 
8
71
  Maintenance — refreshed the bundled Vectros SDK to the current API surface.