P2P Engine v0.6.2

P2P Engine 0.6.2 — 2026-09-03

P2P Engine 0.6.2 adds the local half of governed project-authority transfer
and linked WaveKit replicas. A standalone project can transfer canonical
authority to a compatible WaveKit server without changing its stable
project_uuid. The client uses an authenticated, previewed and confirmed
workflow with deterministic bundle/blob upload, an authority fence and
idempotent recovery after timeouts or lost responses.

An authoritative WaveKit project can then be cloned or attached as a local
replica. Each physical copy receives a distinct replica_id; P2P downloads a
revision-bound canonical snapshot and every referenced managed blob, verifies
the complete artifact set in staging and publishes .p2p atomically. Explicit
status, catch-up, recovery, move, register-copy and forensic read-only commands
complete the bootstrap lifecycle.

Credentials remain in the operating-system keyring. Project memory stores only
the non-secret server binding, account reference, authority epoch, applied
revision and cursor. Linked writes remain disabled and offline reads are
explicitly stale until the later durable-replication protocol is available.

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.2/p2p_engine-0.6.2-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.2 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.1. The filesystem adapter remains the
sole supported product backend; SQLite is not included in this release.
Standalone behavior remains local. Transfer, clone and catch-up require a
compatible WaveKit server and do not expose or depend on its persistence
implementation.

The first linked-local release is intentionally read-only for project-domain
mutations. It supports explicit catch-up and recovery; durable incremental
commands, automatic command preflight and realtime wake-ups remain a later
protocol step.

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 tag-triggered release workflow creates GitHub Artifact Attestations for
the wheel, source distribution and checksum file. Verify the wheel with:

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

The release assets are published only from the exact tagged commit after the
source, reproducibility, installed-wheel and cross-platform uv gates pass.