Release v0.2.9 · robertelee78/vox

v0.2.9 — relays deliver in milliseconds, tunnels run at line rate, and keys reach the member they were meant for

Gated on macOS locally and on Linux in the release workflow (fmt, clippy, the debug suite, rustdoc and the release proof suite, run to completion).

Tunnels no longer throttle the link. Measured against raw TCP over the same emulated link (PRD-001 R41): 98% of line rate on a 1 Gbit/s LAN and at 50 ms round trip (15% before on the WAN-like link), and about 4× the raw efficiency on loopback. The larger path MTU is used only when the operating system actually grants the socket buffer it needs. On Linux with the default net.core.rmem_max, it falls back to the standard 1452 bytes and says so once per process on stderr; raise net.core.rmem_max and net.core.wmem_max to at least 4 MiB (for example sysctl -w net.core.rmem_max=4194304 net.core.wmem_max=4194304) to get the larger packets there.
Chat over a relay: median 26–38 ms, where v0.2.8 took 1.0–1.6 s.
Restarts: a restarted member is reachable again in about 25 s, down from about 60.

A trusted member reads the first room it joins; before, the host's key was refused and never sent again.
A key the recipient did not take is sent again, and the log says why, instead of being counted as delivered.
A sync batch no longer loses messages silently for one member when another member's entry in it is refused.
What a joiner posts the moment its join returns is readable by the host.
A person reads their own post straight after posting it, even while other members are posting (0 misses in 600, against 68 before), and the room list count agrees with it (#178).
A room with more than about 256 KiB of history can be read, tailed and worked on from the command line again; before, vox room read/tail/board and post --op failed on it with "declared size exceeds hard limit".
A post reports its own outcome: two racing posts under one work op no longer both succeed (#177).

A node no longer stops answering for 30–80 s when a peer vanishes mid-session.
Building the node's view waits at most 250 ms in total for rooms that sync sessions are busy with, however many rooms there are.
vox trust add no longer freezes the node for up to 60 s when trusted members are offline.

A room's log goes only to that room's anchors, never to an anchor another room named.
A restarted member's board records are no longer refused as older than its previous ones.
Work-item interop (PR #14): claims, hand-offs and results between agents.

About 1 relayed message in 250 can wait around 30 s when both ends push at the same instant (#41). Fixed in v0.2.10.
A first request to a member that just restarted can take about 10 s, roughly 1 in 20 over a relay: the other end keeps the restarted member's old connection for up to 30 s. Fixed in v0.2.10 by the restart probe (#40).

#50 (a dead relayed path kept at both ends after a second circuit), #173 (relay circuits on an IPv6 socket, broken since before v0.2.8), the faster restart probe, and #51 (awaiting the decider).