weavatrix 0.2.12 → 0.2.14

package/docs/releases/v0.2.12.md

@@ -1,45 +0,0 @@
-# Weavatrix 0.2.12
-
-## Agent workflow routing and cross-repository API clarity
-
-0.2.12 incorporates a second hands-on evaluation across Weavatrix, BranchPilot,
-controller-rest-api and its registered clients. It does not reduce the product to a short list: the
-skill still maps all 38 methods across application understanding, graph views, Health, dependencies,
-dead code, duplicates, coverage, history, endpoints, impact, architecture and Hosted governance.
-
-The skill now makes three high-leverage routing decisions explicit:
-
-- prefer `trace_api_contract` over disconnected per-repository searches when a backend change can
-  affect registered clients;
-- use `change_impact` as a diff-risk classifier that separates additive exports from
-  signature/body/removal risk, runtime/type-only radius and honest coverage evidence;
-- treat `verified_change` as a proof layer around an agent's edit, never a hidden source editor or
-  auto-fix.
-
-The one-symbol refactor workflow now carries exact context, dependents and coverage through the
-post-edit `verified_change` ratchet. The public site also surfaces cross-repository API contract
-tracing as a first-class graph capability rather than hiding it under generic multi-repository mode.
-
-## Worked examples and public benchmark evidence
-
-The README and public site now show four concrete dogfood scenarios instead of relying on feature
-names alone: orienting inside a 1,076-file backend and tracing one of 462 observed routes; proving
-external handler use across three registered repositories; classifying a BranchPilot change before
-editing; and turning Health plus clone evidence into a bounded review queue. The examples preserve
-uncertainty for dynamic URLs, advisory coverage and review-required findings.
-
-The public benchmark section reports reproducible fixture and revision-pinned real-repository
-regression gates with dates, environment, commands and explicit limits. It does not present these
-machine-dependent local measurements as competitor benchmarks. A lightweight CSS motion sequence
-illustrates the graph-to-verdict workflow and respects `prefers-reduced-motion`; no synthetic product
-screenshots are used.
-
-## Compatibility and verification
-
-- Runtime implementation, tool names, schemas and result envelopes are unchanged from 0.2.11.
-- Hosted sync payload v2/v3 and architecture-contract transport are unchanged.
-- Skill inventory: all 38 current methods are routed; 0 missing.
-- Full Node suite baseline: 506 tests, 503 passed, 3 platform skips, 0 failed.
-- Six-language fixture, cross-repository and lifecycle benchmark: `PASS`.
-- Six locally available revision-pinned real-repository baselines: `PASS`.
-- Release metadata, 99-character MCP Registry description and MCPB validation: `PASS`.