weavatrix 1.17.2 → 1.17.3

package/README.md

@@ -58,7 +58,7 @@ weavatrix mcp .
 ```toml
 [mcp_servers.weavatrix]
 command = "npx"
-args = ["-y", "weavatrix@1.17.2", "mcp", "."]
+args = ["-y", "weavatrix@1.17.3", "mcp", "."]
 ```
 
 Pass an absolute repository path when the Codex process cwd is not the project
@@ -67,7 +67,7 @@ you intend to analyze.
 ### Claude Code
 
 ```sh
-claude mcp add weavatrix -- npx -y weavatrix@1.17.2 mcp .
+claude mcp add weavatrix -- npx -y weavatrix@1.17.3 mcp .
 ```
 
 ### Cursor
@@ -80,7 +80,7 @@ the plugin for the same server name:
   "mcpServers": {
     "weavatrix": {
       "command": "npx",
-      "args": ["-y", "weavatrix@1.17.2", "mcp", "${workspaceFolder}"]
+      "args": ["-y", "weavatrix@1.17.3", "mcp", "${workspaceFolder}"]
     }
   }
 }
@@ -89,14 +89,14 @@ the plugin for the same server name:
 Profiles expose bounded views of the same engine:
 
 ```sh
-npx -y weavatrix@1.17.2 mcp . --profile=all
-npx -y weavatrix@1.17.2 mcp . --profile=code
-npx -y weavatrix@1.17.2 mcp . --profile=seo
-npx -y weavatrix@1.17.2 mcp . --profile=n8n
-npx -y weavatrix@1.17.2 mcp . --profile=dify
-npx -y weavatrix@1.17.2 mcp . --profile=agent
-npx -y weavatrix@1.17.2 mcp . --profile=diagram
-npx -y weavatrix@1.17.2 mcp . --profile=web3
+npx -y weavatrix@1.17.3 mcp . --profile=all
+npx -y weavatrix@1.17.3 mcp . --profile=code
+npx -y weavatrix@1.17.3 mcp . --profile=seo
+npx -y weavatrix@1.17.3 mcp . --profile=n8n
+npx -y weavatrix@1.17.3 mcp . --profile=dify
+npx -y weavatrix@1.17.3 mcp . --profile=agent
+npx -y weavatrix@1.17.3 mcp . --profile=diagram
+npx -y weavatrix@1.17.3 mcp . --profile=web3
 ```
 
 The package contains native binaries for Windows x64/arm64, macOS x64/arm64,
@@ -316,11 +316,11 @@ coding agent
     |
     | MCP over stdio
     v
-weavatrix 1.17.2
+weavatrix 1.17.3
     profile catalog · refresh · watcher · MCP framing
     |
     v
