@vitrinka/cli 3.3.0 → 3.5.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 (3) hide show
  1. package/CHANGELOG.md +76 -5
  2. package/README.md +4 -4
  3. package/package.json +8 -8
package/CHANGELOG.md CHANGED
@@ -3,14 +3,85 @@
3
3
  `vitrinka update` prints the sections newer than your previous version after
4
4
  updating — keep entries short and user-facing.
5
5
 
6
+ ## 3.5.0
7
+
8
+ ### Added
9
+ - **`vitrinka skills` — the skill store.** Browse the catalog, see per-runtime
10
+ install state, and toggle per-skill visibility for Claude Code and Codex,
11
+ all through the native plugin mechanisms.
12
+ - **`/vitrinka:usertest`** — an autonomous exploratory user-tester skill ships
13
+ in the plugin.
14
+
15
+ ### Changed
16
+ - **The plugin now installs from the public `vitrinka-kit` repo** —
17
+ `claude plugin marketplace add FixIt-Technologies/vitrinka-kit`, spec
18
+ `vitrinka@vitrinka`. `vitrinka install` registers the new source.
19
+ - **Machines installed under the legacy `vitrinka@lovinka` id are migrated
20
+ automatically** by `vitrinka install` (run it once; `vitrinka doctor` shows
21
+ a "legacy id lingers" row until you do).
22
+ - The `recall` skill dissolved into the MCP server instructions — one fewer
23
+ skill, same pre-build memory pass.
24
+
25
+ ## 3.4.2
26
+
27
+ ### Fixed
28
+ - **npm releases flow again.** The npm channel had been stuck at 3.3.0 since
29
+ the scope move; publishing is restored, so `npm i -g @vitrinka/cli` and the
30
+ shelf now carry the same version. No CLI behavior changes since 3.4.1.
31
+
32
+ ## 3.4.1
33
+
34
+ ### Changed
35
+ - **Updates come from `releases.vitrinka.ai`** — the public vitrinka release
36
+ host. `vitrinka update` and the recorder extension no longer read the
37
+ internal shelf domain, which was unreachable outside the company network.
38
+ Mirrors via `$VITRINKA_RELEASE_FEED` are unchanged.
39
+
40
+ ## 3.4.0
41
+
42
+ ### Changed
43
+ - **The CLI targets `app.vitrinka.ai`** — the app moved off the apex in the
44
+ host split, and the old default could only die on a redirect that drops your
45
+ credential. Old sign-ins keep working (credentials and bindings carry over),
46
+ and an explicit `--base`, `$VITRINKA_URL` or script still pointing at
47
+ `vitrinka.ai` / `vitrinka.in` self-heals to the app host on its own. Nothing
48
+ to migrate.
49
+ - **`vitrinka board create` names the board after the whole set** —
50
+ `<project>-<branch>-<setkey>`, not the set key alone. The key defaults to
51
+ today's date and board slugs are workspace-global, so two repos capturing on
52
+ the same day used to ask for the very same board. Pass `--slug` to name it
53
+ yourself; existing boards are untouched.
54
+
55
+ ### Fixed
56
+ - **`--base` sticks.** Signing in (or pasting a token during `vitrinka
57
+ install`) now persists that deployment as this machine's default, so bare
58
+ commands — `doctor`, `watch`, `mcp` — keep talking to the install you signed
59
+ into instead of the hosted default. No standing `$VITRINKA_URL` needed;
60
+ logging out of it resets the default.
61
+ - **A taken slug is never adopted blindly.** When the board already belongs to
62
+ another project, `board create` stops and tells you whose it is instead of
63
+ importing your set onto someone else's canvas. Reuse of your own board is
64
+ unchanged — it just says so now.
65
+
66
+ ## 3.3.1
67
+
68
+ ### Fixed
69
+ - **Board listeners work again.** `vitrinka watch` no longer degrades to
70
+ "unreachable" on quiet boards — the long-poll was being killed by the CLI's
71
+ own 30-second network timeout, so every idle cycle counted as a failure.
72
+ Idle holds now run their full window and quiet timeouts are treated as the
73
+ normal heartbeat they are.
74
+ - Redirects between vitrinka hosts (e.g. `vitrinka.in` → `vitrinka.ai`) no
75
+ longer drop your credential mid-flight (HTTPS targets only).
76
+
6
77
  ## 3.3.0 — unreleased
7
78
 
8
79
  ### Changed
