@vitrinka/cli 5.3.0 → 5.4.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.
Files changed (2) hide show
  1. package/CHANGELOG.md +35 -0
  2. package/package.json +7 -7
package/CHANGELOG.md CHANGED
@@ -3,6 +3,41 @@
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.4.0
7
+
8
+ **Breaking: the old `<verb>_<kind>` tool names are gone.** `list_tasks`,
9
+ `get_task`, `create_board`, `get_brief`, `list_work`, `get_session` and every
10
+ other name the six generic verbs absorbed in 5.3.0 no longer answer; the call
11
+ is `list · get · create · update · delete · search {kind: "<kind>", …}` —
12
+ the kind is the old name's tail, singular for list and search (`list_tasks`
13
+ → `list {kind: "task"}`, `get_brief` → `get {kind: "brief"}`, `list_work` →
14
+ `list {kind: "work"}`). An old name answers a one-line rename hint, nothing
15
+ else. Per-kind contracts: `docs {topic: "kind:<kind>"}`. `update_cards`,
16
+ `get_card_image`, `get_templates` and `search` keep their names.
17
+
18
+ **The catalogue lost weight.** Argument prose moved out of `tools/list` into
19
+ docs topics, so a registration pays for the tools it can call, not for their
20
+ manuals. A new `rare` module holds the doors a session almost never needs
21
+ (`transfer_project`, `merge_project`, `mark_deploy`, `promote_meeting`,
22
+ `rename_set`, `review_judge*`, `review_stats`, `review_job`,
23
+ `meeting_notes`, `save_template`, `dry_run_rule`, `edit_journey_node`,
24
+ `set_preferences`, `favorite`, `unfavorite`, `my_favorites`,
25
+ `retract_questions`, `board_working`, `request_review`) — never listed by
26
+ default; opt in on the registration's `/mcp` URL with
27
+ `?modules=core,pm,qa,me,rare`. `usage` joins `select`, `jq` and `budget` as
28
+ a universal argument. `vitrinka doctor` prints the tool count the server
29
+ advertises to this registration.
30
+
31
+ **A bare task id is refused where it is ambiguous.** On an organisation-wide
32
+ grant that spans more than one workspace, an id-only tool on the root
33
+ `/mcp` door no longer guesses: a bare `{id: 42}` answers `spell it
34
+ <workspace>/<id>`. A `project` argument that pins the workspace, the
35
+ `/w/<slug>/mcp` door and the `<workspace>/<id>` spelling all work as before.
36
+
37
+ The contract date moves to 2026-09-15 — served by `/api/v1/version`, stamped
38
+ in every skill and in the kit export. Every skill now spells the generic
39
+ verbs, and the ones that lean on a `rare` tool say so.
40
+
6
41
  ## 5.3.0
7
42
 
8
43
  **Skills went on a token diet; the MCP refuses to dump.** Every MCP tool
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vitrinka/cli",
3
- "version": "5.3.0",
3
+ "version": "5.4.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.3.0",
19
- "@vitrinka/cli-darwin-x64": "5.3.0",
20
- "@vitrinka/cli-linux-arm64": "5.3.0",
21
- "@vitrinka/cli-linux-x64": "5.3.0",
22
- "@vitrinka/cli-win32-arm64": "5.3.0",
23
- "@vitrinka/cli-win32-x64": "5.3.0"
18
+ "@vitrinka/cli-darwin-arm64": "5.4.0",
19
+ "@vitrinka/cli-darwin-x64": "5.4.0",
20
+ "@vitrinka/cli-linux-arm64": "5.4.0",
21
+ "@vitrinka/cli-linux-x64": "5.4.0",
22
+ "@vitrinka/cli-win32-arm64": "5.4.0",
23
+ "@vitrinka/cli-win32-x64": "5.4.0"
24
24
  },
25
25
  "keywords": [
26
26
  "vitrinka",