P2P Engine v0.6.10

P2P Engine 0.6.10 — 2026-09-09

P2P Engine 0.6.10 restores convergence across every public and durable
p2p-project-structure-export-result/v1 recovery surface. Direct apply,
project-structure export markers, schema-3 mutation receipts, generic mutation
status, CLI JSON and idempotent replay now expose the same structured semantic
identity for one logical export result.

New export markers and receipts persist semantic_identity alongside the
legacy scalar semantic_checksum. They also retain the top-level coordinate
alias and the receipt authority-context digest. Recovery validates the scalar
and structured identities fail-closed and rejects contradictions.

Existing 0.6.8 and 0.6.9 receipts remain readable without migration or
rewriting. When their result contains only semantic_checksum, P2P Engine
derives the established p2p-vertical-semantic-checksum/v1 SHA-256 identity in
memory. Generic mutation status also omits the obsolete
legal_attribution_preserved field from legacy export results, matching direct
apply and replay.

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.10/p2p_engine-0.6.10-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.10 keeps requires-python >=3.11, workspace schema 4, portable
vertical schema 3, package format 1, canonical bundle v1, registry protocol v2,
the p2p-cli/v1 transport envelope, semantic-checksum v1 and portable-
provenance v1. No project, workspace, receipt or portable artifact migration is
required.

The correction does not modify, migrate or repack sealed .p2pv artifacts.
Authority remains represented by the direct result or mutation-status wrapper;
transport-specific mutation evidence is not fabricated during recovery.

WaveKit should pin and qualify the exact 0.6.10 artifact before consuming the
corrected recovery result. It should validate P2P's returned contract rather
than reproduce semantic identity, provenance or recovery logic.

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.10 and the
create-only, attested GitHub Release. Verify the wheel with:

gh attestation verify p2p_engine-0.6.10-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.