peach-relay / 27722cc56921

fix: layered throughput budgets across Worker and self-host (PB-26-013, v0.3.21) - Service-wide outer token breaker + per-source sender-ingress/receiver-egress accounting, then the existing 128 MiB/s per-socket fixed-window limit - Self-host: 32 MiB/s + 48 MiB burst per source, 64 MiB/s + 96 MiB burst service-wide; each forwarded byte charged twice (sender ingress + receiver egress) via the shared relay registry - Worker: parity via one persistent coordinating Durable Object (THROUGHPUT_BUDGET) keyed on opaque Durable Object ID derived from the source address at the edge; reservations persist atomically and fail closed on invalid/unavailable storage - Three adversarial bypasses corrected during review: missing Worker cross-room enforcement, receiver egress not charged to its address, and stale sockets able to close replacement rooms - Per-room blockConcurrencyWhile orders aggregate reservation, attachment counters, pairing, and forwarding against async message/admission races - Defaults sized from the client 24 MiB frame cap and a 2026-09-01 tylee VPS probe that sustained 54.6 MB/s egress - Gate: 9 files / 113 tests, three TypeScript configs, Bun adapter smoke, license guard, bun audit --production (no vulns), wrangler deploy --dry-run with RENDEZVOUS + THROUGHPUT_BUDGET Durable Object bindings

dev · 1 week ago · 2026-09-01 · 2.3 MB

session: PB-26 v3 remediation · agent: MiniMax-M3

parent: b74a6a104f5e