@vitrinka/cli 3.3.0 → 3.4.2

package/CHANGELOG.md

@@ -3,6 +3,58 @@
 `vitrinka update` prints the sections newer than your previous version after
 updating — keep entries short and user-facing.
 
+## 3.4.2
+
+### Fixed
+- **npm releases flow again.** The npm channel had been stuck at 3.3.0 since
+  the scope move; publishing is restored, so `npm i -g @vitrinka/cli` and the
+  shelf now carry the same version. No CLI behavior changes since 3.4.1.
+
+## 3.4.1
+
+### Changed
+- **Updates come from `releases.vitrinka.ai`** — the public vitrinka release
+  host. `vitrinka update` and the recorder extension no longer read the
+  internal shelf domain, which was unreachable outside the company network.
+  Mirrors via `$VITRINKA_RELEASE_FEED` are unchanged.
+
+## 3.4.0
+
+### Changed
+- **The CLI targets `app.vitrinka.ai`** — the app moved off the apex in the
+  host split, and the old default could only die on a redirect that drops your
+  credential. Old sign-ins keep working (credentials and bindings carry over),
+  and an explicit `--base`, `$VITRINKA_URL` or script still pointing at
+  `vitrinka.ai` / `vitrinka.in` self-heals to the app host on its own. Nothing
+  to migrate.
+- **`vitrinka board create` names the board after the whole set** —
+  `<project>-<branch>-<setkey>`, not the set key alone. The key defaults to
+  today's date and board slugs are workspace-global, so two repos capturing on
+  the same day used to ask for the very same board. Pass `--slug` to name it
+  yourself; existing boards are untouched.
+
+### Fixed
+- **`--base` sticks.** Signing in (or pasting a token during `vitrinka
+  install`) now persists that deployment as this machine's default, so bare
+  commands — `doctor`, `watch`, `mcp` — keep talking to the install you signed
+  into instead of the hosted default. No standing `$VITRINKA_URL` needed;
+  logging out of it resets the default.
+- **A taken slug is never adopted blindly.** When the board already belongs to
+  another project, `board create` stops and tells you whose it is instead of
+  importing your set onto someone else's canvas. Reuse of your own board is
+  unchanged — it just says so now.
+
+## 3.3.1
+
+### Fixed
+- **Board listeners work again.** `vitrinka watch` no longer degrades to
+  "unreachable" on quiet boards — the long-poll was being killed by the CLI's
+  own 30-second network timeout, so every idle cycle counted as a failure.
+  Idle holds now run their full window and quiet timeouts are treated as the
+  normal heartbeat they are.
+- Redirects between vitrinka hosts (e.g. `vitrinka.in` → `vitrinka.ai`) no
+  longer drop your credential mid-flight (HTTPS targets only).
+
 ## 3.3.0 — unreleased
 
 ### Changed

package/README.md

@@ -41,7 +41,7 @@ The MCP server is **remote** — it runs inside the vitrinka server, so there is
 nothing to install and nothing to keep up to date. Register it once:
 
 ```bash
-claude mcp add --scope user --transport http vitrinka https://vitrinka.ai/mcp \
+claude mcp add --scope user --transport http vitrinka https://app.vitrinka.ai/mcp \
   --header "Authorization: Bearer $(vitrinka token)"
 ```
 
@@ -52,7 +52,7 @@ For Claude Desktop or any other MCP client, add the equivalent HTTP entry:
   "mcpServers": {
     "vitrinka": {
       "type": "http",
-      "url": "https://vitrinka.ai/mcp",
+      "url": "https://app.vitrinka.ai/mcp",
       "headers": { "Authorization": "Bearer …" }
     }
   }
@@ -71,7 +71,7 @@ vitrinka is reachable over the WireGuard mesh — bring the VPN up (or point
 
 | Var | Default | Purpose |
 |---|---|---|
-| `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. |
+| `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. |
 | `VITRINKA_TOKEN` | — | Bearer write token. Falls back to the OS keyring / `~/.config/vitrinka/`. Required only by the **mutating** calls; read calls work unauthenticated. |
 | `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. |
 
@@ -98,7 +98,7 @@ vitrinka index --explain path/to/file # winning selection or deny rule
 ```
 
 The config schema is served by the deployment at
-`https://vitrinka.ai/static/vitrinka.config.schema.json` — reference it from
+`https://app.vitrinka.ai/static/vitrinka.config.schema.json` — reference it from
 `$schema` in your `vitrinka.config.json` for editor completion.
 
 ## Desktop app

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vitrinka/cli",
-  "version": "3.3.0",
+  "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.",
   "bin": {
     "vitrinka": "bin/vitrinka.js"
@@ -14,12 +14,12 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@vitrinka/cli-darwin-arm64": "3.3.0",
-    "@vitrinka/cli-darwin-x64": "3.3.0",
-    "@vitrinka/cli-linux-arm64": "3.3.0",
-    "@vitrinka/cli-linux-x64": "3.3.0",
-    "@vitrinka/cli-win32-arm64": "3.3.0",
-    "@vitrinka/cli-win32-x64": "3.3.0"
+    "@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"
   },
   "keywords": [
     "vitrinka",