-weavatrix-rust 2.17.1
+weavatrix-rust 2.17.2
     typed graph · analysis · 67 product operations including local CI, n8n, Dify, agent packages, Mermaid, and Web3
 ```
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "weavatrix",
-  "version": "1.17.2",
-  "weavatrixEngineVersion": "2.17.1",
+  "version": "1.17.3",
+  "weavatrixEngineVersion": "2.17.2",
   "description": "Native repository intelligence for coding agents: 67 read-only MCP operations backed by typed evidence graphs, impact, architecture, local CI restrictions, 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.17.2",
+  "version": "1.17.3",
   "websiteUrl": "https://weavatrix.com",
   "packages": [
     {
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "weavatrix",
-      "version": "1.17.2",
+      "version": "1.17.3",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"

package/skill/SKILL.md

@@ -23,8 +23,16 @@ contracts. Do not call it merely because the server is available.
 1. Call `graph_stats` and confirm `repository_context.root` matches the workspace
    you intend. The MCP process is pinned to its launch root; it will not silently
    answer for another repository.
-2. Use `module_map` or `architecture_inventory` for orientation, or
-   `search_code` for a known literal.
+2. For "what is this repository's architecture?", call
+   `architecture_inventory` with no `detail` argument (bounded summary).
+   Explain its packages, component areas, dominant coupling, and limits in
+   your own concise prose; do not paste the tool's JSON as the answer. Use
+   `module_map` for a directory-focused question, or `search_code` for a
+   known literal. Request `architecture_inventory` with `detail:"full"`
+   only when a specific component, edge, or cycle needs source evidence.
+   Use `get_architecture_contract` or `verify_architecture` only when the
+   question is about declared target policy or compliance. A component
+   quotient/union cycle is a candidate, not proof of a runtime cycle.
 3. Pin decisive evidence with `inspect_symbol`, `go_to_definition`,
    `find_references`, `context_bundle`, or `read_source`.
 4. Expand only when needed: `get_dependents` or `change_impact` for risk,
@@ -52,8 +60,10 @@ Do not call `open_repo` "just in case". Cross-repository tools take explicit
 roots in their arguments. Multi-root retarget requires launching with
 `--allow-retarget`.
 
-Prefer `output_format:"text"` and a small `token_budget` for conversational
-work. Use JSON only for automation or retained evidence. Call `rebuild_graph`
+`output_format` controls the MCP envelope, not the amount of detail: `text`
+still contains JSON. Choose each tool's summary/detail or result limits for
+conversational work. Use `token_budget` only as an additional ceiling; it can
+drop evidence arrays. Call `rebuild_graph`
 only when the repository changed before automatic refresh completed or when
 deliberately changing graph mode.
 

package/skill/references/tool-routing.md

@@ -41,7 +41,7 @@ cannot silently switch to another repository. Pass an explicit
 
 ## Quality and architecture
 
-- [`architecture_inventory`](tools/architecture_inventory.md) — Nested observed components, declared memberships, complete edge totals, and typed cycle witnesses without a style label.
+- [`architecture_inventory`](tools/architecture_inventory.md) — Bounded architecture overview by default, with complete edge/cycle-candidate totals; `detail:"full"` gives paged evidence. Explain the overview in prose, not as a JSON dump.
 - [`ci_restrictions`](tools/ci_restrictions.md) — Local GitHub Actions checks and conditional applicability.
 - [`explain_restriction`](tools/explain_restriction.md) — One restriction and its evidence limits.
 - [`find_duplicates`](tools/find_duplicates.md) — Deterministic Type-1/2/3 clone families.

package/skill/references/tools/architecture_inventory.md

@@ -1,7 +1,8 @@
 # `architecture_inventory`
 
 Observed package, nested component, declared-membership, and typed edge
-evidence. No style label or target architecture is inferred.
+evidence. The default is a bounded architecture overview, not a raw graph
+dump. No style label or target architecture is inferred.
 
 ## When to use
 
@@ -16,13 +17,24 @@ the component quotient is reported as architecture, not as symbol recursion.
 
 ## Inputs
 
-- `output_format` (`text`, `json`, or `structured`).
+- `detail`: `summary` (default) or `full`.
+- `max_results` (1–500) and `edge_cursor`: page edges in `full` mode. Supplying
+  either without `detail` implies `full`; neither shrinks the summary.
+- `token_budget`: additional output ceiling; may drop samples or evidence.
+- `output_format` (`text`, `json`, or `structured`) changes only the MCP
+  representation. `text` still contains serialized JSON, not prose.
 - `expected_repository` (optional active-root guard).
 
 ## Minimal call
 
 ```json
-{"name":"architecture_inventory","arguments":{"output_format":"text"}}
+{"name":"architecture_inventory","arguments":{}}
 ```
 
+Turn the returned packages, component paths, dominant coupling, and complete
+edge/cycle-candidate totals into a concise answer in your own words. Never
+present a quotient/union cycle candidate as a proven executable cycle. Ask
+for `{"detail":"full"}` only to inspect a specific edge, component, or
+cycle witness. The full response can be large and paginates edges.
+
 The live MCP `tools/list` schema is authoritative.