@vitrinka/cli 5.3.0 → 5.5.0

package/CHANGELOG.md

@@ -3,6 +3,87 @@
 `vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 5.5.0
+
+**Breaking: a hand-back files STEPS on the task, not a pile of child
+tasks.** `hand_back` / `vitrinka task handback` lands each `next` item as a
+step on the task's own checklist; a child task appears only when the item
+says `task: true` with a type, so an agent has to argue for a task and
+never for a step. New flags: `--step "name[::kind][::who-or-date][::when]"`
+and `--gate "name[::who][::when]"`; `--next` now means a child TASK. An
+`omitted` item starting with `Decide:` becomes a human gate that blocks
+Done. A step whose trigger is observable carries `when` in the todo grammar
+(`pr 12 merged`) and the server ticks it with evidence. A pickup leads with
+the task's open steps, then its children. ⚠️ An older `@vitrinka/cli`
+sending a raw `next` item as `{title, type}` with no `task` key now gets a
+422 telling it to set `task: true` — update before handing back.
+
+**The session-end auto-archive is gone.** `vitrinka qa session archive
+on|off|status` and the `SessionEnd` hook that uploaded a whole redacted
+transcript whenever a session naming a task ended no longer exist — every
+such session left a record nobody asked for, and the record buried the
+hand-back. Archiving a transcript is an explicit hand-off act:
+`vitrinka qa session archive <transcript.jsonl> --task <id>` when the work
+passes to a colleague, with the task labelled `eve-distill` so they open
+the digest. `vitrinka setup` strips the retired hook.
+
+**One SessionStart hook instead of three.** `vitrinka hook-context start`
+prints the run stamp with the pickup, the todo cue and the schedule cue in
+one process and one envelope; the cues fire only on a real start (Claude
+Code's `source` is `startup` or `clear`), so a resume or a compaction pays
+the stamp alone and needs no matcher. Timeouts are short (8 s start, 10 s
+task-end, 5 s stop, 5 s touch) and the Stop gate reads only the last 4 MiB
+of a transcript. `vitrinka setup` replaces the old `task`, `todo` and
+`schedule` rows in place; the old verbs still answer for machines that have
+not re-run setup.
+
+**NEXT is a work queue, not a menu.** The pickup skill works the task's open
+steps and then every child down the list until only rows a human must do
+remain — a decision the tree waits on is asked mid-flight, never filed and
+left; only the context window ends a sitting. Its mirror in the handoff
+skill: `next` holds only what the human must do, and work the agent can do
+is built before the hand-back.
+
+**Smaller:** the listen skill's ladder is served by the server
+(`docs {topic: "…"}`) instead of shipping as a file in the plugin, and the
+Claude plugin renders into its own kit subtree so an installed plugin cache
+holds nothing installable.
+
+## 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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vitrinka/cli",
-  "version": "5.3.0",
+  "version": "5.5.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.3.0",
-    "@vitrinka/cli-darwin-x64": "5.3.0",
-    "@vitrinka/cli-linux-arm64": "5.3.0",
-    "@vitrinka/cli-linux-x64": "5.3.0",
-    "@vitrinka/cli-win32-arm64": "5.3.0",
-    "@vitrinka/cli-win32-x64": "5.3.0"
+    "@vitrinka/cli-darwin-arm64": "5.5.0",
+    "@vitrinka/cli-darwin-x64": "5.5.0",
+    "@vitrinka/cli-linux-arm64": "5.5.0",
+    "@vitrinka/cli-linux-x64": "5.5.0",
+    "@vitrinka/cli-win32-arm64": "5.5.0",
+    "@vitrinka/cli-win32-x64": "5.5.0"
   },
   "keywords": [
     "vitrinka",