Claude d143053796 Add per-frame send-outcome trace to isolate moq-lite vs downstream loss ...

Test 4 showed a hard 82/100 cliff at 20 ms cadence two-users, all 18
trailing groups lost permanently. Root-cause-narrowing requires knowing
whether MoqLitePublisherHandle.send returned false (frame dropped at the
moq-lite layer due to inboundSubs.isEmpty() / publisherClosed) or true
(frame queued by moq-lite and lost downstream — uni-stream write error
swallowed by runCatching, QUIC flow control wedged, or relay drop).

The production NestMoqLiteBroadcaster wraps everything in
runCatching {…}.onFailure {…} and ignores the boolean, so frame loss is
structurally invisible to the app. This new test bypasses the broadcaster
and calls publisher.send / publisher.endGroup directly while mirroring
the auth + transport + session setup that connectNestsSpeaker performs.

Records sendOutcomes[i] and endGroupErrors[i] per frame; on failure
prints a per-frame send/recv table so we can see exactly when send
flips false (or whether all 100 sends report true and the loss is
strictly downstream of moq-lite).

2026-05-01 02:13:27 +00:00

..

plans

docs(nests): update plan doc for round-2 listener survival fixes

2026-04-28 17:23:10 +00:00

specs

feat(nests): adopt deployed nostrnests schema (streaming/auth/live + paired 10112)

2026-04-29 19:32:53 +00:00

src

Add per-frame send-outcome trace to isolate moq-lite vs downstream loss

2026-05-01 02:13:27 +00:00

build.gradle.kts

Add prod nostrnests.com audio transmission diagnostic tests

2026-05-01 01:08:14 +00:00