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.

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.

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.

P2P Engine v0.6.8

P2P Engine 0.6.8 — 2026-09-08

P2P Engine 0.6.8 makes portable vertical identity, provenance and artifact
lifecycle semantics explicit. It completes the work tracked in GitHub issues
#8 through #11 without changing the established meaning of existing 0.6.7
semantic checksums.

The new p2p-vertical-semantic-checksum/v1 contract names the semantic
projection and canonical serialization frozen from the official 0.6.7
baseline. Static golden vectors cover projection, defaults, ordering,
null/boolean handling, Unicode, dependencies, profiles, modules, sections,
questions, rubrics, artifacts, manifest and canonical bytes. Regression tests
compare against those reviewed static values rather than calculating expected
digests with the implementation under test.

Registry protocol v2 remains backward-compatible. A legacy
semantic_checksum by itself is interpreted as semantic-checksum v1 using
SHA-256. semantic_identity is additive and optional. When both forms are
present they must identify the same digest; contradictions and unsupported
contract/algorithm combinations fail closed. Existing published registry-v2
release semantics are not rewritten.

Example contents are explicitly documentary under semantic v1. The frozen v1
projection continues to include example paths but not their contents. Changing
example bytes therefore changes artifact SHA-256 without changing semantic-v1
identity when the path is unchanged. This deliberate compatibility rule does
not introduce a semantic v2 or alter immutable release coordinates.

The new p2p-vertical-portable-provenance/v1 projection separates facts an
artifact can establish autonomously from host-owned context. Artifact and
semantic identities are calculated from available content. Lineage and
dependency relations remain declarations stored in the artifact; a referenced
dependency target identity becomes verified only when the target content is
available and matches. Registry trust, moderation, uploader identity, review,
audit and WaveKit-specific context remain outside the portable contract.

Artifact lifecycle documentation now states the boundary precisely: an
immutable .p2pv is the lossless representation of the portable artifact
layer. Byte-identical copying preserves the artifact and all declarations it
actually contains, and permits recalculation of both identities. It does not
reconstruct draft state, arbitrary host-side source_attribution, registry
state, audit, review, uploader, timestamps or WaveKit context. Existing sealed
artifacts are inspected and used directly; editing requires an explicit
clone/derive transition. No exact-import command or offline admission
capability was added.

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.8/p2p_engine-0.6.8-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.8 keeps requires-python >=3.11, workspace schema 4, portable
vertical schema 3, package format 1, canonical bundle v1, registry protocol v2
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.7 filesystem projects require no workspace, storage, bundle,
Choice, replica or vertical-package migration. Semantic checksum v1 reproduces
the 0.6.7 behavior exactly. The optional structured registry identity and
portable provenance projections are additive; legacy registry-v2 scalar
checksums remain valid.

WaveKit must pin and qualify the exact 0.6.8 artifact before consuming the new
identity or provenance fields. WaveKit must not reproduce P2P's semantic
projection and must continue to preserve sealed artifacts byte-identically.
Authentication, registry trust, moderation, audit and host provenance remain
WaveKit-owned responsibilities.

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

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

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.

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.

P2P Engine v0.6.5

P2P Engine 0.6.5 — 2026-09-06

P2P Engine 0.6.5 closes the P2P-side discrepancies found by the final
local/remote memory roadmap audit. It does not change the selected filesystem
storage architecture, workspace schema, synchronization protocol or authority
model.

The remote-only profile is now described accurately as a WaveKit-owned access
mode. A remote-only user has no client-local P2P root, CLI, MCP stdio server
or generated integration artifacts; authenticated web, API and MCP HTTP
instructions and tool discovery come from WaveKit. P2P still exposes this
boundary in its profile matrix, while every local artifact renderer rejects
remote-only before writing instead of falling through to standalone or
linked-local assumptions.

Maintained WaveKit transition documentation is bound by tests to the current
fixture manifest and runtime version. Release documentation also distinguishes
the repository's actual create-only, attested and checksum-pinned publication
process from GitHub-enforced immutable releases, which are not enabled.

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.5/p2p_engine-0.6.5-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.5 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.4 filesystem projects remain valid and require no storage,
workspace, bundle, authority, linked-replica or WaveKit server migration.
Standalone and linked-local generated integrations keep their existing public
behavior. WaveKit should update its exact wheel pin only after this release has
successfully published.

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

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

P2P Engine v0.6.4

P2P Engine 0.6.4 — 2026-09-05

P2P Engine 0.6.4 completes the first online lifecycle and recovery model for
linked-local WaveKit projects. Owners can suspend and resume a replica,
detach a verified standalone project with a new identity and explicit lineage,
create a new remote project from local state, publish immutable project
snapshots, remove only the local replica, archive or restore the remote project,
and perform receipt-gated remote deletion without creating dual writers.

Linked replicas now verify project and replica identity, authority epoch,
confirmed revision and canonical semantic/blob digests before synchronization.
Formatting-only changes, Git state and valid adapter-owned transient bytes do
not create false drift. Semantic divergence, identity mismatch, corruption and
interrupted local operations fail closed before blind catch-up or mutation.

