@vitrinka/cli 5.24.0 → 5.26.0

package/CHANGELOG.md

@@ -3,6 +3,56 @@
 `vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 5.26.0
+
+**Recorder and report keys from the terminal.** `vitrinka workspace token
+create --project <p> --origin <url>… --secret-only` requests a recorder (or
+`--kind report`) key. The request opens in your browser, where you approve
+exactly that key, and then its secret prints once, bare, ready to pipe into a
+vault. No flag skips the browser step, and no other kind of token can be
+requested. `--no-wait` files the request and hands back `workspace token
+claim <code>`; `workspace token list` and `revoke` cover the rest, and every
+request, approval and denial is in the audit log.
+
+**Citations are their own noun.** `vitrinka cite <vitr:kind/code…>`
+reads what each durable citation into vitrinka points at now: current,
+replaced, changed or moved.
+
+**Every board flag takes `<workspace>/<slug>`**, not only `board compose`,
+and `board compose` retries never apply a batch twice.
+
+**Opt-in plugins reach Codex** as bundles of their own, and every plugin
+command is named by the plugin that ships it.
+
+## 5.25.0
+
+**doc.json speaks the board's vocabulary.** A document is now a doc
+element — `{"kind": "doc", "payload": {title, …, "elements": [...]}}` —
+and every child is the same `{kind, payload}` a board composes: `md` for
+prose, `source` for code, `cols` with keyed rows for tables, `elements`
+inside sections. `vitrinka board push` rewrites a legacy `{meta, blocks}`
+doc.json (and its pages) to the new shape on disk before it uploads; the
+server still converts the old shape for this release and warns, and the
+next release refuses it. kit-3's `Table`, `Prose`, `Code` and `Compare`
+take the element names too; the old ones keep working.
+
+**A `--json` field typo never writes twice.** Asking a write verb for a
+field it does not return (`vitrinka task create … --json=id,key`) used to
+fail after the task was filed, with a fix that filed it again. Once a
+write has landed, a missing field is an `unknown_field` warning on the
+successful answer, listing the fields that exist; before the write it is
+still refused with the corrected call.
+
+**Eve can judge a review run.** `/vitrinka-qa:review … eve` plans a run for
+Eve the way a session's own review does: Eve judges each planned screen
+or crop once, skips reused and duplicate screens, and fills the same
+coverage receipt.
+
+**A board in another workspace is named, never "no work".** `vitrinka
+work` on a board slug that lives in another workspace answers the
+`<workspace>/<slug>` spelling that reaches it instead of reporting an
+empty queue.
+
 ## 5.24.0
 
 **Reviews read each screen once.** `vitrinka review plan <board>…`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vitrinka/cli",
-  "version": "5.24.0",
+  "version": "5.26.0",
   "description": "vitrinka CLI — capture and publish artifact sets, drive the annotation-board work queue. Thin npm launcher for the single-binary Go CLI.",
   "bin": {
     "vitrinka": "bin/vitrinka.js"
@@ -15,12 +15,12 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@vitrinka/cli-darwin-arm64": "5.24.0",
-    "@vitrinka/cli-darwin-x64": "5.24.0",
-    "@vitrinka/cli-linux-arm64": "5.24.0",
-    "@vitrinka/cli-linux-x64": "5.24.0",
-    "@vitrinka/cli-win32-arm64": "5.24.0",
-    "@vitrinka/cli-win32-x64": "5.24.0"
+    "@vitrinka/cli-darwin-arm64": "5.26.0",
+    "@vitrinka/cli-darwin-x64": "5.26.0",
+    "@vitrinka/cli-linux-arm64": "5.26.0",
+    "@vitrinka/cli-linux-x64": "5.26.0",
+    "@vitrinka/cli-win32-arm64": "5.26.0",
+    "@vitrinka/cli-win32-x64": "5.26.0"
   },
   "keywords": [
     "vitrinka",