@lovinka/vitrinka 1.17.0 → 1.20.0

package/CHANGELOG.md

@@ -3,6 +3,64 @@
 `vitrinka update` prints the sections newer than your previous version after
 updating — keep entries short and user-facing.
 
+## 1.20.0 — 2026-07-23
+
+### Changed
+- All output now lives under one `.vitrinka/` home in the target repo:
+  `.vitrinka/screenshots/` (was `.screenshots/`), `.vitrinka/artifacts/<slug>/`
+  (was `.artifacts/`), plus `.vitrinka/scratch/<topic>/` as the sanctioned spot
+  for ad-hoc session output. Legacy roots auto-migrate the first time a command
+  touches them; explicit `--root`/`--from` paths are respected as given.
+
+### Added
+- `vitrinka tidy [--yes] [--all]` — report-first sweep of legacy roots and
+  shot-shaped repo-root litter (`.screenshots-<topic>/`, loose `shot-*.png`)
+  into `.vitrinka/`; `--all` also moves loose images and `.aud_*` text litter.
+  Git-tracked files are never touched.
+- Plugin skills `/vitrinka:annotations` + `/vitrinka:answers` — manual MCP
+  fallback drains for when a "Send to Claude" dispatch doesn't reach the
+  session (annotation work queue / durable question answers).
+
+## 1.19.0 — 2026-07-23
+
+### Added
+- `vitrinka setup-project` — the repo onboarding wizard (clack-styled TUI, the
+  pkg's first runtime deps: `@clack/prompts` + `picocolors`). One front door for
+  everything a repo needs before the editor and board @ autocomplete work:
+  machine-install gate (offers `install` inline when the machine isn't
+  onboarded), project name + registry record, file/route index push (verified),
+  component-index with auto-detected candidate dirs, desktop-app check, and an
+  optional hello board. Status-first and idempotent — re-runs refresh the cheap
+  bits and only prompt for what's missing; `--yes`/non-TTY takes every default.
+- `edit` and `status` print a one-line hint toward `vitrinka setup-project`
+  while the repo has never been indexed.
+
+## 1.18.0 — 2026-07-21
+
+### Added
+- `vitrinka edit [path]` — focus the resident Vitrinka.app editor on a file or
+  project via the `vitrinka://edit?path=…` deep link (`--print` emits only the
+  URL; when the app isn't installed it prints an install hint). The instant
+  editor's CLI entry point.
+- Automatic project registry: `edit`, `status`, `watch`, and `board-from-set`
+  now record `{project → main-worktree path}` to
+  `~/.config/vitrinka/projects.json` as a side effect, so the desktop editor
+  auto-discovers your live checkouts with zero extra UX. Best-effort — a write
+  failure never breaks the command.
+- `compose_board` accepts kind `"artifact"` — a sandboxed self-contained HTML
+  card straight from a compose batch: `{html}` full document or
+  `{body, runtime: "tw4"}` markup-only (server inlines the Tailwind v4
+  runtime; dramatically cheaper). Up to 8 MiB inline.
+
+### Changed
+- `compose_board`'s card schema is slim: the tool description now carries the
+  kind index + quick shapes only; per-kind payload contracts live in the
+  vitrinka plugin skills (the publish skill's `references/card-kinds.md` is
+  the index). Unknown kinds still 400 with the full allowed list.
+- `vitrinka import` (and `POST /import`) replies with a compact per-card
+  summary (`{id, elemNo, kind, title, counts, section?}`); pass `--verbose`
+  (API: `?verbose=1`) for the full card JSON.
+
 ## 1.17.0 — 2026-07-20
 
 ### Added

package/README.md

@@ -52,19 +52,6 @@ to wire the **Claude Code UI** — re-runnable standalone as `vitrinka install-c
   renders a clickable **🧷 board** badge in Claude Code's footer whenever a
   `/boards/` URL appears in the conversation (clickable in every terminal;
   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-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.
-- **Session-start board link** — `~/.claude/hooks/vitrinka-board-link.sh`, a
-  `SessionStart` hook that prints the repo's live board URL into session
-  context at start, so the clickable footer badge exists from message one
-  (the statusline URL isn't clickable in every terminal). Silent no-op in
-  repos without a `.screenshots/.vitrinka` descriptor; needs `jq`.
 - **App badge** (only when Vitrinka.app is installed) — a second
   `footerLinksRegexes` entry that renders **⧉ app** next to the board badge;
   its `vitrinka://` deep link opens the same board in the desktop app
@@ -77,11 +64,23 @@ to wire the **Claude Code UI** — re-runnable standalone as `vitrinka install-c
 flag file instead of probing `/Applications` themselves — `vitrinka open` uses
 it to open boards in the app (pass `--browser` to force the browser).
 
+**Instant editor** — `vitrinka edit [path]` focuses the resident app on a file or
+project via the `vitrinka://edit?path=…` deep link (`--print` emits only the URL).
+Whenever a command already knows the repo — `edit`, `status`, `watch`,
+`board-from-set` — it records `{project → main-worktree path}` to
+`~/.config/vitrinka/projects.json`, so the desktop editor auto-discovers your live
+checkouts with no extra step (it enumerates worktrees itself via `git worktree list`).
+
 All steps are idempotent — re-runs detect the wiring and no-op. To remove:
-delete `~/.claude/vitrinka-statusline.sh` and `~/.claude/hooks/vitrinka-board-link.sh`,
-restore `statusLine.command` in `~/.claude/settings.json` to the `VITRINKA_ORIG`
-value (or drop the key), and remove the `footerLinksRegexes` entry whose pattern
-contains `/boards/` plus the `hooks.SessionStart` entry running `vitrinka-board-link`.
+drop the `footerLinksRegexes` entries whose pattern contains `/boards/` from
+`~/.claude/settings.json` (or run `vitrinka uninstall`).
+
+The old **statusline segment** and **session-start board-link hook** were
+retired (docs/specs/2026-07-20-menubar-tray-decisions.md): active-board
+visibility now lives in the desktop app's **menu bar tray** (`apps/desktop`),
+which shows the boards with a live listener lease on this machine. `vitrinka
+install`/`update`/`uninstall` clean the legacy wrapper + hook off existing
+installs and restore your original `statusLine.command`.
 
 For Claude Desktop or any other MCP client, add the equivalent entry by hand: