@vitrinka/cli 5.22.0 → 5.24.0

package/CHANGELOG.md

@@ -3,6 +3,61 @@
 `vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 5.24.0
+
+**Reviews read each screen once.** `vitrinka review plan <board>…`
+(`review_plan` for agents) plans a review over your boards: the latest
+capture pass by default, capture gaps left out, exact duplicates judged
+once, near-duplicates as a crop of what changed, and screens already
+judged under the same rubric reused — on a few labelled sheets instead
+of one image per screen. A host that cannot see images is stopped after
+the first sheet, and the run's receipt says what was inspected, reused or
+skipped. `--checklist` adds your own checks; `--full` re-judges
+everything.
+
+**Pick who judges your reviews.** `vitrinka config reviewer codex` judges
+screens on the Codex sidekick, `self` (the default) in the session that
+runs the review; the session start names the lane when it is not the
+default.
+
+**`vitrinka update` refreshes a slow Claude Code.** When `claude
+--version` (or `codex --version`) took more than three seconds — a busy
+computer is enough — update printed "claude (absent)" and skipped the
+plugin refresh without a word. Only a CLI missing from your PATH counts
+as absent now: a slow one is refreshed, and a refresh that fails says why.
+
+**A deleted artifact stays deleted.** `vitrinka board push` to an
+artifact someone deleted is refused with `artifact_deleted` and a link to
+its page, where Restore brings it back. `--revive` publishes it again on
+the same page instead.
+
+**Ticking one step keeps the rest.** A checklist written to a task
+(`vitrinka task field set`, an agent's `update`) now merges by item: send
+only the step you tick and the other steps and gates stay. `--replace`
+writes the whole list, the way to drop, rename or reorder items.
+
+## 5.23.0
+
+**Claude Code stays signed in to vitrinka.** `vitrinka update` and
+`setup modules` no longer rewrite the MCP registration when the modules
+it serves are unchanged — each rewrite signed every session out. Agents
+can no longer start a vitrinka sign-in: that cleared the sign-in every
+session on the computer shares. They now ask you to run `/mcp` →
+vitrinka → Reconnect instead.
+
+**A cut refuses a window that moved.** `vitrinka project release --cut
+--expect-head <sha>` refuses the cut with `release_head_mismatch`,
+cutting nothing, when a refresh moved the head since you checked it. The
+release prints `Page:` (and `--json` carries `docHeadSha`): whether
+Eve's page was written for the current head or is stale after a refresh.
+A window now starts after its start commit, so the PR that commit merged
+is never listed again.
+
+**A deploy mark says when its lineage is partial.** `vitrinka project
+deploy-mark prod <sha>` also prints how many merge commits were read
+from GitHub, and when GitHub's listing fell short it warns `Partial:`
+with how many merged PRs still ship by time.
+
 ## 5.22.0
 
 **memo's memory islands reach vitrinka.** This update is all a Mac

package/package.json

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