@vitrinka/cli 5.0.0 → 5.0.1

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.
package/CHANGELOG.md CHANGED
@@ -1,8 +1,20 @@
1
1
  # Changelog
2
2
 
3
- `vitrinka setup update` prints the sections newer than your previous version
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.0.1
7
+
8
+ `vitrinka update` and `vitrinka doctor` are back at the top level, the way
9
+ `brew doctor`, `flutter doctor` and `<tool> update` read; `setup update` and
10
+ `setup doctor` are gone (unknown command, exit 2 — no aliases). `setup` keeps
11
+ the bare first run plus `uninstall`, `extension` and `skills`.
12
+
13
+ `vitrinka task list --json id,title` (a space before the field list) used to
14
+ fail as "unknown command id,title". It now says what it means: the field list
15
+ rides the flag with `=` — `--json=id,title` — and the fix line is the
16
+ corrected command.
17
+
6
18
  ## 5.0.0
7
19
 
8
20
  One vocabulary. The CLI is twenty entries: nouns that group verbs, three
@@ -12,8 +24,8 @@ they print "unknown command" and exit 2. There are no aliases.
12
24
  ```text
13
25
  Old New
14
26
  install · project setup setup (the whole first run)
15
- doctor · extension doctor setup doctor
16
- update · uninstall setup update · setup uninstall
27
+ doctor · extension doctor doctor
28
+ update · uninstall update · setup uninstall
17
29
  extension … · skills … setup extension … · setup skills …
18
30
  set init|push|capture|rename|meta board init|push|capture|rename|meta
19
31
  artifact … · diagram … board artifact … · board diagram …
@@ -43,7 +55,7 @@ operator · use · smtp config operator · config bind · admin smt
43
55
  minus lockfiles, generated, vendored and `.github`), apply, next action.
44
56
  Done steps are skipped on rerun; Back keeps your answers; the key bar
45
57
  survives 80 columns. `--advanced` opens the directory picker.
46
- - **`vitrinka setup doctor`** checks the installation and this repository;
58
+ - **`vitrinka doctor`** checks the installation and this repository;
47
59
  `--all` adds every registered project. `--fix` shows a target · before ·
48
60
  after plan and applies it after review.
49
61
 
package/README.md CHANGED
@@ -25,9 +25,9 @@ finds, a `vitrinka` shim on PATH, shell completion — all reversible), then ask
25
25
  input, → the OS keyring) and the operator name.
26
26
 
27
27
  ```bash
28
- vitrinka setup doctor # server, token, operator, skills, shim, MCP
29
- vitrinka setup doctor --fix # repairs the repairable
30
- vitrinka setup update # update the CLI and everything install put here
28
+ vitrinka doctor # server, token, operator, skills, shim, MCP
29
+ vitrinka doctor --fix # repairs the repairable
30
+ vitrinka update # update the CLI and everything install put here
31
31
  vitrinka setup uninstall # remove it all (--purge: token too)
32
32
  ```
33
33
 
@@ -53,7 +53,7 @@ OpenCode (`opencode.json`), VS Code (`.vscode/mcp.json`), Gemini CLI
53
53
  (`.gemini/settings.json`) — as a plain remote URL the harness signs into with
54
54
  its own OAuth flow; `--harness <csv|all>` picks them (default: Claude Code
55
55
  plus whatever is detected), entries merge into existing files, and
56
- `vitrinka setup doctor` reports drift. Through a user-level entry (root `/mcp`)
56
+ `vitrinka doctor` reports drift. Through a user-level entry (root `/mcp`)
57
57
  writes reach only projects that already exist; the bound repo's project file
58
58
  is what allows creating them.
59
59
 
@@ -72,7 +72,7 @@ no headers:
72
72
  ```
73
73
 
74
74
  > The old **HTTP + `Authorization: Bearer …` registration is retired** — it
75
- > baked a credential into client config. `vitrinka setup doctor` flags it and
75
+ > baked a credential into client config. `vitrinka doctor` flags it and
76
76
  > `vitrinka setup` rewrites it.
77
77
 
78
78
  `vitrinka setup` also links `~/.local/bin/vitrinka` straight to the Go
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vitrinka/cli",
3
- "version": "5.0.0",
3
+ "version": "5.0.1",
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.0.0",
19
- "@vitrinka/cli-darwin-x64": "5.0.0",
20
- "@vitrinka/cli-linux-arm64": "5.0.0",
21
- "@vitrinka/cli-linux-x64": "5.0.0",
22
- "@vitrinka/cli-win32-arm64": "5.0.0",
23
- "@vitrinka/cli-win32-x64": "5.0.0"
18
+ "@vitrinka/cli-darwin-arm64": "5.0.1",
19
+ "@vitrinka/cli-darwin-x64": "5.0.1",
20
+ "@vitrinka/cli-linux-arm64": "5.0.1",
21
+ "@vitrinka/cli-linux-x64": "5.0.1",
22
+ "@vitrinka/cli-win32-arm64": "5.0.1",
23
+ "@vitrinka/cli-win32-x64": "5.0.1"
24
24
  },
25
25
  "keywords": [
26
26
  "vitrinka",