@lovinka/vitrinka 1.4.0 → 1.6.0

package/CHANGELOG.md

@@ -0,0 +1,32 @@
+# Changelog
+
+`vitrinka update` prints the sections newer than your previous version after
+updating — keep entries short and user-facing.
+
+## 1.6.0 — 2026-07-08
+
+### Added
+- `vitrinka update` — updates the CLI (git pull in a checkout, `npm i -g` when
+  behind the registry), prints what's new, and refreshes the installed skills
+  and Claude UI wiring.
+- Status-first onboarding: `vitrinka install` now prints a ✓/✗ setup table and
+  handles everything install.sh used to (MCP registration, write token,
+  operator persona, env checks) — asking only for what's missing.
+- `vitrinka uninstall [--purge]` — clean offboarding (skills, shim, completion,
+  Claude wiring, MCP registration; `--purge` also removes token + operator).
+- `vitrinka doctor --fix` — repairs stale skills, a stale/missing shim, a lost
+  MCP registration, and the Claude UI wiring.
+- `vitrinka open [--qr]` — opens the capture root's live board; `--qr` renders
+  a terminal QR code to scan with the iPad.
+- `vitrinka status` — session dashboard: live board, open work queue, and the
+  listener lease for the current repo+branch.
+- Passive update notifier (one dim line, cached daily, npm installs only) and a
+  first-run hint on fully unconfigured machines.
+
+### Removed
+- `install.sh` — the CLI is the installer now: `vitrinka install` (or
+  `node pkg/src/cli.ts install` from a checkout).
+
+## 1.5.0 — 2026-07-08
+
+- project-memory MCP tools + link/board compose vocabulary (pre-changelog release).

package/README.md

@@ -21,10 +21,30 @@ becomes one HTTPS request against the deployed vitrinka Go server.
 # both bins on PATH
 npm i -g @lovinka/vitrinka
 
-# register the MCP server (Claude Code, user scope) — no global install needed
-claude mcp add --scope user vitrinka -- npx -y --package=@lovinka/vitrinka vitrinka-mcp
+# one-command machine setup — status-first onboarding: prints a ✓/✗ table, silently
+# installs the Claude skills bundle (vitrinka + listen, screenshot, artifact,
+# brainstorming) + the /vitrinka:listen command stub + PATH shim + shell completion,
+# then asks [Y/n] only for the missing config-touchers: MCP registration, write
+# token (silent input), operator persona, Claude Code UI wiring.
+# (npm install itself has NO side effects; skills land only via this command or
+# `vitrinka install-skills`.)
+vitrinka install
+
+# later: update the CLI, see what's new, refresh everything a previous install put
+# here (npm i -g @lovinka/vitrinka@latest when behind — or git pull in a checkout —
+# then re-copies the skills bundle + /vitrinka:listen stub and refreshes the
+# Claude UI wiring where it was already consented to; never asks new questions)
+vitrinka update
+
+# health check / repair / clean removal
+vitrinka doctor          # server, token, operator, skills, shim, MCP, UI wiring
+vitrinka doctor --fix    # repairs the repairable (skills, shim, MCP, UI wiring)
+vitrinka uninstall       # removes everything install put here (--purge: token too)
 ```
 
+Registering the MCP by hand (install does this for you when the `claude` CLI is
+present): `claude mcp add --scope user vitrinka -- npx -y --package=@lovinka/vitrinka vitrinka-mcp`
+
 `vitrinka install` also offers (interactive `[Y/n]`, or `--claude`/`--no-claude`)
 to wire the **Claude Code UI** — re-runnable standalone as `vitrinka install-claude`:
 
@@ -34,8 +54,9 @@ to wire the **Claude Code UI** — re-runnable standalone as `vitrinka install-c
   needs Claude Code ≥ 2.1.176).
 - **Statusline segment** — `~/.claude/vitrinka-statusline.sh` wraps your existing
   statusline command (recorded on its `VITRINKA_ORIG=` line) and appends a
-  `🧷 board` OSC 8 link when the session's `.screenshots/.vitrinka` descriptor
-  exists; with no statusline configured it renders a minimal
+  `🧷 <board-url>` segment when the session's `.screenshots/.vitrinka` descriptor
+  exists (plain-text URL — Claude Code strips OSC 8 from statusline output, and
+  terminals cmd+click-linkify visible URLs themselves); with no statusline configured it renders a minimal
   `dir │ branch │ 🧷 board │ model` line itself. Needs `jq`; degrades to
   pass-through without it, and never double-renders a board segment your own
   statusline already prints.
@@ -71,7 +92,7 @@ vitrinka is reachable over the WireGuard mesh — bring the VPN up (or point
 |---|---|---|
 | `VITRINKA_URL` / `VITRINKA_BASE_URL` | `https://vitrinka.lovinka.com` | vitrinka server base URL. `VITRINKA_URL` wins, then `VITRINKA_BASE_URL`; the CLI's `--base` flag overrides both. |
 | `VITRINKA_TOKEN` | — | Bearer write token. Falls back to `~/.config/vitrinka/token`. Required only by the **mutating** tools; read tools work unauthenticated. |
-| `VITRINKA_OPERATOR` | — | Operator persona name. Falls back to `~/.config/vitrinka/operator` (written by `install.sh` onboarding). When set, write calls carry `X-Board-Actor: <name>` so the board credits the operator's machine — agent-authored content (`reply`, `attach_after`) keeps its explicit `claude` attribution. |
+| `VITRINKA_OPERATOR` | — | Operator persona name. Falls back to `~/.config/vitrinka/operator` (written by `vitrinka install` onboarding). When set, write calls carry `X-Board-Actor: <name>` so the board credits the operator's machine — agent-authored content (`reply`, `attach_after`) keeps its explicit `claude` attribution. |
 
 ## MCP tools