@vitrinka/cli 5.0.0 → 5.0.2

package/CHANGELOG.md

@@ -1,8 +1,33 @@
 # Changelog
 
-`vitrinka setup update` prints the sections newer than your previous version
+`vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 5.0.2
+
+`vitrinka setup` now installs the todo hooks it always claimed to. `doctor`
+names setup as the repair when the SessionStart todo rows are missing their
+`startup|clear` matcher or the PreToolUse touch row is absent, but setup only
+ever wrote the task-run hooks — it printed "Claude hooks done" and changed
+nothing. Run `vitrinka setup` once after updating and `vitrinka doctor` goes
+clean.
+
+Until a machine does that, its session starts still inject the whole open
+todo list on every start, resume and compaction, instead of the handful of
+todos whose condition actually fired.
+
+## 5.0.1
+
+`vitrinka update` and `vitrinka doctor` are back at the top level, the way
+`brew doctor`, `flutter doctor` and `<tool> update` read; `setup update` and
+`setup doctor` are gone (unknown command, exit 2 — no aliases). `setup` keeps
+the bare first run plus `uninstall`, `extension` and `skills`.
+
+`vitrinka task list --json id,title` (a space before the field list) used to
+fail as "unknown command id,title". It now says what it means: the field list
+rides the flag with `=` — `--json=id,title` — and the fix line is the
+corrected command.
+
 ## 5.0.0
 
 One vocabulary. The CLI is twenty entries: nouns that group verbs, three
@@ -12,8 +37,8 @@ they print "unknown command" and exit 2. There are no aliases.
 ```text
 Old                                New
 install · project setup            setup            (the whole first run)
-doctor · extension doctor          setup doctor
-update · uninstall                 setup update · setup uninstall
+doctor · extension doctor          doctor
+update · uninstall                 update · setup uninstall
 extension … · skills …             setup extension … · setup skills …
 set init|push|capture|rename|meta  board init|push|capture|rename|meta
 artifact … · diagram …             board artifact … · board diagram …
@@ -43,7 +68,7 @@ operator · use · smtp              config operator · config bind · admin smt
   minus lockfiles, generated, vendored and `.github`), apply, next action.
   Done steps are skipped on rerun; Back keeps your answers; the key bar
   survives 80 columns. `--advanced` opens the directory picker.
-- **`vitrinka setup doctor`** checks the installation and this repository;
+- **`vitrinka doctor`** checks the installation and this repository;
   `--all` adds every registered project. `--fix` shows a target · before ·
   after plan and applies it after review.
 

package/README.md

@@ -25,9 +25,9 @@ finds, a `vitrinka` shim on PATH, shell completion — all reversible), then ask
 input, → the OS keyring) and the operator name.
 
 ```bash
-vitrinka setup doctor          # server, token, operator, skills, shim, MCP
-vitrinka setup doctor --fix    # repairs the repairable
-vitrinka setup update          # update the CLI and everything install put here
+vitrinka doctor          # server, token, operator, skills, shim, MCP
+vitrinka doctor --fix    # repairs the repairable
+vitrinka update          # update the CLI and everything install put here
 vitrinka setup uninstall       # remove it all (--purge: token too)
 ```
 
@@ -53,7 +53,7 @@ OpenCode (`opencode.json`), VS Code (`.vscode/mcp.json`), Gemini CLI
 (`.gemini/settings.json`) — as a plain remote URL the harness signs into with
 its own OAuth flow; `--harness <csv|all>` picks them (default: Claude Code
 plus whatever is detected), entries merge into existing files, and
-`vitrinka setup doctor` reports drift. Through a user-level entry (root `/mcp`)
+`vitrinka doctor` reports drift. Through a user-level entry (root `/mcp`)
 writes reach only projects that already exist; the bound repo's project file
 is what allows creating them.
 
@@ -72,7 +72,7 @@ no headers:
 ```
 
 > The old **HTTP + `Authorization: Bearer …` registration is retired** — it
-> baked a credential into client config. `vitrinka setup doctor` flags it and
+> baked a credential into client config. `vitrinka doctor` flags it and
 > `vitrinka setup` rewrites it.
 
 `vitrinka setup` also links `~/.local/bin/vitrinka` straight to the Go

package/package.json

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