@vitrinka/cli 5.5.0 → 5.6.0

package/CHANGELOG.md

@@ -3,6 +3,46 @@
 `vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 5.6.0
+
+**A native work hub without marking your project briefs read.**
+`vitrinka me hub --json` gathers projects, tasks waiting on you, active runs
+and linked completion, verification, merge and deployment evidence. History
+covers up to 30 days, with resumable pages and explicit source coverage.
+
+**Live updates over one read-only connection.** `vitrinka me hub --watch
+--json` streams snapshots when workspace activity changes, without idle
+polling or claiming an annotation listener. Successes and failures each use
+one JSON envelope per line, suitable for native clients such as Switcheroo.
+
+**Automatic achievements grounded in recorded outcomes.** `vitrinka me hub
+--generate --json` requests daily-capped Eve proposals and reuses cached
+definitions. Starter milestones and cached results remain explicit when AI
+is unavailable; proposals never declare work complete. These commands need
+the matching work-hub server endpoints and a personal Vitrinka identity.
+
+**Capture details survive publishing.** Usertest snapshots retain their
+route, state, device and capture context on QA cards. Capture writes also
+restore the runtime directory's Git ignore file, keeping local screenshots
+out of accidental commits.
+
+## 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

package/package.json

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