# Weavatrix Online 0.2.0

Online becomes the top of the layered stack: `weavatrix-online ⊃
weavatrix-refactor ⊃ weavatrix`. It now composes the **refactor** layer
in-process, not just the read-only core, so a single install of Weavatrix Online
exposes every tool in the stack — the 34 read-only core tools, the 11 refactor
tools (9 plan producers plus `apply_edit_plan` / `rollback_last_apply`), and
Online's own 5 network tools — for a combined surface of 50 tools.

## What changed

- **Composes the refactor layer.** `weavatrix-refactor` is now a direct
  dependency (`^0.1.2`) and its extension is loaded in-process ahead of Online's
  own extension: `loadExtensions: [refactorExtension(), createOnlineExtension()]`.
  Online users get the full preview → confirm-token → apply → rollback
  refactoring flow without installing anything else.
- **Carries the paired core fixes.** The minimum core is `weavatrix ^0.3.14`,
  so Online includes structured duplicate/audit results, production-first
  vendored filtering, faster large-graph aggregation, precise Electron and
  `node:http` discovery, and Rust Tarpaulin coverage.
- **Unchanged Online surface.** The five network tools (`online_status`,
  `refresh_advisories`, `pull_architecture_contract`, `preview_sync`,
  `sync_graph`) and their destination policy are exactly as in 0.1.0. Nothing
  leaves the machine without a local preview and an explicit confirmation token.
- The write gate is inherited from the refactor layer:
  `apply_edit_plan` / `rollback_last_apply` still require
  `WEAVATRIX_ALLOW_SOURCE_EDITS=1` and a single-use confirm token.

## Layer boundaries preserved

The MIT core stays read-only and separately versioned; the MIT refactor
layer stays the only writer; Online adds only outbound capability on top. Each
lower layer keeps its own license and version history — Online never forks or
relicenses them.

## Provenance

Published from tag `v0.2.0` with npm provenance (SLSA) and mirrored to the
official MCP Registry as `io.github.sergii-ziborov/weavatrix-online`.