joinweave 0.1.3 — compact ownership receipts

joinweave 0.1.3 repairs the ownership-receipt regression in 0.1.2 while preserving the native safety limit, identity and stored data.

npx joinweave@0.1.3

Detailed managed MCP file records now live in a private, SHA256-bound census, keeping the native ownership receipt below its unchanged 64 KiB limit. Recognized 0.1.2 receipts migrate before native service commands. Persisted removal intent supports recovery after interrupted uninstall; modified or unrelated files remain protected.

Native CLI, runtime MCP and all four platform packages remain at 0.1.0. This patch does not release or install Weave Desktop.

Validation: all 60 checks passed with no skips on Depot run 38281000021, including the full registry MCP tree. The exact candidate completed a fresh supervised Linux install, live doctor with three peers, actual persistent MCP initialization/tool listing, stop/start, crash recovery, safe rerun and identity/data-preserving uninstall. Its native ownership receipt was 854 bytes. This candidate flow used the exact local installer archive; separate postpublication registry acceptance is tracked independently.

Archive SHA256: 35628d03da4dd0e49e8b40b4adab5d0706f62631eab558d5faccbb1cf71dffd2.

Qualified application source: cf3181e7f79c609e9a023e20ca69ebf86d15cd10. Signed release operations: cb162109762ce230a144d9678dda7c8cb579b0f9. GitHub-hosted provenance run: 38281608819. The attached qualification, manifest and provenance receipts bind the exact archive bytes; no native binaries were rebuilt for this patch.

For an affected 0.1.2 workspace, retain the same WEAVE_HOME and run npx joinweave@0.1.3 --yes --json. Do not purge identity/data or hand-edit receipts to work around the earlier error. Review any changed-file conflicts; PATH and agent-client changes still require explicit consent.