docs(audio-rooms): moq-lite listener landed — refresh status callouts

Phase 5d wrapped, so the doc set now reflects "listener path done,
speaker pending":

  - nestsClient/plans/2026-04-26-moq-lite-gap.md — new "Implementation
    status" section maps phases 5a → 5d to commits, calls out the
    speaker side as blocked on a small `WebTransportSession.acceptBidi`
    extension (since publisher.rs:40 uses Stream::accept), and points
    at the existing :quic primitive (QuicConnection.awaitIncomingPeerStream)
    that the bridge can lean on.
  - nestsClient/plans/2026-04-26-audio-rooms-completion.md — Phase M1
    is no longer "on hold for moq-lite"; manual nostrnests.com
    validation should now work end-to-end on the listener path.
  - .claude/CLAUDE.md — :nestsClient now hosts both IETF MoQ-transport
    and moq-lite Lite-03; production listener path uses moq-lite.

.claude/CLAUDE.md

@@ -13,9 +13,10 @@ a non-interactive JVM command-line client that drives the same `quartz` + `commo
 humans, agents, and interop tests. `quic` is a from-scratch pure-Kotlin QUIC v1 + HTTP/3 +
 WebTransport client (no JNI, no BouncyCastle), built because no Android-compatible Java QUIC library
 exists. `nestsClient` runs the audio-room protocol on top of `:quic` for the NIP-53
-audio-rooms feature. It currently implements IETF `draft-ietf-moq-transport-17`; the
-real nostrnests relay speaks **moq-lite** (kixelated's wire-incompatible variant),
-so end-to-end interop is gated on a moq-lite codec — see
+audio-rooms feature. It implements both IETF `draft-ietf-moq-transport-17` (under
+`moq/`) and **moq-lite Lite-03** (kixelated's variant, under `moq/lite/`) — the
+production listener path uses moq-lite to interop with the nostrnests reference
+relay. Speaker-side moq-lite is still pending; see
 `nestsClient/plans/2026-04-26-moq-lite-gap.md`.
 
 ## Architecture