v0.99.35

Added

• Shared-pool reservations with one authoritative owner (F02, not yet
  enforced).
  • synapse hub --spend-ledger FILE makes a hub the owner of shared pools. It
    requires --hub-id and --multihub-serving-policy.
  • The owner decides every reservation in an owner-only SQLite ledger, kept
    apart from the replicated journal, and checks
    settled + outstanding + new <= hard_bound in one serialized transaction.
  • Exposure includes the pool's minimum charge and fixed fee, and every pool
    declares its tax basis.
  • Expired grants and grants from an earlier owner epoch still count until a
    final settlement or an operator reconciliation.
  • Depth, wall time and concurrent seats are separate limits. An overrun blocks
    new grants until it is reconciled.
  • Peer hubs use spend_request / spend_result (reserve, settle, query), or
    synapse spend request. Every refusal is the same not-admitted, and a
    retry or query returns the stored answer.
  • Operators configure, inspect, audit and reconcile pools locally with
    synapse spend.
  • Owner failover. An operator-signed revocation of the current epoch, from
    a key the pool lists, names the new owner, the ledger sequence and digest of
    the exact copy it starts from, and an attestation that the old key is revoked
    or the host retired.
    • synapse spend fail-over takes the pool over from that copy.
    • Grants of the old epoch still count until they are settled.
    • A recovered old owner that records the revocation refuses its revoked
      epoch.
  • The ledger bounds reservations, but it cannot stop a provider from billing.

Artifact checksums (SHA-256)

2cacb09dc8a076901b04ae152e6cebf0dd27823b93261c42e3558a318e348709  synapse_channel-0.99.35-py3-none-any.whl
7a5dde5c44e5633803a6cad23b5064d76359a40b093d12f7c6727200b8b50f46  synapse_channel-0.99.35.tar.gz
946d4eecc43159efc580311fd2a072f19fa7b617acb2d14cbbe36713951b1371  synapse-channel-v0.99.35-sbom.cdx.json