@lovinka/vitrinka 1.21.0 → 1.22.0

package/CHANGELOG.md

@@ -3,6 +3,80 @@
 `vitrinka update` prints the sections newer than your previous version after
 updating — keep entries short and user-facing.
 
+## Unreleased
+
+### Fixed
+- `vitrinka tag` read option VALUES as positionals, so
+  `tag add b1 auth --actor alice` sent `["auth", "alice"]` as tag names — and
+  tags autocreate, so routine invocations silently minted junk tags. A flag
+  placed before the verb (`tag --actor x add …`) also fell through to the `ls`
+  default. Both now come from the shared `positionals()` parse the rest of the
+  CLI already uses.
+
+### Changed
+- **`tag merge` and `tag drop` now REFUSE without a TTY unless `--yes` is
+  given** (exit 2). They previously treated "no TTY to ask on" as approval, so
+  they ran unconfirmed in scripts, CI and any redirected shell — `drop`
+  detaches the tag from every board, card and session. **If you script either
+  verb, add `--yes`.**
+
+## 1.21.2 — 2026-07-26
+
+### Added
+- `vitrinka doctor` reports listener leases held by dead watch processes on this
+  machine, and `vitrinka doctor --fix` releases them.
+- `vitrinka extension setup | update | doctor` — install the journey-recorder
+  browser extension from the CLI and keep it current. Updates now happen in
+  place: the popup's "update available" banner is a button that has the CLI
+  download, checksum-verify and swap the release, then reloads the extension
+  into it. `--check` reports without installing; `doctor --fix` re-registers the
+  native-messaging host after a CLI reinstall moves `node` or the CLI.
+- The extension takes its base URL and token from this machine's CLI config on
+  first load, so a fresh install needs no pasting (the options page gains a
+  "Fill from the vitrinka CLI" override). Existing settings are never replaced.
+- **Migrating a hand-unzipped copy:** the extension now pins its id, so the
+  CLI-managed folder is a *different* extension to Chrome. Run
+  `vitrinka extension setup`, load `~/.config/vitrinka/extension`, and remove
+  the old card — a token you pasted by hand does not carry over.
+
+### Changed
+- `vitrinka install` now detects the Chromium browsers on the machine and offers
+  the recorder as a step (`--extension` / `--no-extension`), so re-running it on
+  an already-onboarded machine is how you backfill the extension. An install
+  that already has it silently re-registers the update host, which is also how a
+  browser added since the last run starts working. `vitrinka update` keeps an
+  installed extension current, and the update host is registered for the
+  browsers detected on the machine (falling back to all of them when none is
+  detected, so a fresh box still gets a working host) — so `extension doctor`
+  can now tell you the browser you *use* is unregistered instead of counting
+  four blind writes.
+
+### Fixed
+- A listener could outlive the session that armed it and hold its board's lease
+  **forever**. Claude Code signals the wrapper shell it spawned, so the watch
+  underneath never got the SIGTERM — it was adopted by init and kept renewing
+  its lease, which the TTL cannot reap (the TTL only reaps leases that stop
+  heartbeating). Annotations dispatched on that board then vanished into a
+  process nobody was reading. Three fixes: `/vitrinka:listen` now arms
+  `exec vitrinka watch` so the watch *is* the signalled process; `vitrinka
+  watch` self-terminates if it is ever orphaned, covering exits that deliver no
+  signal at all (agent SIGKILLed, crashed, terminal closed); and it now handles
+  SIGHUP alongside SIGINT/SIGTERM.
+- Release integrity is fail-closed: a feed without a usable SHA-256, or an
+  artifact larger than it advertised, is refused before anything is downloaded
+  or swapped. Previously the checksum was only verified when the field happened
+  to be present, and the whole body was buffered unbounded.
+
+## 1.21.1 — 2026-07-25
+
+### Fixed
+- `/vitrinka:brainstorming` sometimes skipped the decision map — the map was
+  reasoned out but never written, so the round opened straight into a "anything
+  to cut, add, or reorder?" picker whose options referenced decisions you could
+  not see anywhere, expanded output included. The map is now printed as its own
+  message before any question is asked, and the board-mode exemption from
+  printing it only applies once a board actually exists.
+
 ## 1.21.0 — 2026-07-25
 
 ### Added