P2P Engine v0.6.6

P2P Engine 0.6.6 — 2026-09-06

P2P Engine 0.6.6 makes Choice definitions immutable and gives every Choice an
explicit one-way terminal lifecycle. It resolves
BINARYA/p2p-Engine#7
without coupling Choice state to proposal lifecycle or changing the selected
filesystem storage architecture.

New Choices require a complete Problem and Context and store a deterministic
digest of the immutable decision frame. options.yml now contains definition
data only: deciding a Choice no longer rewrites option status. The selected
option and terminal evidence live in the authoritative lifecycle.yml record.

An open Choice can transition exactly once to decided, withdrawn or
superseded. These transitions share one owner-governed preview/apply service,
durable idempotency receipt, atomic filesystem mutation and recovery path. A
superseded Choice records one authoritative replacement reference; inverse
lineage is derived without modifying the replacement Choice. Active blockers
are retired atomically while their history remains readable.

CLI and local MCP expose equivalent transition semantics. MCP apply remains
single-use-consent gated. Discovery, next actions, project assessment,
specification blockers, registries, decision-context, context packets, vertical
memory and generated agent instructions now agree that terminal Choices are
history rather than active decision debt.

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.6/p2p_engine-0.6.6-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.6 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 0.6.5 filesystem projects remain readable and require no workspace,
bundle, storage or replica migration. Legacy Choices are not rewritten during
reads: they remain explicitly unsealed, existing decided Choices are terminal,
and incomplete open legacy frames may be withdrawn or superseded but not
decided.

The old one-step p2p choice decide behavior is intentionally removed. Without
a preview token the command only previews; apply requires the matching token
and --confirm. There is no supported Choice edit, reopen or re-decide
operation. If the decision frame changes, create a new Choice and optionally
supersede the old one. Proposal lifecycle remains independent.

WaveKit must update its exact wheel pin and fixture manifest to 0.6.6 before
using this runtime. Exposing the new Choice lifecycle through WaveKit HTTP, MCP
or UI is a separate server change; installing the wheel alone does not add
those server surfaces.

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

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