@vitrinka/cli 3.4.2 → 3.5.0

package/CHANGELOG.md

@@ -3,6 +3,25 @@
 `vitrinka update` prints the sections newer than your previous version after
 updating — keep entries short and user-facing.
 
+## 3.5.0
+
+### Added
+- **`vitrinka skills` — the skill store.** Browse the catalog, see per-runtime
+  install state, and toggle per-skill visibility for Claude Code and Codex,
+  all through the native plugin mechanisms.
+- **`/vitrinka:usertest`** — an autonomous exploratory user-tester skill ships
+  in the plugin.
+
+### Changed
+- **The plugin now installs from the public `vitrinka-kit` repo** —
+  `claude plugin marketplace add FixIt-Technologies/vitrinka-kit`, spec
+  `vitrinka@vitrinka`. `vitrinka install` registers the new source.
+- **Machines installed under the legacy `vitrinka@lovinka` id are migrated
+  automatically** by `vitrinka install` (run it once; `vitrinka doctor` shows
+  a "legacy id lingers" row until you do).
+- The `recall` skill dissolved into the MCP server instructions — one fewer
+  skill, same pre-build memory pass.
+
 ## 3.4.2
 
 ### Fixed
@@ -58,11 +77,11 @@ updating — keep entries short and user-facing.
 ## 3.3.0 — unreleased
 
 ### Changed
-- **Package renamed: `@lovinka/vitrinka` → `@vitrinka/cli`** (platform packages
+- **Package renamed to `@vitrinka/cli`** (platform packages
   `@vitrinka/cli-<os>-<arch>`). Same CLI, same `vitrinka` bin, now under the
   product's own npm scope alongside `@vitrinka/expo`. `vitrinka update` on an
-  old-scope install migrates automatically (removes the legacy package before
-  installing this one); `@lovinka/vitrinka` is deprecated with a pointer here.
+  old-scope install migrates automatically (removes the legacy launcher before
+  installing this one); the retired launcher is deprecated with a pointer here.
 
 ## 3.2.0 — 2026-08-23
 
@@ -152,7 +171,7 @@ updating — keep entries short and user-facing.
 
 ## 3.0.0 — 2026-08-18
 
-The CLI is now a **compiled Go binary**. `@lovinka/vitrinka` is a thin npm
+The CLI is now a **compiled Go binary**. The npm package is a thin
 launcher: it resolves the per-platform binary package for your machine and
 execs it. Same commands, same flags, same config files — no Node runtime
 needed to run vitrinka, and startup is instant.
@@ -160,7 +179,7 @@ needed to run vitrinka, and startup is instant.
 ### Changed
 - **`vitrinka` is Go.** Source moved from `pkg/src/cli.ts` to `cmd/vitrinka` +
   `internal/cli/*` in the vitrinka repo. The npm package ships `bin/vitrinka.js`,
-  which launches the binary from `@lovinka/vitrinka-<platform>-<arch>`
+  which launches the per-platform binary package
   (declared as optionalDependencies, resolved by npm from whatever registry
   you already use — no postinstall download, works offline and behind proxies).
 - Installing with `--omit=optional` / `--no-optional` skips the binary by

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@vitrinka/cli",
-  "version": "3.4.2",
-  "description": "vitrinka CLI — capture and publish artifact sets, drive the annotation-board work queue. Thin npm launcher for the single-binary Go CLI.",
+  "version": "3.5.0",
+  "description": "vitrinka CLI \u2014 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"
   },
@@ -14,12 +14,12 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@vitrinka/cli-darwin-arm64": "3.4.2",
-    "@vitrinka/cli-darwin-x64": "3.4.2",
-    "@vitrinka/cli-linux-arm64": "3.4.2",
-    "@vitrinka/cli-linux-x64": "3.4.2",
-    "@vitrinka/cli-win32-arm64": "3.4.2",
-    "@vitrinka/cli-win32-x64": "3.4.2"
+    "@vitrinka/cli-darwin-arm64": "3.5.0",
+    "@vitrinka/cli-darwin-x64": "3.5.0",
+    "@vitrinka/cli-linux-arm64": "3.5.0",
+    "@vitrinka/cli-linux-x64": "3.5.0",
+    "@vitrinka/cli-win32-arm64": "3.5.0",
+    "@vitrinka/cli-win32-x64": "3.5.0"
   },
   "keywords": [
     "vitrinka",