P2P Engine v0.6.4

P2P Engine 0.6.4 — 2026-09-05

P2P Engine 0.6.4 completes the first online lifecycle and recovery model for
linked-local WaveKit projects. Owners can suspend and resume a replica,
detach a verified standalone project with a new identity and explicit lineage,
create a new remote project from local state, publish immutable project
snapshots, remove only the local replica, archive or restore the remote project,
and perform receipt-gated remote deletion without creating dual writers.

Linked replicas now verify project and replica identity, authority epoch,
confirmed revision and canonical semantic/blob digests before synchronization.
Formatting-only changes, Git state and valid adapter-owned transient bytes do
not create false drift. Semantic divergence, identity mismatch, corruption and
interrupted local operations fail closed before blind catch-up or mutation.

The owner can inspect bounded logical findings, preserve a verified forensic
archive and rebuild the local replica atomically from a complete authoritative
WaveKit snapshot. When the entire difference is exactly one supported domain
change, P2P can preview and explicitly apply project.domain.set or
project.domain.clear through the ordinary WaveKit command, receipt and feed
path. Unknown differences remain unsupported. Raw local YAML, database pages,
credentials and Git data are never uploaded as reconciliation evidence.

MCP exposes only sanitized lifecycle, publication and drift inspection. Detach,
delete, rebuild and reconciliation apply remain owner-confirmed CLI operations.
Generated agent instructions tell agents to stop linked writes on drift and
request governed recovery instead of editing .p2p directly.

Install

Install the exact release wheel from GitHub with uv-managed Python:

uv tool install --managed-python --python 3.12 --no-config \
  https://github.com/BINARYA/p2p-Engine/releases/download/v0.6.4/p2p_engine-0.6.4-py3-none-any.whl

Run uv tool update-shell only if uv reports that its tool binary directory is
not on PATH. Installing or replacing uv, Python or P2P Engine remains an
explicit owner action.

Compatibility

Version 0.6.4 keeps requires-python >=3.11, workspace schema 4, portable
vertical schema 3, canonical bundle v1 and the p2p-cli/v1 JSON envelope.
Python 3.12 is the release-qualified runtime. The same candidate wheel is
qualified on Linux x86-64, macOS x86-64, Windows x86-64 and macOS ARM64.

Existing current-schema filesystem projects remain valid and require no
storage or workspace migration from 0.6.3. The filesystem adapter remains the
sole supported product backend; SQLite is not included. Standalone projects
continue to use local backup, restore and workspace recovery without WaveKit.

Linked lifecycle, durable replication and drift reporting require a compatible
WaveKit server advertising their negotiated capabilities. Older servers fail
capability negotiation rather than accepting an unsupported transition or
reconciliation request. Offline linked mutations remain outside this release.

Checksums

The GitHub Release contains SHA256SUMS for the exact wheel and source
distribution. Verify downloaded artifacts before installation:

sha256sum --check --ignore-missing SHA256SUMS

Checksums prove downloaded-byte identity; they are not signatures.

Provenance

The explicit on-demand release workflow qualifies the exact main commit,
creates GitHub Artifact Attestations and only then creates tag v0.6.4 and the
immutable GitHub Release. Verify the wheel with:

gh attestation verify p2p_engine-0.6.4-py3-none-any.whl \
  --repo BINARYA/p2p-Engine

The published assets are the same candidate bytes that pass source,
reproducibility, installed-wheel and cross-platform uv gates.