@vitrinka/cli 5.5.1 → 5.6.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.
Files changed (2) hide show
  1. package/CHANGELOG.md +32 -0
  2. package/package.json +7 -7
package/CHANGELOG.md CHANGED
@@ -3,6 +3,38 @@
3
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.6.1
7
+
8
+ **`/vitrinka:review` files findings and stops.** A review pass, local or
9
+ Eve's, ends with staged annotations on the board and a report grouped by
10
+ root cause; it no longer fixes code or composes a next pass on its own. The
11
+ user accepts or dismisses on the board, and `/vitrinka:resolve` works what
12
+ was accepted — including re-capturing as a new pass and linking the Eve
13
+ post-fix audit.
14
+
15
+ ## 5.6.0
16
+
17
+ **A native work hub without marking your project briefs read.**
18
+ `vitrinka me hub --json` gathers projects, tasks waiting on you, active runs
19
+ and linked completion, verification, merge and deployment evidence. History
20
+ covers up to 30 days, with resumable pages and explicit source coverage.
21
+
22
+ **Live updates over one read-only connection.** `vitrinka me hub --watch
23
+ --json` streams snapshots when workspace activity changes, without idle
24
+ polling or claiming an annotation listener. Successes and failures each use
25
+ one JSON envelope per line, suitable for native clients such as Switcheroo.
26
+
27
+ **Automatic achievements grounded in recorded outcomes.** `vitrinka me hub
28
+ --generate --json` requests daily-capped Eve proposals and reuses cached
29
+ definitions. Starter milestones and cached results remain explicit when AI
30
+ is unavailable; proposals never declare work complete. These commands need
31
+ the matching work-hub server endpoints and a personal Vitrinka identity.
32
+
33
+ **Capture details survive publishing.** Usertest snapshots retain their
34
+ route, state, device and capture context on QA cards. Capture writes also
35
+ restore the runtime directory's Git ignore file, keeping local screenshots
36
+ out of accidental commits.
37
+
6
38
  ## 5.5.1
7
39
 
8
40
  **The 5.5.0 hook ceilings actually arrive.** `vitrinka setup` compared a
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vitrinka/cli",
3
- "version": "5.5.1",
3
+ "version": "5.6.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.5.1",
19
- "@vitrinka/cli-darwin-x64": "5.5.1",
20
- "@vitrinka/cli-linux-arm64": "5.5.1",
21
- "@vitrinka/cli-linux-x64": "5.5.1",
22
- "@vitrinka/cli-win32-arm64": "5.5.1",
23
- "@vitrinka/cli-win32-x64": "5.5.1"
18
+ "@vitrinka/cli-darwin-arm64": "5.6.1",
19
+ "@vitrinka/cli-darwin-x64": "5.6.1",
20
+ "@vitrinka/cli-linux-arm64": "5.6.1",
21
+ "@vitrinka/cli-linux-x64": "5.6.1",
22
+ "@vitrinka/cli-win32-arm64": "5.6.1",
23
+ "@vitrinka/cli-win32-x64": "5.6.1"
24
24
  },
25
25
  "keywords": [
26
26
  "vitrinka",