@vitrinka/cli 3.11.0 → 4.1.0

package/CHANGELOG.md

@@ -3,6 +3,75 @@
 `vitrinka update` prints the sections newer than your previous version after
 updating — keep entries short and user-facing.
 
+## 4.1.0
+
+The brainstorm hands itself off: a feature brief the next session reads
+instead of the whole board, one worktree per feature, and a machine ledger
+`doctor` can repair.
+
+### Added
+- **`vitrinka task brief <epic> [--out <file>]`** composes the brainstorm
+  board's `Plan` chapter (chosen takes only) and prints the brief skeleton;
+  the skill fills the prose and re-uploads it as the next version.
+- **`vitrinka task upload <id> <files…> --kind <kind> --hint <text> --version-of <refId>`**
+  attaches typed, hinted files, optionally as the next version of an
+  existing lineage.
+- **`vitrinka task pickup` honours `meta.load`** on refs: `first` leads the
+  READ rail, `on-demand` prints as a `read on demand:` line, `never` hides.
+- **Brainstorming skill**: `deep` level (same flow, bigger budget), spike /
+  bounded / architectural classification before the first question, the
+  feature worktree created at step 1, a vocabulary challenge, and every
+  brainstorm closes with "in which style to implement".
+- **`project setup` picks the project** from the workspace's projects and
+  their declared repositories; **`project link` / `project unlink`** manage
+  a checkout's binding.
+- **`vitrinka doctor` reads the machine ledger** (`projects.<name>.repos[]`
+  in the config) and **`doctor --fix`** repairs machine, server and per-repo
+  drift after one confirm.
+- **`vitrinka dev` seeds a personal workspace** beside the team one.
+
+### Changed
+- `project setup` appends the origin to a non-empty declared repository
+  list instead of leaving it alone.
+- The repo-side `docs` guide gains a `brief` topic (`vitrinka docs brief`).
+
+## 4.0.0
+
+One `--json` shape for ordinary commands, including help, version and doctor.
+An agent reads `ok`, then `data` or `diagnostics`, then `next`.
+
+### Changed (breaking)
+- **`--json` is an envelope**: ordinary commands print
+  `{v: 1, ok, verb, data, diagnostics, next}` on stdout, success and failure
+  alike. What a command printed before is now its `data`; a failure carries
+  one or more `diagnostics` (`code` · `severity` · `detail` · `why` · `fix`
+  · `http_status`) plus `exit_code`, and `next` lists `{do, cmd}` steps.
+  Scripts reading a top-level field (`.url`, `.slug`, `.error`) read
+  `.data.url` / `.diagnostics[0].detail` now.
+- **Misuse is a coded diagnostic, exit 2** — an unknown command, a wrong
+  argument count or a bad flag value answers `unknown_command` /
+  `bad_argument` with the corrected invocation in `fix`. An unknown
+  subcommand no longer prints the group's help page and exits 0.
+- **Every failure carries a `code`** from one closed vocabulary shared with
+  the server (`not_signed_in`, `unreachable`, `not_found`,
+  `gateway_unavailable`, …); an error with no better class is `failed`.
+  A raw library error never reaches you as styled prose under `--json`.
+
+### Added
+- A bare group under `--json` (`vitrinka task --json`) lists its commands
+  as `data.commands` instead of printing help.
+- The server's own error `code`, `detail` and `fix` are read into the
+  diagnostic when the reply carries them.
+- REST errors, including authentication and routing failures, carry a code
+  and recovery instructions. MCP exposes the same object in `structuredContent`.
+- `doctor --json` emits one failure with check results. Permission failures
+  do not suggest repeated login; malformed JSON bodies cannot silently mutate data.
+- Protocol/stream exceptions retain their output: MCP, extension host,
+  child commands via `run`, `listen`, continuous `work watch`, raw `auth token`,
+  completion scripts and interactive UI.
+- Go source builds use module `github.com/henderson-tech/vitrinka`; update
+  custom import paths and `-ldflags -X` references when building from source.
+
 ## 3.11.0
 
 The task is the handoff: a session picks a task up from one bounded view,

package/package.json

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