@vitrinka/cli 4.0.0 → 4.2.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 (2) hide show
  1. package/CHANGELOG.md +65 -0
  2. package/package.json +7 -7
package/CHANGELOG.md CHANGED
@@ -3,6 +3,71 @@
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
+ ## 4.2.0
7
+
8
+ `update` can no longer skip a plugin silently, `doctor` catches a plugin that
9
+ fell behind the CLI, board reviews become audited judgments, and work time is
10
+ measured instead of typed.
11
+
12
+ ### Fixed
13
+ - **`vitrinka update` refreshes the Codex plugin again.** When the
14
+ `codex plugin list` probe failed, the runtime printed as `(no plugin)` and
15
+ the refresh was skipped without a word — Codex sat two releases behind
16
+ while `update` reported success. A failed probe now prints
17
+ `codex (probe failed)`, warns with the real failure and lands under
18
+ "steps need a hand" with the re-run; a probe whose process exited is
19
+ taken as its answer even when a grandchild held the pipe past the deadline.
20
+ - **`vitrinka doctor` reports plugin version drift**: an installed plugin
21
+ whose version disagrees with the CLI shows
22
+ `stale — 3.11.0 installed, CLI is 4.2.0 — repair: vitrinka update`
23
+ instead of a green `installed`; a failed probe is a red `probe failed`
24
+ row, never `not installed`.
25
+
26
+ ### Added
27
+ - **`vitrinka review judge <board|set>`** replaces the old board reviewer:
28
+ captured screens are judged server-side, every failed judgment gets an
29
+ independent audit, and `--status` reads compact results. `review judge
30
+ export <job>` prints version-pinned judgments for local triage and
31
+ `review file` files the ones you keep. Skills `review` and `tasks` follow.
32
+ - **`vitrinka time enable|disable|status|capture`** and **`time service
33
+ install`** — opt-in, automatic capture of human and agent effort
34
+ (Claude/Codex hooks, a local collector kept running at login) feeding the
35
+ task and epic time views;
36
+ `get_work_time` / `get_work_evidence` / `get_work_forecasts` read the
37
+ ledger over MCP.
38
+
39
+ ## 4.1.0
40
+
41
+ The brainstorm hands itself off: a feature brief the next session reads
42
+ instead of the whole board, one worktree per feature, and a machine ledger
43
+ `doctor` can repair.
44
+
45
+ ### Added
46
+ - **`vitrinka task brief <epic> [--out <file>]`** composes the brainstorm
47
+ board's `Plan` chapter (chosen takes only) and prints the brief skeleton;
48
+ the skill fills the prose and re-uploads it as the next version.
49
+ - **`vitrinka task upload <id> <files…> --kind <kind> --hint <text> --version-of <refId>`**
50
+ attaches typed, hinted files, optionally as the next version of an
51
+ existing lineage.
52
+ - **`vitrinka task pickup` honours `meta.load`** on refs: `first` leads the
53
+ READ rail, `on-demand` prints as a `read on demand:` line, `never` hides.
54
+ - **Brainstorming skill**: `deep` level (same flow, bigger budget), spike /
55
+ bounded / architectural classification before the first question, the
56
+ feature worktree created at step 1, a vocabulary challenge, and every
57
+ brainstorm closes with "in which style to implement".
58
+ - **`project setup` picks the project** from the workspace's projects and
59
+ their declared repositories; **`project link` / `project unlink`** manage
60
+ a checkout's binding.
61
+ - **`vitrinka doctor` reads the machine ledger** (`projects.<name>.repos[]`
62
+ in the config) and **`doctor --fix`** repairs machine, server and per-repo
63
+ drift after one confirm.
64
+ - **`vitrinka dev` seeds a personal workspace** beside the team one.
65
+
66
+ ### Changed
67
+ - `project setup` appends the origin to a non-empty declared repository
68
+ list instead of leaving it alone.
69
+ - The repo-side `docs` guide gains a `brief` topic (`vitrinka docs brief`).
70
+
6
71
  ## 4.0.0
7
72
 
8
73
  One `--json` shape for ordinary commands, including help, version and doctor.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vitrinka/cli",
3
- "version": "4.0.0",
3
+ "version": "4.2.0",
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": "4.0.0",
19
- "@vitrinka/cli-darwin-x64": "4.0.0",
20
- "@vitrinka/cli-linux-arm64": "4.0.0",
21
- "@vitrinka/cli-linux-x64": "4.0.0",
22
- "@vitrinka/cli-win32-arm64": "4.0.0",
23
- "@vitrinka/cli-win32-x64": "4.0.0"
18
+ "@vitrinka/cli-darwin-arm64": "4.2.0",
19
+ "@vitrinka/cli-darwin-x64": "4.2.0",
20
+ "@vitrinka/cli-linux-arm64": "4.2.0",
21
+ "@vitrinka/cli-linux-x64": "4.2.0",
22
+ "@vitrinka/cli-win32-arm64": "4.2.0",
23
+ "@vitrinka/cli-win32-x64": "4.2.0"
24
24
  },
25
25
  "keywords": [
26
26
  "vitrinka",