P2P Engine v0.6.11

P2P Engine 0.6.11 — 2026-10-05

Release metadata and notes are prepared for publication with intended tag
v0.6.11. Preparing these notes does not publish, tag, attest or deploy
artifacts; publication remains a separate owner-controlled action. The release
adds durable machine-facing Choice creation, bounded receipt-backed question
contracts and decided Choice supersession by a decided replacement.

Choice creation uses choice.create (owner-only locally, external root authority),
bounded explicit input and atomic Choice/receipt/existing worker batch persistence.
Exact operation-key replay preserves the same immutable created ID/outcome.
Decided supersession validates explicit identity and replacement state while
preserving lineage and returning the superseded source to no-decision projection.
The old Choice remains identifiable and links to the new decided Choice, which
is the current decision. No additional event ledger or Choice versioning is
introduced. Mutation status retains the specific transition outcome and replay
fingerprint required to recover an applied decision after response loss.

Question reads expose page/next v1 contracts; keyed mutations use exact question
leaf capabilities, revisions, distinct subject/executor and common recovery.
External root and capability-grant attestations are accepted for exact question
leaves. Convergence updates definition plus questions atomically; proposal apply
only reports plan_registered and never writes proposal.md. See
Question machine contract.

Install

Until publication, use verified local artifacts rather than a future download:

Install the local candidate only from its verified wheel path, for example:

uv tool install --managed-python --python 3.12 --no-config /PATH/p2p_engine-0.6.11-py3-none-any.whl

Install the exact release wheel from GitHub only after a separate owner-approved
publication. No 0.6.11 download asset is claimed by this preparation. The current
published 0.6.10 installation instructions remain in INSTALL.

Compatibility

Python >=3.11, workspace schema 4, portable vertical schema 3, package format 1,
CLI envelope v1 and receipt schema 3 remain unchanged. No project migration is
required. Existing local text and unkeyed project-question JSON behavior remains
compatible; hosted JSON cannot fall back to local authority. Proposal revisions
default 1 for legacy questions and increment on touched records.

New Choice create result and question contracts appear in the release inventory.
Hosted MCP typed creation/question parity remains explicitly deferred to MS3;
existing local MCP tools are unchanged. WaveKit activation is an independent
qualification of the exact wheel bytes.
The new publication must be qualified on its actual artifacts; local MS2
checks do not imply cross-platform release, upgrade or rollback qualification.

Checksums

The existing local candidate build emits SHA256SUMS for its wheel and sdist.
The publication workflow will provide a separate SHA256SUMS for the exact
official artifacts. Verify the selected set before installation:

sha256sum --check --ignore-missing SHA256SUMS

Checksums identify bytes, not signatures. Final source notes and the official
commit timestamp can change the build bytes; do not use the earlier local
candidate's checksum as the future release checksum.

Provenance

Preparation does not supply GitHub attestation or publication provenance.
After the reviewed source is committed and pushed to main, the existing
owner-controlled workflow qualifies that exact commit, builds and attests its
artifacts, then creates tag v0.6.11 and the create-only, attested GitHub Release.
Do not create the tag manually: publication refuses an existing tag or release.
Only after publication, verify the downloaded official wheel with:

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

No commit, push, tag, workflow dispatch or publication is performed by this
preparation. Earlier local reproducibility and installed-wheel results remain
identified by their own actual artifact paths and hashes in the implementation
handoff; they are not relabeled as published evidence.