rigswig 0.1.3

rigswig is an MCP server now. rigswig mcp speaks newline-delimited JSON-RPC over stdio — the transport a harness's own client launches and owns — so the tools you audit can ask the auditor: what does a session in this repo load, does it pass its budgets, what does an audit find, and what would differ between two checkouts or two harnesses.

Five tools: status (the full harness JSON, with what-if), check (the CI limits and their verdict), audit (ranked findings with fixes), compare (two repos or two harnesses), and tools (harness detection with evidence). Read-only by construction: no write tool, no network from a tool call, and the registration is the same mcpServers row the adapters already read — see docs/MCP.md. The protocol is hand-rolled on serde_json and std; nine wire-level tests spawn the binary and check every message, including that no tool run prints into the protocol.

Also in this release: a Windows path-display fix (an absolute path built with Path::join displayed its platform separator mid-path; every displayed path is forward-slash on every host now).

Install: cargo install rigswig (crates.io has rigswig-core and rigswig at 0.1.3), or npm install -g rigswig / npx rigswig (npm has the six packages at 0.1.3, all with provenance attestations). Verify a tarball: shasum -a 256 -c SHA256SUMS.

Full Changelog: v0.1.2...v0.1.3