@codacy/verity-cli 0.31.1-experimental.be74f71 → 0.31.2

package/CHANGELOG.md

@@ -5,6 +5,33 @@ All notable changes to Verity are documented here. This project follows
 
 ## [Unreleased]
 
+**Verity ships as a Claude Code plugin.** `/plugin marketplace add codacy/verity`
+then `/plugin install verity@codacy` gives a working gate with nothing else to
+install — the plugin carries the CLI as a pinned dependency, and Claude Code
+installs and updates it for you.
+
+### 🔌 The plugin
+
+- **Eight skills, namespaced** — `/verity:analyze`, `/verity:status`,
+  `/verity:learn`, `/verity:memory`, `/verity:reflect` are available to Claude
+  directly; `/verity:setup`, `/verity:insights` and `/verity:feedback` are yours
+  to invoke and are not offered to the model at all. The whole plugin adds about
+  500 tokens to a session (`claude plugin details verity`).
+- **All six hooks come from the plugin**, so nothing is written to your
+  `.claude/settings.json`.
+- **One gate decision per turn.** A project carrying both the plugin and the
+  hooks `verity init` used to write no longer reviews each turn twice: when the
+  plugin is present it owns the hooks, and the settings.json copy stands down.
+  `verity init` detects the plugin and removes the duplicate wiring.
+
+### ⚙️ Git-moment gating moved into the project
+
+`verity guard` now reads `.verity/config.json` instead of taking its moments from
+which hook was wired, because a plugin's hooks are the same for everyone. **The
+default gates nothing** — set it with `verity config git-moments commit,push`, or
+answer the question in `verity init`. An explicit `--on` still wins, so existing
+installs are untouched.
+
 **Setup is one command.** `verity init` and `/verity-setup` were two half-flows
 that overlapped — and the overlap was not harmless: init wired the Stop hook,
 then the skill reconciled the hooks to a selection it asked for afterwards,