Add MOQ Lite integration test issue

Author: dmorn

.scratch/moq-lite-04-protocol/PRD.md

@@ -182,6 +182,11 @@ Delivered so far:
   stream lifecycle, support transport normalized events, and the
   reference-style subscribe/group/frame smoke flow
 
+Follow-up integration work:
+
+- issue 09: real QUIC MOQ Lite 04 integration tests over
+  `MOQX.Transport.Quicer`
+
 ## References
 
 - <https://datatracker.ietf.org/doc/html/draft-lcurley-moq-lite-04>

.scratch/moq-lite-04-protocol/issues/09-add-moq-lite-real-quic-integration-tests.md

@@ -0,0 +1,75 @@
+> *This was generated by AI during triage.*
+
+# Add MOQ Lite 04 real QUIC integration tests
+
+Status: ready-for-agent
+Type: enhancement
+
+## Parent
+
+`.scratch/moq-lite-04-protocol/PRD.md`
+
+## What to build
+
+Add explicit integration coverage proving the completed MOQ Lite 04 client APIs
+work over the real `MOQX.Transport.Quicer` backend, not only the deterministic
+`MOQX.Transport.Support` backend.
+
+The first integration slice should use a local real-QUIC self-pair: one endpoint
+acts as the subscriber, the other as the publisher, and the test exercises the
+same public API flow covered by the Support-transport smoke test:
+
+1. subscriber connects with `MOQX.MOQLite04.connect/2`;
+2. subscriber opens a Subscribe transaction stream;
+3. publisher accepts the peer-opened Subscribe stream;
+4. publisher receives `Subscribe`;
+5. publisher sends `SubscribeOk`;
+6. subscriber receives `SubscribeOk`;
+7. publisher opens a unidirectional Group stream with `publish_group/3`;
+8. subscriber accepts the Group stream and receives the original Frame payload.
+
+The test must run against `MOQX.Transport.Quicer` through the
+`MOQX.Transport` facade and public `MOQX.MOQLite04` APIs. It should not match
+raw `quicer` messages in protocol assertions.
+
+## Acceptance criteria
+
+- [ ] An ExUnit integration test exists for the MOQ Lite 04 subscribe/group/frame
+      flow over a real local `MOQX.Transport.Quicer` pair.
+- [ ] The test module is tagged `:integration` and remains excluded by default.
+- [ ] The test reuses the caller-managed integration harness conventions from
+      `docs/adr/0004-docker-compose-driven-quic-integration-harness.md` and
+      does not start Docker from ExUnit.
+- [ ] Certificate, ALPN, host, and port inputs come from explicit test config or
+      helper arguments; the test does not mutate `Application` env.
+- [ ] The subscriber side uses `MOQX.MOQLite04.connect/2` with
+      `transport: {MOQX.Transport.Quicer, opts}`.
+- [ ] The publisher side uses `MOQX.Transport` listener/accept/handshake APIs and
+      wraps the accepted connection in a `MOQX.MOQLite04.Client` with a fresh
+      `MOQX.MOQLite04.Session`.
+- [ ] The protocol flow uses public MOQ Lite APIs:
+      `subscribe/2`, `accept_stream/2`, `recv/2`, `subscribe_ok/3`, and
+      `publish_group/3`.
+- [ ] The final assertion proves the subscriber receives the exact original
+      `Frame.payload` sent by the publisher.
+- [ ] Default `mix test` remains fast and hermetic.
+- [ ] `mix test --only integration` or the documented targeted integration
+      command runs the new test when the real QUIC harness prerequisites are
+      available.
+- [ ] Any external MOQ Lite reference relay/client interop gap is documented as a
+      follow-up issue unless this slice adds a stable repo-owned reference
+      harness.
+
+## Notes
+
+- Start from the Support-transport smoke test in
+  `test/moqx/moq_lite_04/publisher_operations_test.exs`.
+- Reuse the existing Quicer integration patterns in `test/integration/` and
+  `test/support/transport_contract.ex`.
+- MOQ Lite draft-04 uses ALPN `moq-lite-04`; the integration options must
+  negotiate that ALPN rather than the generic `moqx-test` transport-contract
+  ALPN.
+
+## Blocked by
+
+- `.scratch/moq-lite-04-protocol/issues/08-add-role-neutral-moq-lite-publisher-operations.md`