archprint 0.8.1 → 0.8.3

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # archprint
 
+## 0.8.3
+
+### Patch Changes
+
+- The MCP server is ready for MCP directories. Each tool now has a human-readable title and is marked read-only and non-destructive, so clients can show it as safe to run (the remote `--http` tools are also marked as reaching the internet). The package declares its MCP Registry name, and every release publishes to the official MCP Registry automatically. `archprint scan` now labels each rule group the same way `init` and `recommend` do: dependency hygiene and dependency declaration read "review before enforcing", and circular dependencies read "report only". The README lists example prompts to ask your agent.
+
+## 0.8.2
+
+### Patch Changes
+
+- `archprint init` and `archprint recommend` no longer list circular dependencies under "Enforcing now". Archprint does not write a lint rule for cycles, so nothing was enforcing them. They now appear under a new "Report only" group, which is also recorded as `reportOnly` in `.archprint/config.json`, in `recommend --json`, in the MCP `archprint_recommend` result, and in the README section `init` writes.
+- The README is reorganised so anyone can follow it: a plain-words explanation of what Archprint does and who it is for, the demo recordings and a "try it in your browser" link up front, a section on using it with AI coding agents (with the measured comparison), a short quick start, and a plain explanation of how it decides which rules to trust before the reference material. It also corrects the list of rule families that turn on automatically: dependency declaration is held for review, as the detector table and `init` already said. Circular dependencies are now described as reported rather than enforced, since no lint rule is written for them yet, and the README states precisely what makes generated rules green on your code and what `generate --check` adds.
+
 ## 0.8.1
 
 ### Patch Changes