@vitrinka/cli 5.20.0 → 5.22.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CHANGELOG.md +30 -0
  2. package/package.json +7 -7
package/CHANGELOG.md CHANGED
@@ -3,6 +3,36 @@
3
3
  `vitrinka update` prints the sections newer than your previous version
4
4
  after updating — keep entries short and user-facing.
5
5
 
6
+ ## 5.22.0
7
+
8
+ **memo's memory islands reach vitrinka.** This update is all a Mac
9
+ running memo needs: memo calls four hidden doors from its outbox.
10
+ `memory snapshot put` publishes each cloud-bound island's snapshot of a
11
+ merged commit. The island's current moves only by compare-and-set, and a
12
+ stale publisher gets `cas_mismatch` with the cloud's current to adopt.
13
+ `memory usage put` sends this Mac's hourly usage tally. `memory resolve`
14
+ ranks `memo recall --deep` through Eve. `memory watch put|completions`
15
+ mirrors a `for: human` watch row to one todo and reports the todos
16
+ completed here. Agents read the cache as `get {kind: "project_memory"}`:
17
+ a bounded, ranked index, paged by cursor.
18
+
19
+ **Cut the release you deployed.** `vitrinka project release --refresh
20
+ --until <sha>` sweeps only the merges that commit contains and answers
21
+ its head, so a pipeline cuts exactly the tag it shipped.
22
+ `vitrinka deploy-mark` says how History ships a production mark: by
23
+ ancestry, with how many waiting refs it contains, or by the time rule
24
+ and why.
25
+
26
+ ## 5.21.0
27
+
28
+ **A fresh session opens again from Claude Code.** `vitrinka qa session
29
+ launch <task url> <dir>` runs your `$VITRINKA_SESSION_LAUNCHER` with
30
+ both appended and prints its receipt; the brainstorm's and the hand-back's
31
+ fresh-session exits call it. They used to run the launcher through
32
+ `sh -c`, which Claude Code's removal check refuses with nobody at the
33
+ prompt, so the exit always fell back to `/continue`. Unset, not runnable
34
+ or a non-zero exit still names the `/continue` line to run by hand.
35
+
6
36
  ## 5.20.0
7
37
 
8
38
  **The plugin is four plugins.** `vitrinka` (core: publish, artifact,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vitrinka/cli",
3
- "version": "5.20.0",
3
+ "version": "5.22.0",
4
4
  "description": "vitrinka CLI — capture and publish artifact sets, drive the annotation-board work queue. Thin npm launcher for the single-binary Go CLI.",
5
5
  "bin": {
6
6
  "vitrinka": "bin/vitrinka.js"
@@ -15,12 +15,12 @@
15
15
  "node": ">=18"
16
16
  },
17
17
  "optionalDependencies": {
18
- "@vitrinka/cli-darwin-arm64": "5.20.0",
19
- "@vitrinka/cli-darwin-x64": "5.20.0",
20
- "@vitrinka/cli-linux-arm64": "5.20.0",
21
- "@vitrinka/cli-linux-x64": "5.20.0",
22
- "@vitrinka/cli-win32-arm64": "5.20.0",
23
- "@vitrinka/cli-win32-x64": "5.20.0"
18
+ "@vitrinka/cli-darwin-arm64": "5.22.0",
19
+ "@vitrinka/cli-darwin-x64": "5.22.0",
20
+ "@vitrinka/cli-linux-arm64": "5.22.0",
21
+ "@vitrinka/cli-linux-x64": "5.22.0",
22
+ "@vitrinka/cli-win32-arm64": "5.22.0",
23
+ "@vitrinka/cli-win32-x64": "5.22.0"
24
24
  },
25
25
  "keywords": [
26
26
  "vitrinka",