v0.1.5

Weavatrix Refactor 0.1.5

This metadata-only patch completes the 0.1.4 architecture release across every
public distribution surface.

• Keeps the same 11 transactional refactoring tools and strict architecture.
• Fits the official MCP Registry 100-character description boundary without
  weakening the product promise.
• Synchronizes npm and MCP Registry versions and descriptions.

The package remains MIT-licensed. Preview hashes, single-use confirmation,
atomic writes, and rollback behavior are unchanged.

v0.1.3

Weavatrix Refactor 0.1.3

0.1.3 moves the JavaScript refactoring extension to the explicitly named
weavatrix-js host package.

Compatibility

• All runtime, extension, analysis-kit, and local-service imports now resolve
  through weavatrix-js.
• The minimum host dependency is weavatrix-js ^0.3.15.
• The canonical weavatrix npm name is no longer used by this JavaScript
  extension and remains available for the native Rust engine.

No edit-plan schema or write-safety contract changed.

Publication ordering

Publish weavatrix-js 0.3.15 first, then regenerate and verify this package's
lockfile against the registry artifact before publishing 0.1.3.

v0.1.2

Weavatrix Refactor 0.1.2

0.1.2 publishes the complete confirmed rename workflow introduced on the
0.1.1 source tag and pairs it with Weavatrix Core 0.3.14.

Refactor workflow

• Rename plans resolve related declarations and exact references across the
  repository, expose unresolved ambiguity before confirmation, and remain
  preview-only until a single-use confirmation token is supplied.
• apply_edit_plan validates file hashes, ranges, before text, provenance, and
  the write gate before one atomic apply session.
• rollback_last_apply restores the recorded preimage through the same
  hash-verified session boundary.
• Plan producers remain separate from the two write tools, preserving the
  explicit preview, confirmation, apply, and rollback contract.

Core compatibility

The minimum dependency is weavatrix ^0.3.14. Refactor therefore inherits
structured duplicate/audit results, vendored-code filtering, Electron and
node:http precision fixes, faster large-graph aggregation, and Rust Tarpaulin
coverage support without duplicating Core implementation.

The Core remains MIT and read-only. This Apache-2.0 package remains the only
Weavatrix layer allowed to write source files.

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

v0.1.0

Weavatrix Refactor 0.1.0

The first published release of the refactoring layer. weavatrix-refactor is the
only Weavatrix component that writes code, and it sits in the middle of the stack:
weavatrix-online ⊃ weavatrix-refactor ⊃ weavatrix. Install it and you get the
full read-only core plus the tools that turn its proven analysis into applied
edits.

What it adds on top of the core

The read-only core (weavatrix 0.3.12) provides the analysis surface; this
layer's own read-only producers compute and prove edit plans against it, and its
apply tools apply them:

• Plan producers (read-only): rename_symbol (LSP, SQL, or graph-resolved
  by language), rename_related_symbols, change_signature, edit_symbol,
  bulk_replace, and organize_imports emit an applyable
  weavatrix.edit-plan.v1; move_file, move_symbol, and delete_readiness
  emit a review plan / dry-run / verdict you act on directly, not an apply
  envelope. Each edit carries its provenance tier, and only proven tiers are
  applyable.
• Appliers: apply_edit_plan and rollback_last_apply. Both are closed by
  default and open only with WEAVATRIX_ALLOW_SOURCE_EDITS=1, a single-use
  confirm token bound to the previewed plan, and a re-checked file hash. Every
  apply is reversible.

Guarantees carried up from the core

The core stays provably read-only; all writing lives here, behind the write gate.
A plan this layer computed and hash-verified against the core applies here only
if the working tree still matches the hashes it was proven against — otherwise it
fails closed with no partial writes, and rollback converges rather than wedging.

Provenance

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