@vitrinka/cli 5.4.0 → 5.5.1

package/CHANGELOG.md

@@ -3,6 +3,69 @@
 `vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 5.5.1
+
+**The 5.5.0 hook ceilings actually arrive.** `vitrinka setup` compared a
+hook's command but never its timeout, so a row whose command never changed
+kept the ceiling it was first written with — the Stop gate stayed at 20 s on
+every upgraded machine while setup reported done and `doctor` agreed. The
+timeout is now part of the hook's identity: setup rewrites a stale ceiling
+in place and counts it as drift. Re-run `vitrinka setup` once on 5.5.1.
+
+**`setup` repairs the Codex hooks it is told to repair.** `doctor`'s
+`hooks·codex` row has always named `vitrinka setup` as its fix, but setup
+only ever touched Claude's `settings.json`, so a machine kept the retired
+`hook-context task` row in `~/.codex/hooks.json` indefinitely. The step now
+covers every harness present, and the presence probe for the Claude CLI is
+memoized like its Codex twin — setup asked for it up to three times, each a
+3-second subprocess.
+
+## 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`,

package/package.json

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