@codacy/verity-cli 0.33.2 → 0.33.3-experimental.03bb89a

package/CHANGELOG.md

@@ -64,6 +64,32 @@ installs are untouched.
   which is the ordinary case for someone whose first Verity install *is* the
   plugin.
 
+## [0.33.3] — 2026-09-24
+
+**The knowledge seed runs once per project, not once per checkout.**
+
+- **`verity memory seed` and the analyze auto-seed no longer re-seed a project
+  that is already seeded.** The old "already seeded" check looked for a file the
+  server never writes (`domain/project-overview.md`; nodes are named
+  `n{seq}-{slug}.md`), so it never matched, and an empty, not-yet-pulled
+  `.verity/memory/` in a fresh clone or worktree read as "never seeded". Every
+  new checkout posted the whole batch again and the server recorded every copy.
+  One project reached 13,497 nodes, 11,214 of them copies of 38 seed titles, and
+  every analyze for it died on request size (HTTP 546, VRT-243). The CLI now
+  checks the frontmatter of what is on disk, then asks the server which seed
+  titles the project has, and posts only the titles that are missing — so a
+  seed that only half landed is completed, and a seeded project is never
+  re-posted.
+- **The server refuses to record the same seed twice.** Posting a seed node whose
+  title and body the project already carries returns the existing node
+  (`200`, `deduplicated: true`) instead of minting another. This holds for old
+  CLIs, cleared markers and parallel worktrees alike. A seed whose body changed
+  (the README was edited) is still a new node, and an archived seed can be
+  recorded again.
+- `verity memory seed` reports nodes that already existed apart from nodes it
+  created, and `--force` re-materializes the existing nodes locally rather than
+  duplicating them.
+
 ## [0.33.2] — 2026-09-23
 
 **Which build is gating, said out loud.**