@vitrinka/cli 5.7.1 → 5.9.0

package/CHANGELOG.md

@@ -3,6 +3,46 @@
 `vitrinka update` prints the sections newer than your previous version
 after updating — keep entries short and user-facing.
 
+## 5.9.0
+
+**Task reads are flat, and every task spelling works.** `task search` and
+`task list` return flat rows with `parentId` and `url`; `--json=id,title`
+works on search, list and get; `task list --parent <task>` and
+`task get --include children` read an epic's tree in one call; search
+stays in this checkout's project unless you pass `--all` (`--limit` sizes
+it). Every task verb reads `42`, `#42`, `vt-42`, `VIT-42`, `fixit/42` or
+the task URL, and a spelling it cannot read fails with the fix before any
+request. `--jq` never hides a failure: a failed call prints its whole
+envelope with its exit code.
+
+**A failed request names its phase.** A DNS lookup that did not answer
+(with the resolver file behind it), a server that took the connection but
+never answered, or the network, instead of blanket proxy advice;
+`vitrinka doctor` gains a `dns` row. Also new: `board capture safari`
+shoots Mobile Safari on the iOS Simulator through Appium in six states
+with the measured safe-area insets; `setup --experimental` installs the
+opt-in `vitrinka-experimental` plugin (Claude Code only). `setup` and
+`doctor` keep a `?modules=` MCP list, `work watch` stops with a fix on a
+board this workspace does not hold, `task get` marks Eve and agent
+comments, `admin smtp` names who may edit the deployment mailer, and the
+tasks skill finds an epic by name in one call.
+
+## 5.8.0
+
+**Release notes read like a register.** Pushed documents take the new
+release vocabulary — galleries, compare charts, audience-tagged sections
+and table rows (`{cells, audience}`), a unit per compare item — and export
+from one viewer as PDF, HTML, email or Word. `vitrinka project release
+--notes <ref>` links a release to its notes document (`--notes-clear`
+unlinks it), and the release pool ranks screenshots by visual score so the
+notes carry the best shots once each. Web captures are 2× device scale by
+default (`capture.hidpi` in `vitrinka.config.json`). Slow uploads fail on
+an idle stall instead of a fixed deadline (`VITRINKA_UPLOAD_IDLE`
+overrides it), rapid captures on a slow link share one background push
+per capture folder that always ends on the newest shots, and
+`review file` without a valid `--agent` names the accepted runtimes and
+the corrected call.
+
 ## 5.7.1
 
 **Errors say what the server said.** When the server answers a 502/503/504

package/package.json

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