v0.99.29

Added

• Let agents message seats on another hub as PROJECT/seat@HUB_ID (wire
  version 5). synapse hub --message-peer HUB_ID=URI forwards chats,
  version-three delivery intents and synapse who --hub roster requests to a
  peer that grants this hub the target's namespace under its multi-hub serving
  policy and pinned mutual TLS. Chats wait in a durable outbox and are retried
  until answered or expired, and the receiving hub answers each forward once.
  Forwarded senders appear as seat@ORIGIN_HUB and never gain interrupt or
  steer. Receipts report the forward's outcome, including to a sender that
  was offline when it settled.

Changed

• Reserve every name containing @ for seats on peer hubs; a local client that
  registers one is refused as a name conflict.
• Upgrade note: once a hub has admitted a delivery intent forwarded by a peer
  hub, its delivery journal holds requests that entered through that peer, and
  hubs older than 0.99.29 refuse to serve that journal
  (delivery journal belongs to a different stable hub id). Back up the event
  store before accepting forwarded delivery intents if a downgrade may be
  needed. Forwarded chats do not affect a downgrade.
• Mark the Pro mobile app and the Team hosted dashboard as planned in the price
  list: neither is available yet, so neither is part of what a plan delivers today.

Fixed

• Refuse claims forwarded by a peer hub while the owning hub needs journal
  recovery. Local mutations were already refused in that state, but a forwarded
  claim could still be granted on the degraded hub.

Artifact checksums (SHA-256)

0d3af814308af8ddcc873ba8df917c17287698c46f0980998cf01dcb97b0e89c  synapse_channel-0.99.29-py3-none-any.whl
a52398dab8db3539bfc901294d3d220af9562937261492a177755daf2498398a  synapse_channel-0.99.29.tar.gz
b226753b6ea8fd028075c27d6ebae1bae7343a34027b5c95850e93ead822e81d  synapse-channel-v0.99.29-sbom.cdx.json