enricobuehler
9c278ee351
ci / bun-nix (pull_request) Successful in 23s
ci / docs-drift (pull_request) Successful in 28s
ci / docs-site (pull_request) Successful in 1m11s
ci / rust-arm64 (pull_request) Successful in 1m30s
ci / web (pull_request) Successful in 1m42s
ci / rust (pull_request) Successful in 6m18s
android / android (pull_request) Successful in 6m32s
Static content used to strip every defense before motion: the unpaced microburst allowance was an absolute max(128 KiB, wire/4) — sized for gigabit LAN, so at Wi-Fi bitrates every frame went out back-to-back — and adaptive FEC decayed to 1 %, so the first big motion frame died unprotected (the 2026-08-26 field case; RFC design/abr-stack-overhaul.md in punktfunk-planning, §2.1–2.4). - The allowance is now TIME at the pace rate: 10 ms, clamped to [16 KiB, 256 KiB] (send_pacing::auto_burst_bytes). One constant lines up both proven ends — ~19 KiB at the field case's 15 Mbps pace (its discriminator was PACE_BURST_KB=16) and ~112 KiB at 90 Mbps LAN pace, so LAN latency does not regress. PACE_FACTOR=0 keeps the legacy rule. - A streamed AU consumes ONE allowance across its block flushes instead of a fresh one per block (the latent per-block multiplication). - One frame's paced spread is bounded to ~2 frame intervals so an IDR can't back the encode|send sync_channel(3) up into cadence_degraded, which refuses every climb; MAX_PACE_SPREAD stays the absolute bound. - Adaptive FEC gains a burned floor: any window with real shard loss raises the decay floor to 5 %; ~2 clean minutes re-earn 1 %, an early re-burn doubles the requirement (bounded), a durable step-down resets it — no session-permanent latch, per the encode stand-down's house rule. PUNKTFUNK_FEC_PCT pin semantics and the GameStream plane are untouched. Pure logic (FecFloor, auto_burst_bytes, native_budget) is unit-tested; the burned-floor band is noted in the FEC_PCT docs.