@vitrinka/cli 5.2.0 → 5.4.0

package/CHANGELOG.md

@@ -3,6 +3,86 @@
 `vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 5.4.0
+
+**Breaking: the old `<verb>_<kind>` tool names are gone.** `list_tasks`,
+`get_task`, `create_board`, `get_brief`, `list_work`, `get_session` and every
+other name the six generic verbs absorbed in 5.3.0 no longer answer; the call
+is `list · get · create · update · delete · search {kind: "<kind>", …}` —
+the kind is the old name's tail, singular for list and search (`list_tasks`
+→ `list {kind: "task"}`, `get_brief` → `get {kind: "brief"}`, `list_work` →
+`list {kind: "work"}`). An old name answers a one-line rename hint, nothing
+else. Per-kind contracts: `docs {topic: "kind:<kind>"}`. `update_cards`,
+`get_card_image`, `get_templates` and `search` keep their names.
+
+**The catalogue lost weight.** Argument prose moved out of `tools/list` into
+docs topics, so a registration pays for the tools it can call, not for their
+manuals. A new `rare` module holds the doors a session almost never needs
+(`transfer_project`, `merge_project`, `mark_deploy`, `promote_meeting`,
+`rename_set`, `review_judge*`, `review_stats`, `review_job`,
+`meeting_notes`, `save_template`, `dry_run_rule`, `edit_journey_node`,
+`set_preferences`, `favorite`, `unfavorite`, `my_favorites`,
+`retract_questions`, `board_working`, `request_review`) — never listed by
+default; opt in on the registration's `/mcp` URL with
+`?modules=core,pm,qa,me,rare`. `usage` joins `select`, `jq` and `budget` as
+a universal argument. `vitrinka doctor` prints the tool count the server
+advertises to this registration.
+
+**A bare task id is refused where it is ambiguous.** On an organisation-wide
+grant that spans more than one workspace, an id-only tool on the root
+`/mcp` door no longer guesses: a bare `{id: 42}` answers `spell it
+<workspace>/<id>`. A `project` argument that pins the workspace, the
+`/w/<slug>/mcp` door and the `<workspace>/<id>` spelling all work as before.
+
+The contract date moves to 2026-09-15 — served by `/api/v1/version`, stamped
+in every skill and in the kit export. Every skill now spells the generic
+verbs, and the ones that lean on a `rare` tool say so.
+
+## 5.3.0
+
+**Skills went on a token diet; the MCP refuses to dump.** Every MCP tool
+takes `select`, `jq` and `budget`; a reply above the budget (8k tokens by
+default, 30k ceiling) comes back as an `over_budget` envelope naming the
+tool's narrowing arguments instead of the dump. The 52 `<verb>_<kind>` tools
+collapsed behind six generic verbs (`list · get · create · update · delete ·
+search {kind}`; the old names still answer, flagged deprecated), `tools/list`
+is scoped to the project's modules, and PM reads ride compact rows. The
+plugin ships 15 skills instead of 21: the five personal skills are ONE
+manual-only `me` skill, `answers` and `annotations` dissolved into the MCP
+instructions, and every SKILL.md is a trigger plus contracts.
+
+**Procedure moved to the server.** The step choreography the publish,
+brainstorming and sessions skills used to carry is served as guide pages:
+`vitrinka docs guide:publish-capture`, `guide:brainstorm-flow`,
+`guide:sessions-pipeline` (MCP `docs {topic: "guide:<name>"}`, index
+`docs {family: "guide"}`). A wording fix is a deploy, never a plugin update.
+
+`--json` envelopes of `task pickup`, `task start`, `task spot`, `task
+handback`, `qa run` and `qa usertest start · case · verdict` now carry
+`next[]` — the command to run next, executable as printed. `vitrinka doctor`
+reports MCP replies that ran over budget.
+
+MCP: `set_board_meta {archived: true}` retires a board (false restores it);
+a task `id` spelled as a numeric string (`"289"`) is accepted like the
+number; the `spot` and `hand_back` receipts name the parent task as a line
+instead of embedding its whole row.
+
+`vitrinka project merge <from> --into <to>` merges a project into another
+project of the same workspace: everything <from> owns moves — tasks with
+their ledger, comments and attachments, boards, sets, sessions, reports,
+releases, press editions and project memory — nothing is dropped (a clashing
+custom field is renamed `<key>_from_<from>`, a clashing set `<key>-from-<from>`,
+values kept), and the old
+name stays as an alias so every old link keeps working. Dry run by default;
+`--apply` writes, `--adopt --title "<epic>"` parents the moved root tasks
+under one new epic. `project merge-plan --into <to>` lists the strays a
+merge would sweep. `project fold` / `fold-plan` keep working as hidden
+aliases; `--adopt "<title>"` became `--adopt --title "<title>"`.
+
+`vitrinka task update <id> --project <slug>` moves one task with its whole
+subtree into another project; states, labels, fields, sprint and milestone
+map by key and missing keys are created in the target.
+
 ## 5.2.0
 
 **One sign-in ever on Claude Code.** Claude Code keeps a separate OAuth token

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vitrinka/cli",
-  "version": "5.2.0",
+  "version": "5.4.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.2.0",
-    "@vitrinka/cli-darwin-x64": "5.2.0",
-    "@vitrinka/cli-linux-arm64": "5.2.0",
-    "@vitrinka/cli-linux-x64": "5.2.0",
-    "@vitrinka/cli-win32-arm64": "5.2.0",
-    "@vitrinka/cli-win32-x64": "5.2.0"
+    "@vitrinka/cli-darwin-arm64": "5.4.0",
+    "@vitrinka/cli-darwin-x64": "5.4.0",
+    "@vitrinka/cli-linux-arm64": "5.4.0",
+    "@vitrinka/cli-linux-x64": "5.4.0",
+    "@vitrinka/cli-win32-arm64": "5.4.0",
+    "@vitrinka/cli-win32-x64": "5.4.0"
   },
   "keywords": [
     "vitrinka",