P2P Engine v0.6.9

P2P Engine 0.6.9 — 2026-09-09

P2P Engine 0.6.9 corrects the project-structure export lineage projection. The
export service no longer emits the unconditional
legal_attribution_preserved: true boolean in preview, draft-document,
semantic-diff, apply, CLI or MCP results.

That boolean asserted a legal conclusion that portable artifact bytes cannot
establish. Portable attribution remains represented by the concrete publisher,
license and explicit forked_from or previous_release lineage fields that are
actually written to the artifact. P2P Engine does not infer or certify broader
legal compliance from those declarations.

Idempotent replay remains compatible with project-structure export mutation
receipts created by 0.6.8. When an existing receipt contains the obsolete key,
P2P Engine omits it from the returned result without rewriting the receipt.
The correction does not change project state and does not rewrite, migrate or
repack sealed .p2pv artifacts.

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.9/p2p_engine-0.6.9-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.9 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. 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 0.6.8 filesystem projects require no workspace, storage, bundle,
Choice, replica or vertical-package migration. Existing project-structure
export receipts are retained byte-identically. Replaying one may produce a
corrected response shape that omits legal_attribution_preserved; all concrete
lineage and artifact identity fields remain unchanged.

WaveKit should pin and qualify the exact 0.6.9 artifact before consuming the
corrected export projection. It should validate P2P's returned contract rather
than recreate semantic identity, provenance or legal-attribution logic, and it
must continue to preserve sealed artifacts byte-identically.

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

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