Listener cliff at uni stream #124 with the publisher continuing to
push for ~55 s past that point — the prior MAX_STREAMS_UNI extension
fix is either firing too late or not firing at all on the live
device. The trace can't tell us which because the bump itself is
silent.
- QuicConnectionWriter: log every MAX_STREAMS_UNI / MAX_STREAMS_BIDI
emission with old→new cap and the current peerInitiated count, so
we can see whether the writer is bumping the cap at all and how
far behind reception it falls.
- QuicConnection: log peerInitiatedUniCount every 25 streams along
with the currently advertised cap and headroom. Cheap and lets us
correlate "stream count growth" against "cap bumps" without
printing per-stream noise.
Tag is `NestQuic` so listeners can scope `adb logcat -s NestRx:D
NestTx:D NestQuic:D` to capture the full picture.
https://claude.ai/code/session_01PYYez8a6sjiakyjAxsfCEQ
Claude
283e7760bd