@codacy/verity-cli 0.32.0-experimental.cc76941 → 0.32.0

package/CHANGELOG.md

@@ -42,12 +42,6 @@ default gates nothing** — set it with `verity config git-moments commit,push`,
 answer the question in `verity init`. An explicit `--on` still wins, so existing
 installs are untouched.
 
-Linked git worktrees inherit the setting from the main checkout: `.verity/` is
-gitignored, so a fresh `git worktree add` had no config of its own and the guard
-there gated nothing while `verity hooks check` said "wired but gating nothing".
-A worktree's own `.verity/config.json`, when present, still wins — including an
-explicit `none` — and `hooks check` names the file it inherited from.
-
 ### 🎯 Setup finishes in one command
 
 - **`verity init` now derives the Standard itself.** When the service has nothing
@@ -259,46 +253,6 @@ with one entry point.
   terminal (Ctrl+D, a pty that ends) falls back to the default instead of
   crashing init between copying the skills and wiring the hooks.
 
-### 🔒 Fixed — four ways the gate could be off while reporting itself on
-
-- **`git add x && git commit` was never reviewed.** A Claude Code hook runs
-  *before* the command, so the index it read had not had the `add` applied:
-  no files, and the gate's "nothing staged" exit — a silent allow, with no
-  trace that a commit had gone unreviewed. It is the shape an agent writes by
-  default, so it was most of the pre-commit gate's coverage. The gate now works
-  out what the command will stage, using git's own pathspec matching, and
-  handles `git commit -a`. Where it cannot — a pathspec the shell expands,
-  `git add -p` — it says so and lets the commit through **loudly** rather than
-  reviewing a set it guessed at.
-- **Uninstalling the Claude Code plugin left projects with no gate at all.**
-  Whether the plugin owned a project's hooks was decided by whether its install
-  directory existed — and that directory survives an uninstall. Every project
-  the plugin had ever run in went on standing its own hooks down for a plugin
-  that was gone. Ownership now comes from Claude Code's install registry, and
-  `verity init` clears the stale marker.
-- **`verity init` now says which mode it is in before it acts on it** — the
-  plugin's hooks or this project's own — with the install it found and
-  `--no-plugin` to overrule it. It does two opposite things depending on that
-  answer, and it used to make the choice silently.
-- **A repository can no longer switch the gate off by shipping a file.**
-  Ownership was claimed by `.verity/.plugin-active`, which is a file inside the
-  project. One naming any directory that happened to exist disabled every hook
-  in that project. An install Claude Code cannot vouch for is now ignored.
-- **`verity status` and `verity doctor` agree with `verity hooks check`.** Under
-  the plugin both used to report "Stop: off" and tell you to install hooks that
-  were firing on every turn. All three read one answer now, and it is correct
-  from a subdirectory too.
-- **A commit gate on a linked worktree gates what the main checkout gates.**
-  `.verity/config.json` is machine-local, so every `git worktree add` started
-  with no moments and reviewed nothing.
-- **A verdict the client does not understand is no longer rendered as a pass.**
-  An absent or unrecognised gate decision — a truncated response, a proxy error
-  page — reached the "✓ PASS" line. It is reported as unreviewed.
-- **`verity hooks install --moments <typo>` no longer removes every gate.**
-  Unrecognised moments were dropped, so a misspelling reconciled to nothing and
-  reported success. It is an error now; `--moments none` turns them off on
-  purpose.
-
 ## [0.31.3] — 2026-09-03
 
 **After a rebase, Verity reviewed the wrong code.** When a branch was rebased