@vitrinka/cli 5.23.0 → 5.25.0
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 +62 -0
- package/package.json +7 -7
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,68 @@
|
|
|
3
3
|
`vitrinka update` prints the sections newer than your previous version
|
|
4
4
|
after updating — keep entries short and user-facing.
|
|
5
5
|
|
|
6
|
+
## 5.25.0
|
|
7
|
+
|
|
8
|
+
**doc.json speaks the board's vocabulary.** A document is now a doc
|
|
9
|
+
element — `{"kind": "doc", "payload": {title, …, "elements": [...]}}` —
|
|
10
|
+
and every child is the same `{kind, payload}` a board composes: `md` for
|
|
11
|
+
prose, `source` for code, `cols` with keyed rows for tables, `elements`
|
|
12
|
+
inside sections. `vitrinka board push` rewrites a legacy `{meta, blocks}`
|
|
13
|
+
doc.json (and its pages) to the new shape on disk before it uploads; the
|
|
14
|
+
server still converts the old shape for this release and warns, and the
|
|
15
|
+
next release refuses it. kit-3's `Table`, `Prose`, `Code` and `Compare`
|
|
16
|
+
take the element names too; the old ones keep working.
|
|
17
|
+
|
|
18
|
+
**A `--json` field typo never writes twice.** Asking a write verb for a
|
|
19
|
+
field it does not return (`vitrinka task create … --json=id,key`) used to
|
|
20
|
+
fail after the task was filed, with a fix that filed it again. Once a
|
|
21
|
+
write has landed, a missing field is an `unknown_field` warning on the
|
|
22
|
+
successful answer, listing the fields that exist; before the write it is
|
|
23
|
+
still refused with the corrected call.
|
|
24
|
+
|
|
25
|
+
**Eve can judge a review run.** `/vitrinka:review … eve` plans a run for
|
|
26
|
+
Eve the way a session's own review does: Eve judges each planned screen
|
|
27
|
+
or crop once, skips reused and duplicate screens, and fills the same
|
|
28
|
+
coverage receipt.
|
|
29
|
+
|
|
30
|
+
**A board in another workspace is named, never "no work".** `vitrinka
|
|
31
|
+
work` on a board slug that lives in another workspace answers the
|
|
32
|
+
`<workspace>/<slug>` spelling that reaches it instead of reporting an
|
|
33
|
+
empty queue.
|
|
34
|
+
|
|
35
|
+
## 5.24.0
|
|
36
|
+
|
|
37
|
+
**Reviews read each screen once.** `vitrinka review plan <board>…`
|
|
38
|
+
(`review_plan` for agents) plans a review over your boards: the latest
|
|
39
|
+
capture pass by default, capture gaps left out, exact duplicates judged
|
|
40
|
+
once, near-duplicates as a crop of what changed, and screens already
|
|
41
|
+
judged under the same rubric reused — on a few labelled sheets instead
|
|
42
|
+
of one image per screen. A host that cannot see images is stopped after
|
|
43
|
+
the first sheet, and the run's receipt says what was inspected, reused or
|
|
44
|
+
skipped. `--checklist` adds your own checks; `--full` re-judges
|
|
45
|
+
everything.
|
|
46
|
+
|
|
47
|
+
**Pick who judges your reviews.** `vitrinka config reviewer codex` judges
|
|
48
|
+
screens on the Codex sidekick, `self` (the default) in the session that
|
|
49
|
+
runs the review; the session start names the lane when it is not the
|
|
50
|
+
default.
|
|
51
|
+
|
|
52
|
+
**`vitrinka update` refreshes a slow Claude Code.** When `claude
|
|
53
|
+
--version` (or `codex --version`) took more than three seconds — a busy
|
|
54
|
+
computer is enough — update printed "claude (absent)" and skipped the
|
|
55
|
+
plugin refresh without a word. Only a CLI missing from your PATH counts
|
|
56
|
+
as absent now: a slow one is refreshed, and a refresh that fails says why.
|
|
57
|
+
|
|
58
|
+
**A deleted artifact stays deleted.** `vitrinka board push` to an
|
|
59
|
+
artifact someone deleted is refused with `artifact_deleted` and a link to
|
|
60
|
+
its page, where Restore brings it back. `--revive` publishes it again on
|
|
61
|
+
the same page instead.
|
|
62
|
+
|
|
63
|
+
**Ticking one step keeps the rest.** A checklist written to a task
|
|
64
|
+
(`vitrinka task field set`, an agent's `update`) now merges by item: send
|
|
65
|
+
only the step you tick and the other steps and gates stay. `--replace`
|
|
66
|
+
writes the whole list, the way to drop, rename or reorder items.
|
|
67
|
+
|
|
6
68
|
## 5.23.0
|
|
7
69
|
|
|
8
70
|
**Claude Code stays signed in to vitrinka.** `vitrinka update` and
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vitrinka/cli",
|
|
3
|
-
"version": "5.
|
|
3
|
+
"version": "5.25.0",
|
|
4
4
|
"description": "vitrinka CLI — capture and publish artifact sets, drive the annotation-board work queue. Thin npm launcher for the single-binary Go CLI.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"vitrinka": "bin/vitrinka.js"
|
|
@@ -15,12 +15,12 @@
|
|
|
15
15
|
"node": ">=18"
|
|
16
16
|
},
|
|
17
17
|
"optionalDependencies": {
|
|
18
|
-
"@vitrinka/cli-darwin-arm64": "5.
|
|
19
|
-
"@vitrinka/cli-darwin-x64": "5.
|
|
20
|
-
"@vitrinka/cli-linux-arm64": "5.
|
|
21
|
-
"@vitrinka/cli-linux-x64": "5.
|
|
22
|
-
"@vitrinka/cli-win32-arm64": "5.
|
|
23
|
-
"@vitrinka/cli-win32-x64": "5.
|
|
18
|
+
"@vitrinka/cli-darwin-arm64": "5.25.0",
|
|
19
|
+
"@vitrinka/cli-darwin-x64": "5.25.0",
|
|
20
|
+
"@vitrinka/cli-linux-arm64": "5.25.0",
|
|
21
|
+
"@vitrinka/cli-linux-x64": "5.25.0",
|
|
22
|
+
"@vitrinka/cli-win32-arm64": "5.25.0",
|
|
23
|
+
"@vitrinka/cli-win32-x64": "5.25.0"
|
|
24
24
|
},
|
|
25
25
|
"keywords": [
|
|
26
26
|
"vitrinka",
|