9
- - **Package renamed: `@lovinka/vitrinka` → `@vitrinka/cli`** (platform packages
80
+ - **Package renamed to `@vitrinka/cli`** (platform packages
10
81
  `@vitrinka/cli-<os>-<arch>`). Same CLI, same `vitrinka` bin, now under the
11
82
  product's own npm scope alongside `@vitrinka/expo`. `vitrinka update` on an
12
- old-scope install migrates automatically (removes the legacy package before
13
- installing this one); `@lovinka/vitrinka` is deprecated with a pointer here.
83
+ old-scope install migrates automatically (removes the legacy launcher before
84
+ installing this one); the retired launcher is deprecated with a pointer here.
14
85
 
15
86
  ## 3.2.0 — 2026-08-23
16
87
 
@@ -100,7 +171,7 @@ updating — keep entries short and user-facing.
100
171
 
101
172
  ## 3.0.0 — 2026-08-18
102
173
 
103
- The CLI is now a **compiled Go binary**. `@lovinka/vitrinka` is a thin npm
174
+ The CLI is now a **compiled Go binary**. The npm package is a thin
104
175
  launcher: it resolves the per-platform binary package for your machine and
105
176
  execs it. Same commands, same flags, same config files — no Node runtime
106
177
  needed to run vitrinka, and startup is instant.
@@ -108,7 +179,7 @@ needed to run vitrinka, and startup is instant.
108
179
  ### Changed
109
180
  - **`vitrinka` is Go.** Source moved from `pkg/src/cli.ts` to `cmd/vitrinka` +
110
181
  `internal/cli/*` in the vitrinka repo. The npm package ships `bin/vitrinka.js`,
111
- which launches the binary from `@lovinka/vitrinka-<platform>-<arch>`
182
+ which launches the per-platform binary package
112
183
  (declared as optionalDependencies, resolved by npm from whatever registry
113
184
  you already use — no postinstall download, works offline and behind proxies).
114
185
  - Installing with `--omit=optional` / `--no-optional` skips the binary by
package/README.md CHANGED
@@ -41,7 +41,7 @@ The MCP server is **remote** — it runs inside the vitrinka server, so there is
41
41
  nothing to install and nothing to keep up to date. Register it once:
42
42
 
43
43
  ```bash
44
- claude mcp add --scope user --transport http vitrinka https://vitrinka.ai/mcp \
44
+ claude mcp add --scope user --transport http vitrinka https://app.vitrinka.ai/mcp \
45
45
  --header "Authorization: Bearer $(vitrinka token)"
46
46
  ```
47
47
 
@@ -52,7 +52,7 @@ For Claude Desktop or any other MCP client, add the equivalent HTTP entry:
52
52
  "mcpServers": {
53
53
  "vitrinka": {
54
54
  "type": "http",
55
- "url": "https://vitrinka.ai/mcp",
55
+ "url": "https://app.vitrinka.ai/mcp",
56
56
  "headers": { "Authorization": "Bearer …" }
57
57
  }
58
58
  }
@@ -71,7 +71,7 @@ vitrinka is reachable over the WireGuard mesh — bring the VPN up (or point
71
71
 
72
72
  | Var | Default | Purpose |
73
73
  |---|---|---|
74
- | `VITRINKA_URL` / `VITRINKA_BASE_URL` | `https://vitrinka.ai` | vitrinka server base URL. `VITRINKA_URL` wins, then `VITRINKA_BASE_URL`; the CLI's `--base` flag overrides both. |
74
+ | `VITRINKA_URL` / `VITRINKA_BASE_URL` | `https://app.vitrinka.ai` | vitrinka server base URL. `VITRINKA_URL` wins, then `VITRINKA_BASE_URL`; the CLI's `--base` flag overrides both. |
75
75
  | `VITRINKA_TOKEN` | — | Bearer write token. Falls back to the OS keyring / `~/.config/vitrinka/`. Required only by the **mutating** calls; read calls work unauthenticated. |
76
76
  | `VITRINKA_OPERATOR` | — | Operator persona name. When set, write calls carry `X-Board-Actor: <name>` so the board credits the operator — agent-authored content keeps its explicit `claude` attribution. |
77
77
 
@@ -98,7 +98,7 @@ vitrinka index --explain path/to/file # winning selection or deny rule
98
98
  ```
99
99
 
100
100
  The config schema is served by the deployment at
101
- `https://vitrinka.ai/static/vitrinka.config.schema.json` — reference it from
101
+ `https://app.vitrinka.ai/static/vitrinka.config.schema.json` — reference it from
102
102
  `$schema` in your `vitrinka.config.json` for editor completion.
103
103
 
104
104
  ## Desktop app
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@vitrinka/cli",
3
- "version": "3.3.0",
4
- "description": "vitrinka CLI — capture and publish artifact sets, drive the annotation-board work queue. Thin npm launcher for the single-binary Go CLI.",
3
+ "version": "3.5.0",
4
+ "description": "vitrinka CLI \u2014 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"
7
7
  },
@@ -14,12 +14,12 @@
14
14
  "node": ">=18"
15
15
  },
16
16
  "optionalDependencies": {
17
- "@vitrinka/cli-darwin-arm64": "3.3.0",
18
- "@vitrinka/cli-darwin-x64": "3.3.0",
19
- "@vitrinka/cli-linux-arm64": "3.3.0",
20
- "@vitrinka/cli-linux-x64": "3.3.0",
21
- "@vitrinka/cli-win32-arm64": "3.3.0",
22
- "@vitrinka/cli-win32-x64": "3.3.0"
17
+ "@vitrinka/cli-darwin-arm64": "3.5.0",
18
+ "@vitrinka/cli-darwin-x64": "3.5.0",
19
+ "@vitrinka/cli-linux-arm64": "3.5.0",
20
+ "@vitrinka/cli-linux-x64": "3.5.0",
21
+ "@vitrinka/cli-win32-arm64": "3.5.0",
22
+ "@vitrinka/cli-win32-x64": "3.5.0"
23
23
  },
24
24
  "keywords": [
25
25
  "vitrinka",