@vitrinka/cli 3.9.1 → 3.11.0

package/CHANGELOG.md

@@ -3,6 +3,81 @@
 `vitrinka update` prints the sections newer than your previous version after
 updating — keep entries short and user-facing.
 
+## 3.11.0
+
+The task is the handoff: a session picks a task up from one bounded view,
+files what it spots the moment it sees it, and hands back through one door
+whose printed block is the hand-back. Every AI coding harness can listen.
+
+### Added
+- **`vitrinka task pickup [id|url]`** — the server-composed pickup: what the
+  task is about, the last hand-back, the branch (and whether it exists on
+  origin), what to read first, who is on it, the open children in rank order
+  and what was deliberately not loaded. MCP: `get_task {view: "pickup"}`.
+- **`vitrinka task handback [id]`** — one atomic door: next steps and
+  omissions become ranked children, the summary becomes the next version of
+  the task's `handoff` attachment, PR/board refs and status land, the parent
+  epic's `next_action` moves, and the printed block is the hand-back to paste
+  verbatim. `-` reads the exact REST body from stdin. MCP: `hand_back`.
+- **`vitrinka task spot <title>`** — file a defect or follow-up under the
+  bound task (else the project's rolling *Found during implementation* epic)
+  the moment you see it; `--production` adds the might-affect-production
+  label. MCP: `spot`.
+- **`vitrinka task start`** with no id binds the checkout's `vt-<id>` branch.
+- **Hooks**: `vitrinka project setup` offers the three Claude Code hooks
+  interactively and shows the exact `settings.json` entries — SessionStart
+  prints the pickup, SessionEnd writes the git residue into the run, and a
+  Stop gate asks for `hand_back` on a hand-back turn. `vitrinka install`
+  keeps registering them.
+- Two built-in rules move status by themselves: a run starting marks the
+  task in progress, an opened PR marks it in review (`merged-pr-completes`
+  stays).
+- **`vitrinka listen --harness <name>`** — host any harness (Codex, Gemini,
+  OpenCode, Cursor, …) over the Agent Client Protocol and feed it the scope's
+  board work; **`work watch --exec <harness>`** is the headless resume rung.
+  `install` provisions the adapters behind consent; `doctor` prints the
+  `listen·` and `acp·` rows.
+- **`vitrinka search <text>`** — the ⌘K palette from the terminal: tasks,
+  pages, boards, tags, cards, sessions and shots in one call; **`vitrinka
+  resolve <url>`** names what a pasted app URL points at, in any workspace.
+- **`vitrinka project fold <name> --into <home>`** (`fold-plan` for the dry
+  run) folds a stray project name into its real home and leaves an alias;
+  `project transfer` retires the source name.
+- Skills: `pickup`, `spot` and `handoff` (module `pm`); `listen` carries the
+  ONE listening ladder every finishing skill points at.
+
+### Changed
+- A task or epic URL in a prompt means "pickup first" for every MCP client;
+  the full tree is never loaded up front.
+- Task deep links are `/p/<project>/t/<id>`; the `/t/<id>` short form is gone.
+
+## 3.10.0
+
+One verb per testing lane: run your suite, or explore by hand, and vitrinka
+keeps the QA record — task, journeys, verdicts, board, screenshots, bugs.
+
+### Added
+- **`vitrinka run -- <test command>`** — runs the command with the run env set
+  (`VITRINKA_RUN_ID`, `VITRINKA_RUN_DIR`, `VITRINKA_RUN_STARTED_AT`,
+  `VITRINKA_SHOTS=always`), finds the results it left (JUnit XML, a Playwright
+  JSON report, `allure-results/`, wdio reports or a run manifest; declared
+  runners first, else a scan since the start) and publishes them. Exits with
+  the command's exit code; `--dry-run` prints the folded manifest.
+- **`vitrinka usertest start · case · verdict · finish`** — an exploratory
+  session over `snap`: every capture attaches to the open case, `finish`
+  publishes one journey per case with its verdict and shots.
+- **`vitrinka project setup --runners [--check]`** — declares where each
+  detected runner (Playwright · wdio · Jest · Vitest) writes results in
+  `.vitrinka/project.json`; `--check` exits 1 on drift.
+- A run with no task in context lands under the project's rolling
+  **Unplanned runs** epic instead of failing; `run publish` does the same.
+- The run door accepts JUnit XML and Playwright JSON bodies directly
+  (`POST /tasks/{id}/run`, `POST /projects/{project}/run`).
+
+### Changed
+- The `usertest` skill is the two verbs; board mechanics left it. The
+  publisher agent keeps only walkthrough boards.
+
 ## 3.9.1
 
 The feature-lifecycle follow-ups: the QA board and final artifact from the

package/package.json

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