docs(audio-rooms): full moq-lite wire spec + IETF gap call-outs

Background research turned up the complete moq-lite (Lite-03) wire
format from kixelated/moq-rs and @moq/lite v0.1.7. Folded the spec
into nestsClient/plans/2026-04-26-moq-lite-gap.md as a phase-5
implementation plan:

  - ALPN ("moq-lite-03"); no SETUP/control message in Lite-03 (the WT
    handshake IS the handshake)
  - Per-request bidi streams keyed by ControlType varint (Announce=1,
    Subscribe=2, Fetch=3, Probe=4)
  - AnnouncePlease(prefix) / Announce(status, suffix, hops) shape
  - Subscribe with priority (raw u8), ordered, maxLatency (ms),
    startGroup/endGroup (off-by-one None-encoded), reply Ok/Drop
  - Group = uni stream with (DataType=0, subscribeId, sequence)
    header followed by varint-length frames until QUIC FIN
  - No datagrams; no per-frame envelope beyond size
  - Mandatory path normalisation; FIN-as-unsubscribe; RESET_STREAM
    for errors

Phase-5a..e implementation plan included (~1 week scope).

Doc + KDoc updates so the IETF MoQ-transport code is correctly
labelled and the moq-lite gap is discoverable from every entry point:

  - .claude/CLAUDE.md project description and architecture diagram
  - nestsClient/plans/2026-04-26-audio-rooms-completion.md status block
  - MoqSession.kt, MoqMessage.kt, MoqObject.kt, MoqCodec.kt KDoc — flag
    these as "IETF draft-ietf-moq-transport-17, NOT moq-lite", with
    pointers to the gap doc
  - NestsConnect.kt — note that step 3 of the listener handshake
    (SETUP) does NOT match nostrnests's relay framing

.claude/CLAUDE.md

@@ -12,8 +12,11 @@ architecture while sharing the back end components with the android counterpart.
 a non-interactive JVM command-line client that drives the same `quartz` + `commons` code — used by
 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 MoQ-transport audio-room protocol on top of `:quic` for the NIP-53
-audio-rooms feature.
+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
+`nestsClient/plans/2026-04-26-moq-lite-gap.md`.
 
 ## Architecture
 
@@ -35,7 +38,7 @@ amethyst/
 │       ├── commonMain/    # Protocol, frame/packet codecs, TLS state machine
 │       ├── jvmAndroid/    # JCA-backed AEAD + UDP socket actuals
 │       └── commonTest/    # RFC vector + adversarial tests
-├── nestsClient/    # MoQ-transport audio-room client on top of :quic
+├── nestsClient/    # Audio-room client (IETF MoQ-transport today; moq-lite phase pending)
 │   └── src/
 │       ├── commonMain/    # MoQ session, NestsListener, audio glue
 │       └── jvmAndroid/    # Opus encode/decode, AudioRecord/AudioTrack