weavatrix 0.2.10 → 0.2.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/releases/v0.2.11.md +23 -0
- package/package.json +2 -2
- package/docs/releases/v0.2.10.md +0 -53
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
# Weavatrix 0.2.11
|
|
2
|
+
|
|
3
|
+
## MCP Registry publication hotfix
|
|
4
|
+
|
|
5
|
+
0.2.11 is the immutable follow-up to 0.2.10. The 0.2.10 npm package published successfully, but
|
|
6
|
+
the official MCP Registry rejected its expanded server description because that field exceeded the
|
|
7
|
+
Registry's 100-character limit. This patch shortens only the Registry summary while preserving the
|
|
8
|
+
broad product positioning across the package, MCPB, skill, README and public site. The release
|
|
9
|
+
verifier now enforces the same 1-100 character boundary before a tag can publish.
|
|
10
|
+
|
|
11
|
+
The runtime is otherwise the verified 0.2.10 release: 38 graph-backed methods for fast application
|
|
12
|
+
understanding, Health, dependencies, dead-code and duplicate review, history, endpoint and impact
|
|
13
|
+
tracing, proof-carrying changes, target-architecture ratchets and explicit Hosted governance. Its
|
|
14
|
+
Java receiver-aware call resolver and product-code-only architecture starter are unchanged.
|
|
15
|
+
|
|
16
|
+
## Compatibility and verification
|
|
17
|
+
|
|
18
|
+
- Tool names, input schemas, result envelopes and Hosted sync payload v2/v3 remain unchanged.
|
|
19
|
+
- Full Node suite: 506 tests, 503 passed, 3 platform skips, 0 failed.
|
|
20
|
+
- Six-language, cross-repository, framework and MCP lifecycle benchmark: `PASS`.
|
|
21
|
+
- Six available real-repository baselines: 6/6 `PASS`.
|
|
22
|
+
- Repo Lens portable analyzer parity: 21/21 methods present in the default offline profile.
|
|
23
|
+
- Release metadata, MCP Registry description length and MCPB manifest validation: `PASS`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "weavatrix",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.11",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Local repository intelligence MCP for AI coding agents: reusable architecture graph for fast application understanding, Health, dead code, clones, history, blast radius and architecture safeguards.",
|
|
6
6
|
"author": "Sergii Ziborov <sergii.ziborov@gmail.com>",
|
|
@@ -26,7 +26,7 @@
|
|
|
26
26
|
"skill",
|
|
27
27
|
"scripts/run-agent-task-benchmark.mjs",
|
|
28
28
|
"docs/agent-task-benchmark.md",
|
|
29
|
-
"docs/releases/v0.2.
|
|
29
|
+
"docs/releases/v0.2.11.md",
|
|
30
30
|
"README.md",
|
|
31
31
|
"SECURITY.md",
|
|
32
32
|
"LICENSE"
|
package/docs/releases/v0.2.10.md
DELETED
|
@@ -1,53 +0,0 @@
|
|
|
1
|
-
# Weavatrix 0.2.10
|
|
2
|
-
|
|
3
|
-
## Broad graph workflows without losing graph depth
|
|
4
|
-
|
|
5
|
-
0.2.10 is a graph-quality, positioning and agent-routing patch. It does not narrow Weavatrix to text search, a
|
|
6
|
-
single blast-radius tool, or three fixed workflows. The package, MCP registry metadata, portable
|
|
7
|
-
MCPB, skill, README and public site now describe one reusable graph exposed through 38 methods and
|
|
8
|
-
many task-specific projections: module/community/hub navigation, exact symbols and paths, local and
|
|
9
|
-
cross-repository API flow, symbol/diff impact, structural and behavioral history, Health,
|
|
10
|
-
dependencies, vulnerability evidence, dead code, clones, coverage, hot paths, proof-carrying change
|
|
11
|
-
verification, intended-architecture ratchets, local multi-repository work and explicit Hosted
|
|
12
|
-
governance.
|
|
13
|
-
|
|
14
|
-
The skill's intent router now maps each independent scenario to the smallest sufficient graph view or
|
|
15
|
-
analysis before lower-level source search. `module_map` is explicitly the first unfamiliar-repository
|
|
16
|
-
orientation view, `run_audit` is the core production-first Health review, and `verified_change` is
|
|
17
|
-
explicitly the pre-commit proof-carrying safeguard. Text search remains a useful source check, not the
|
|
18
|
-
product center.
|
|
19
|
-
|
|
20
|
-
## Java call graph and Repo Lens baseline
|
|
21
|
-
|
|
22
|
-
- Java field, parameter, local and static receiver types now resolve project-internal cross-file
|
|
23
|
-
method calls. Overloads are selected by argument arity; ambiguous methods and external or
|
|
24
|
-
same-basename impostor types fail closed. Call-site lines remain available to bounded context and
|
|
25
|
-
endpoint traces, while hub ranking continues to count unique neighbors rather than occurrences.
|
|
26
|
-
- A release regression test now asserts that the default offline catalog retains all 21 portable
|
|
27
|
-
repository-analysis methods inherited from Repo Lens. Its Electron-only `app_action` and
|
|
28
|
-
`app_job_status` process-control bridge is not misrepresented as an analyzer method: rebuild,
|
|
29
|
-
audit, advisory refresh, duplicate review and coverage generation/mapping retain direct bounded
|
|
30
|
-
MCP paths, while the persistent Electron job journal remains app-specific orchestration.
|
|
31
|
-
- The skill routes every one of the 38 current methods into a concrete scenario, so graph, history,
|
|
32
|
-
Health, duplicates, dead code and architecture governance remain first-class product surfaces.
|
|
33
|
-
- The unconfigured-architecture starter now proposes product-code territories only: tests, docs,
|
|
34
|
-
benchmarks, generated files and repository configs are filtered out, while direct source-root
|
|
35
|
-
files are grouped without overlapping deeper modules. It remains a source-free owner-review
|
|
36
|
-
proposal and is never saved or enforced automatically.
|
|
37
|
-
|
|
38
|
-
## Compatibility and data boundary
|
|
39
|
-
|
|
40
|
-
Tool names, MCP schemas, result envelopes and Hosted sync payloads are unchanged. Java graph nodes
|
|
41
|
-
and edges gain additive local `parameter_count` and `javaResolution` evidence; existing readers can
|
|
42
|
-
ignore those fields, and the Hosted payload allowlist remains unchanged. The default profile still
|
|
43
|
-
exposes 34 local tools and no HTTP tools. Hosted remains separately opt-in, preview-confirmed and
|
|
44
|
-
wire-compatible with payload v3.
|
|
45
|
-
|
|
46
|
-
## Verification
|
|
47
|
-
|
|
48
|
-
- Full Node suite: 506 tests, 503 passed, 3 platform skips, 0 failed.
|
|
49
|
-
- Six-language, cross-repository, framework and MCP lifecycle benchmark: `PASS`.
|
|
50
|
-
- Six available real-repository baselines, including the Java call-graph case: 6/6 `PASS`.
|
|
51
|
-
- Release metadata consistency and JSON syntax: `PASS`.
|
|
52
|
-
- Repo Lens portable analyzer parity: 21/21 methods present in the default offline profile.
|
|
53
|
-
- Hosted API and sync-payload schemas are unchanged.
|