The owner can inspect bounded logical findings, preserve a verified forensic
archive and rebuild the local replica atomically from a complete authoritative
WaveKit snapshot. When the entire difference is exactly one supported domain
change, P2P can preview and explicitly apply project.domain.set or
project.domain.clear through the ordinary WaveKit command, receipt and feed
path. Unknown differences remain unsupported. Raw local YAML, database pages,
credentials and Git data are never uploaded as reconciliation evidence.

MCP exposes only sanitized lifecycle, publication and drift inspection. Detach,
delete, rebuild and reconciliation apply remain owner-confirmed CLI operations.
Generated agent instructions tell agents to stop linked writes on drift and
request governed recovery instead of editing .p2p directly.

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.4/p2p_engine-0.6.4-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.4 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 current-schema filesystem projects remain valid and require no
storage or workspace migration from 0.6.3. The filesystem adapter remains the
sole supported product backend; SQLite is not included. Standalone projects
continue to use local backup, restore and workspace recovery without WaveKit.

Linked lifecycle, durable replication and drift reporting require a compatible
WaveKit server advertising their negotiated capabilities. Older servers fail
capability negotiation rather than accepting an unsupported transition or
reconciliation request. Offline linked mutations remain outside this release.

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.4 and the
immutable GitHub Release. Verify the wheel with:

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

P2P Engine v0.6.3

P2P Engine 0.6.3 — 2026-09-04

P2P Engine 0.6.3 completes durable replication for linked-local WaveKit
projects. Linked mutations now travel as typed, revision-bound commands to the
authoritative server and return immutable, idempotent operation receipts.
Successful commits create one monotone project revision and one ordered
after-state change batch in the P2P-owned filesystem memory.

Linked replicas can recover independently of realtime delivery through a
cursor-based durable feed. Batch application, managed-blob verification, inbox
deduplication and cursor advancement use one local transaction. A client that
falls outside bounded feed retention receives a verified snapshot fallback
instead of silently skipping changes.

The public p2p sync status|catch-up|recover commands expose explicit recovery
and diagnostics. p2p watch uses authenticated SSE only as an optional wake-up
and always confirms changes through the durable feed. Lost responses reconcile
through operation identity; duplicate commands and batches do not duplicate
effects, and stale same-entity work returns a typed conflict instead of using
last-write-wins.

Linked MCP reads perform freshness preflight, while linked MCP domain writes
route through WaveKit authorization with expected revision and entity evidence.
Raw feed, cursor, storage and compaction primitives remain private worker
surfaces. Offline linked mutations remain blocked, and ephemeral presence is
excluded from canonical memory, bundles and P2P audit.

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.3/p2p_engine-0.6.3-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.3 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 current-schema filesystem projects remain valid and require no
storage or workspace migration from 0.6.2. The filesystem adapter remains the
sole supported product backend; SQLite is not included in this release.
Standalone projects continue to work locally without WaveKit.

Durable linked operation requires a compatible WaveKit server that advertises
p2p-durable-replication/v1. Older servers fail capability negotiation rather
than accepting unsupported writes. The protocol remains transport-neutral, so
future WebSocket notification delivery does not change commands, receipts,
change batches or cursors.

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 tag-triggered release workflow creates GitHub Artifact Attestations for
the wheel, source distribution and checksum file. Verify the wheel with:

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

The release assets are published only from the exact tagged commit after the
source, reproducibility, installed-wheel and cross-platform uv gates pass.

P2P Engine v0.6.2

P2P Engine 0.6.2 — 2026-09-03

P2P Engine 0.6.2 adds the local half of governed project-authority transfer
and linked WaveKit replicas. A standalone project can transfer canonical
authority to a compatible WaveKit server without changing its stable
project_uuid. The client uses an authenticated, previewed and confirmed
workflow with deterministic bundle/blob upload, an authority fence and
idempotent recovery after timeouts or lost responses.

An authoritative WaveKit project can then be cloned or attached as a local
replica. Each physical copy receives a distinct replica_id; P2P downloads a
revision-bound canonical snapshot and every referenced managed blob, verifies
the complete artifact set in staging and publishes .p2p atomically. Explicit
status, catch-up, recovery, move, register-copy and forensic read-only commands
complete the bootstrap lifecycle.

Credentials remain in the operating-system keyring. Project memory stores only
the non-secret server binding, account reference, authority epoch, applied
revision and cursor. Linked writes remain disabled and offline reads are
explicitly stale until the later durable-replication protocol is available.

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.2/p2p_engine-0.6.2-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.2 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 current-schema filesystem projects remain valid and require no
storage or workspace migration from 0.6.1. The filesystem adapter remains the
sole supported product backend; SQLite is not included in this release.
Standalone behavior remains local. Transfer, clone and catch-up require a
compatible WaveKit server and do not expose or depend on its persistence
implementation.

The first linked-local release is intentionally read-only for project-domain
mutations. It supports explicit catch-up and recovery; durable incremental
commands, automatic command preflight and realtime wake-ups remain a later
protocol step.

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 tag-triggered release workflow creates GitHub Artifact Attestations for
the wheel, source distribution and checksum file. Verify the wheel with:

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

The release assets are published only from the exact tagged commit after the
source, reproducibility, installed-wheel and cross-platform uv gates pass.