@vitrinka/cli 5.21.0 → 5.23.0

package/CHANGELOG.md

@@ -3,6 +3,48 @@
 `vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 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
+running memo needs: memo calls four hidden doors from its outbox.
+`memory snapshot put` publishes each cloud-bound island's snapshot of a
+merged commit. The island's current moves only by compare-and-set, and a
+stale publisher gets `cas_mismatch` with the cloud's current to adopt.
+`memory usage put` sends this Mac's hourly usage tally. `memory resolve`
+ranks `memo recall --deep` through Eve. `memory watch put|completions`
+mirrors a `for: human` watch row to one todo and reports the todos
+completed here. Agents read the cache as `get {kind: "project_memory"}`:
+a bounded, ranked index, paged by cursor.
+
+**Cut the release you deployed.** `vitrinka project release --refresh
+--until <sha>` sweeps only the merges that commit contains and answers
+its head, so a pipeline cuts exactly the tag it shipped.
+`vitrinka deploy-mark` says how History ships a production mark: by
+ancestry, with how many waiting refs it contains, or by the time rule
+and why.
+
 ## 5.21.0
 
 **A fresh session opens again from Claude Code.** `vitrinka qa session

package/package.json

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