weavatrix 1.16.1 → 1.16.2

package/README.md

@@ -9,13 +9,18 @@
 
 **Give your coding agent repository evidence before it starts guessing.**
 
-Weavatrix is the native MCP product for repository intelligence. It gives
-Codex, Claude Code, and other coding agents 64 read-only operations over one
-revision-bound evidence graph: impact, architecture, APIs, Git history,
-duplicates, dead code, search, semantic links, temporal memory, exported
-n8n workflows, Dify YAML apps, Agent packages, Mermaid flowcharts, and
-Web3 ABI/consumer impact. Those parsers are domains on Weavatrix
-Core, not new MCP products. See
+Weavatrix answers the questions agents otherwise invent: what breaks if this
+file changes, who consumes this n8n field, whether an MCP schema still
+accepts yesterday’s request, which viem call sites follow an ABI layout
+change, and whether `.weavatrix/architecture.json` still holds. **64
+read-only operations**, one revision-bound graph, no LSP and no prompt pack.
+
+Codex, Claude Code, Cursor, and Grok get impact, architecture, APIs, Git
+history, duplicates, dead code, search, semantic links, temporal memory,
+exported n8n workflows (`n8n_*`), Dify YAML apps (`dify_*`), Agent
+Plugins/Skills/MCP catalogs (`agent_*`), Mermaid flowcharts (`diagram_*`),
+and Web3 ABI/consumer impact (`web3_*`). Those parsers are domains on
+Weavatrix Core, not new MCP products. See
 [n8n](https://weavatrix.com/n8n), [Dify](https://weavatrix.com/dify), and
 [parsers](https://weavatrix.com/parsers).
 
@@ -53,7 +58,7 @@ weavatrix mcp .
 ```toml
 [mcp_servers.weavatrix]
 command = "npx"
-args = ["-y", "weavatrix@1.16.1", "mcp", "."]
+args = ["-y", "weavatrix@1.16.2", "mcp", "."]
 ```
 
 Pass an absolute repository path when the Codex process cwd is not the project
@@ -62,7 +67,7 @@ you intend to analyze.
 ### Claude Code
 
 ```sh
-claude mcp add weavatrix -- npx -y weavatrix@1.16.1 mcp .
+claude mcp add weavatrix -- npx -y weavatrix@1.16.2 mcp .
 ```
 
 ### Cursor
@@ -75,7 +80,7 @@ the plugin for the same server name:
   "mcpServers": {
     "weavatrix": {
       "command": "npx",
-      "args": ["-y", "weavatrix@1.16.1", "mcp", "${workspaceFolder}"]
+      "args": ["-y", "weavatrix@1.16.2", "mcp", "${workspaceFolder}"]
     }
   }
 }
@@ -84,14 +89,14 @@ the plugin for the same server name:
 Profiles expose bounded views of the same engine:
 
 ```sh
-npx -y weavatrix@1.16.1 mcp . --profile=all
-npx -y weavatrix@1.16.1 mcp . --profile=code
-npx -y weavatrix@1.16.1 mcp . --profile=seo
-npx -y weavatrix@1.16.1 mcp . --profile=n8n
-npx -y weavatrix@1.16.1 mcp . --profile=dify
-npx -y weavatrix@1.16.1 mcp . --profile=agent
-npx -y weavatrix@1.16.1 mcp . --profile=diagram
-npx -y weavatrix@1.16.1 mcp . --profile=web3
+npx -y weavatrix@1.16.2 mcp . --profile=all
+npx -y weavatrix@1.16.2 mcp . --profile=code
+npx -y weavatrix@1.16.2 mcp . --profile=seo
+npx -y weavatrix@1.16.2 mcp . --profile=n8n
+npx -y weavatrix@1.16.2 mcp . --profile=dify
+npx -y weavatrix@1.16.2 mcp . --profile=agent
+npx -y weavatrix@1.16.2 mcp . --profile=diagram
+npx -y weavatrix@1.16.2 mcp . --profile=web3
 ```
 
 The package contains native binaries for Windows x64/arm64, macOS x64/arm64,
@@ -117,6 +122,17 @@ same, and a call that names its own `output_format` still wins.
 `json` is the default and keeps the mirror, because a client that ignores
 `structuredContent` would otherwise see an empty result.
 
+### What the new domains actually answer
+
+| Ask | Tool | Honest limit |
+| --- | --- | --- |
+| Will this MCP schema still accept yesterday’s request? | `agent_change_impact` | `string` → `integer` is incompatible. A missing tool in a partial catalog is `unconfirmed`, not removed. |
+| Who calls this ABI after an event layout change? | `web3_impact` | Comment/string “calls” are not consumers. ABI equality is not a live deployment. |
+| Who reads this field in an exported n8n workflow? | `n8n_trace` | Secrets stay off the graph. |
+| Which Dify nodes consume `start_node.query`? | `dify_trace` | Conversation variables are directed edges, not string presence. |
+| Does this Mermaid arrow prove a code call? | `diagram_*` | Arrows are `declared_architecture`, never `Calls`. |
+| Does `.weavatrix/architecture.json` still hold? | `verify_architecture` | Unknown rules fail closed. |
+
 ## What an agent can ask
 
 ```text
@@ -131,6 +147,9 @@ Build the smallest source bundle needed to edit this symbol safely.
 Show me this file as it was two commits ago, without a checkout.
 If I change the email recipient in this exported n8n workflow, who reads it?
 If I change start_node.query in this Dify YAML, which nodes consume it?
+Did this MCP catalog make `id` an integer so old string requests fail?
+Which viem `decodeEventLog` sites still assume the old Deposit layout?
+Is this Mermaid arrow a real call, or only declared architecture?
 ```
 
 ## See it answer
@@ -256,7 +275,7 @@ export in git → existing JSON/YAML parse → typed domain → inventory / trac
 | [Dify](https://weavatrix.com/dify) | `dify_inventory`, `dify_trace`, `dify_context` | Product 1.13.0 |
 | Agent packages | `agent_inventory`, `agent_trace`, `agent_context`, `agent_change_impact` | Product 1.14.0 |
 | Mermaid diagrams | `diagram_inventory`, `diagram_trace`, `diagram_context` | Product 1.14.0 |
-| Web3 integration | `web3_inventory`, `web3_trace`, `web3_impact`, `web3_context` | Product 1.16.1 |
+| Web3 integration | `web3_inventory`, `web3_trace`, `web3_impact`, `web3_context` | Product 1.16.2 |
 
 | Need | Use |
 | --- | --- |
@@ -276,11 +295,11 @@ coding agent
     |
     | MCP over stdio
     v
-weavatrix 1.16.1
+weavatrix 1.16.2
     profile catalog · refresh · watcher · MCP framing
     |
     v
-weavatrix-rust 2.16.1
+weavatrix-rust 2.16.2
     typed graph · analysis · 64 product operations including n8n, Dify, agent packages, Mermaid, and Web3
 ```
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "weavatrix",
-  "version": "1.16.1",
-  "weavatrixEngineVersion": "2.16.1",
+  "version": "1.16.2",
+  "weavatrixEngineVersion": "2.16.2",
   "description": "Native repository intelligence for coding agents: 64 read-only MCP operations backed by typed evidence graphs, impact, architecture, APIs, Git, search, semantics, memory, n8n workflows, Dify apps, agent packages, Mermaid diagrams, and Web3 ABIs.",
   "author": "Sergii Ziborov <sergii.ziborov@gmail.com>",
   "license": "MIT",

package/server.json

@@ -7,14 +7,14 @@
     "url": "https://github.com/Weavatrix/weavatrix",
     "source": "github"
   },
-  "version": "1.16.1",
+  "version": "1.16.2",
   "websiteUrl": "https://weavatrix.com",
   "packages": [
     {
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "weavatrix",
-      "version": "1.16.1",
+      "version": "1.16.2",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"

package/skill/references/tool-routing.md

@@ -112,7 +112,7 @@ engine `weavatrix-rust` 2.14.3.
 
 Local ABI JSON, supplied solc/Foundry artifacts, and static viem/wagmi
 sources only. Not a compiler, RPC client, or wallet. Requires engine
-`weavatrix-rust` 2.16.1.
+`weavatrix-rust` 2.16.2.
 
 - [`web3_inventory`](tools/web3_inventory.md) — List ABIs, artifacts, and static consumers.
 - [`web3_trace`](tools/web3_trace.md) — Walk proven ABI, artifact, and consumer bindings.