P2P Engine v0.6.7

P2P Engine 0.6.7 — 2026-09-07

P2P Engine 0.6.7 exposes complete, bounded and versioned Choice read contracts.
It corrects the mismatch in 0.6.6 where generated WaveKit instructions
advertised p2p choice list --format json and
p2p choice show CHOICE-XXX --format json, but the installed CLI did not
accept those options.

choice list now returns p2p-choice-list/v1 and choice show returns
p2p-choice-detail/v1, both inside the existing p2p-cli/v1 envelope. The
semantic projection is shared by CLI and MCP, deterministic, backend-neutral
and free of physical storage paths. List items and detail relations use
explicit pagination with a default limit of 50, a maximum of 100 and stable
continuation metadata.

Choice detail includes the complete immutable Problem, Context, Governance
Boundary and ordered options together with lifecycle, integrity, typed
selection, terminal evidence and supersession relations. Legacy incomplete
Choices remain explicitly legacy and unsealed; reads do not migrate or rewrite
them.

The existing MCP choices and choice keys remain available as deprecated
compatibility aliases. New consumers should use the normative choice_list and
choice_detail keys. Choice definitions and terminal lifecycle semantics are
unchanged: there is still no edit, reopen or re-decide operation, and proposal
decisions remain independent.

Release qualification now associates advertised worker commands with explicit
classifications. Choice cases are stored as validated argument arrays in the
candidate wheel and executed without a shell against empty, open, decided,
withdrawn, superseded, paginated and missing-Choice fixtures. A nonexistent
advertised option or wrong nested contract fails the release gate.

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.7/p2p_engine-0.6.7-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.7 keeps requires-python >=3.11, workspace schema 4, portable
vertical schema 3, canonical bundle v1 and the p2p-cli/v1 transport 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 0.6.6 filesystem projects require no workspace, storage, bundle,
Choice or replica migration. The five Choice definition/lifecycle/transition
contract versions from 0.6.6 remain unchanged; 0.6.7 adds the two distinct read
contract dimensions.

WaveKit must pin and qualify the exact 0.6.7 artifact before consuming the new
contracts. Installing the wheel does not by itself enable Choice projection,
authorization, concurrency, audit, HTTP, MCP or UI behavior in WaveKit; that
product integration remains a separate approved change.

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

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