@vitrinka/cli 5.9.0 → 5.11.0

package/CHANGELOG.md

@@ -3,6 +3,44 @@
 `vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 5.11.0
+
+**Decisions are asked while you are there.** The handoff and spot skills
+ask a call the person in the session can answer now and record the answer
+in the hand-back; a `Decide:` gate is filed only by a run nobody attends (a
+Workflow, a headless or scheduled run). A brainstorm decision settled in
+the terminal closes its board question, and the skills' `?modules=` advice
+names every module to keep (`core,pm,qa,me,rare`), so opting into `rare`
+no longer hides the task and personal tools.
+
+**Task search travels light.** `task search` reads compact rows, about
+2.5× smaller on the wire, with the same columns; `task list --text` matches
+tasks carrying every word while `task search` ranks any of them. `vitrinka
+help json` documents the envelope as it ships (`next[].do`,
+`diagnostics[].why`, `exit_code` on failure only), and the skills, help
+and session hints name the current commands and MCP calls.
+
+## 5.10.0
+
+**Find one task in one call.** `vitrinka search <ref> --resolve` reads a
+title, any id spelling, a URL, a branch or "bugs under <epic>" as one task
+reference and answers a verdict (exact, confident, ambiguous, none) with at
+most five candidates, each with its parent, child count and why it matched;
+a task verb handed a name instead of an id points at that exact call.
+`task search` filters by `--type`, `--state`, `--parent` and `--epic` (any
+depth), `--within <task>` searches one task's tree, each row says where it
+matched (`≈` marks a typo correction), and a type, state or project that
+names nothing is refused with the allowed values instead of an empty list.
+
+**Each shot uploads once.** Screenshot sets sync file by file: every
+capture sends only its new shots and the board fills live as they land, an
+explicit `board push` drops what the folder no longer holds, a set past 100
+files no longer trips the guard, and `qa run` reuses shots the set already
+holds; older deployments keep the whole-set upload. The plugin's review and
+code loops now fix on their last pass, converge only when every gate was
+green and walk every fixed usertest failure again; the experimental `test`
+run marks a PR ready only on a record a reviewer judged.
+
 ## 5.9.0
 
 **Task reads are flat, and every task spelling works.** `task search` and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vitrinka/cli",
-  "version": "5.9.0",
+  "version": "5.11.0",
   "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.9.0",
-    "@vitrinka/cli-darwin-x64": "5.9.0",
-    "@vitrinka/cli-linux-arm64": "5.9.0",
-    "@vitrinka/cli-linux-x64": "5.9.0",
-    "@vitrinka/cli-win32-arm64": "5.9.0",
-    "@vitrinka/cli-win32-x64": "5.9.0"
+    "@vitrinka/cli-darwin-arm64": "5.11.0",
+    "@vitrinka/cli-darwin-x64": "5.11.0",
+    "@vitrinka/cli-linux-arm64": "5.11.0",
+    "@vitrinka/cli-linux-x64": "5.11.0",
+    "@vitrinka/cli-win32-arm64": "5.11.0",
+    "@vitrinka/cli-win32-x64": "5.11.0"
   },
   "keywords": [
     "vitrinka",