Crate weave_cli 

Library half of the weave CLI.

The weave binary is the primary consumer, but the two repo-scope engines here — the cross-file binding pass (repo_scope) and the typed patch format (patch) — are also exposed as MCP tools, and an MCP server cannot call into a binary. They therefore live in a library target rather than under src/commands/, which stays the thin argument-parsing shell.

Modules

edit

weave edit: how an agent changes code, addressed by entity.

gitscan

Reading whole trees out of git, for the repo-scope pass.

land

weave land — land a merge, and say for every file git could not merge how much is known about the result.

mergestate

What state a merge is really in, for land --onto / --queue.

onto

weave land --onto <remote>/<branch> — the whole landing: bring the branch’s latest commits onto a shared branch, and publish nothing that has not been checked against the exact commit it is published onto.

patch

weave patch — the WRITE side of the agent contract.

preserve

The publish-time invariant: a merge keeps each side’s changes.

queue

weave land --queue — a landing queue kept in the shared bare repository. Experimental: the protocol and its refs may change.

repo_scope

The repo-scope binding pass — weave’s answer to the per-file driver’s one structural blind spot.

semcheck

weave land --check sem: the merged tree is verified by sem check before anything is published.

wire

The findings wire format, v1.1.0 — serialisable form of crates/weave-mcp/schema/weave-findings.schema.json.

worktree

Verifying the WORKING TREE — the check an agent actually wants.