feat: Update production readiness checks and enhance SCTP data channel integration tests; improve documentation and status clarity

Author: MarlonJD

README.md

@@ -259,10 +259,10 @@ association bootstrap that can exchange SCTP DATA chunks, SACK responses, and
 reassemble fragmented SCTP DATA messages, with duplicate DATA TSN suppression
 and contiguous cumulative SACK tracking. The shared media/data binder and Room
 live-media startup helper can select that association transport in
-package-internal opt-in tests, and the separately gated LiveKit integration
-harness now validates a two-client reliable `DataPacket` publish/receive path
-over that standards-shaped SCTP association transport. The public default Room
-path continues to use the existing packet-envelope transport until the remaining
+package-internal opt-in tests, and the LiveKit integration harness now validates
+a default-gated two-client reliable `DataPacket` publish/receive path over that
+standards-shaped SCTP association transport. The public default Room path
+continues to use the existing packet-envelope transport until the remaining
 standards-compliant SCTP hardening is complete.
 Data channel recovery now resets LiveKit channels after association restart,
 reopens DCEP on the next publish, and Room reconnect responses reset injected
@@ -281,9 +281,9 @@ coverage, including selected ICE pair and default media/data session assertions,
 into full secure RTP/RTCP send/receive validation, TURN TCP/TLS, live
 quality-control wiring, real-device video display hardening,
 default-path DTLS-SCTP association receive-pump integration, LiveKit-validated
-data-channel recovery, promoting the separately gated live data-packet
-publish/receive smoke into the default integration gate once standards SCTP is
-hardened, real-device audio session hardening, integration apps, and size gates.
+data-channel recovery, hardening the default-gated live data-packet
+publish/receive smoke once standards SCTP is fully complete, real-device audio
+session hardening, integration apps, and size gates.
 
 Current builds expose `LiveKitNative.productionReadiness` and
 `LiveKitNative.assertProductionReady()` so applications and release automation
@@ -447,7 +447,10 @@ REQUIRE_PRODUCTION_READY=1 scripts/check_release_readiness.sh
 The default gate checks package shape, forbidden runtime dependencies,
 unit/integration opt-in tests, benchmark smoke, and the compressed release
 binary size proxy. The strict gate additionally requires
-`LiveKitNative.productionReadiness.status == .productionReady` and no blockers.
+`LiveKitNative.productionReadiness.status == .productionReady`, no blockers,
+tests, benchmarks, the size gate, Apple platform builds, and configured LiveKit
+integration variables so a production tag cannot pass with any release gate
+disabled.
 That strict gate intentionally fails today because LiveKit E2E secure RTP/RTCP
 verification, full ICE/TURN hardening, real-device video display validation,
 standards-compliant live SCTP, Apple-platform OpenSSL packaging validation,
@@ -475,27 +478,14 @@ LIVEKIT_NATIVE_API_SECRET=secret \
 swift test --filter LiveKitNativeIntegrationTests --jobs 1
 ```
 
-The separately gated data-track and DataPacket live smoke path can be included
-when working on the DTLS-backed SCTP blocker:
-
-```sh
-LIVEKIT_NATIVE_RUN_INTEGRATION=1 \
-LIVEKIT_NATIVE_RUN_DATA_TRACK_INTEGRATION=1 \
-LIVEKIT_NATIVE_LIVEKIT_URL=ws://127.0.0.1:7880 \
-LIVEKIT_NATIVE_API_KEY=devkey \
-LIVEKIT_NATIVE_API_SECRET=secret \
-swift test --filter LiveKitNativeIntegrationTests --jobs 1
-```
-
 The harness generates per-run room names with an `lknative-` prefix and
 short-lived room-scoped participant tokens. It currently covers one-client
 connect/disconnect, two-client participant join/leave, and live OpenSSL
 DTLS-SRTP publisher/subscriber media startup on the socket-backed Room media
 path with one publisher H.264 RTP send attempt. The live data-track
 subscriber-handle and standards-shaped SCTP data-packet publish/receive tests
-are passing but gated separately with
-`LIVEKIT_NATIVE_RUN_DATA_TRACK_INTEGRATION=1` until the DTLS-backed SCTP data
-channel transport blocker is closed. Strict production release mode now
+are included in the default integration gate whenever
+`LIVEKIT_NATIVE_RUN_INTEGRATION=1` is set. Strict production release mode now
 requires those integration variables so the future `productionReady` marker
 cannot pass while live tests are silently skipped.
 

Sources/LiveKitNative/Core/ProductionReadiness.swift

@@ -32,7 +32,7 @@ public extension LiveKitNative {
             "Fresh join, resume reconnect, disconnect, and failed signal-loop boundaries regenerate local ICE credentials, clear stale peer negotiation state, parse TURN UDP/TCP/TLS endpoint configuration, order TURN relay fallback candidates as UDP, TCP, then TLS while identifying the currently executable UDP datagram path, select supported TURN UDP relay session configurations from parsed ICE server endpoints with credentials, exercise TURN Allocate, Refresh, CreatePermission, and ChannelBind request/authentication/response-validation primitives with one-shot stale nonce retry, cover TURN ChannelData framing, provide deterministic allocation/permission maintenance scheduling and execution, plan relayed ICE candidates from TURN bindings, compose and execute a bounded TURN relay session setup plan over abstract transports, expose a ChannelData relay transport over an abstract media datagram transport, allocate default UDP TURN relay candidates through the bound Room ICE socket, use ChannelData relay bindings for relayed ICE checks and media datagrams, provide deterministic ICE consent freshness planning plus an injected Room startup loop, run ICEAgent connectivity checks through paced scheduling with queued triggered-check priority plus role-conflict role switching and pair-priority recompute, and rebuild reconnect SyncState SDP/trickle state with fresh local ICE credentials, but TCP/TLS TURN transport execution, LiveKit TURN-only validation, and live media recovery are not complete.",
             "Publisher camera capture can encode H.264 through VideoToolbox with bounded frame backpressure/drop control and publisher microphone capture can encode Opus through AudioToolbox before RTP/SRTP send, while subscriber RTP can pass through jitter buffering, H.264/Opus packet assembly, NACK/PLI feedback, opt-in Opus decode-to-audio-playout scheduling, opt-in H.264 VideoToolbox decode-to-pixel-buffer scheduling, application-provided subscriber video renderer handoff, UIKit/AppKit VideoView sample-buffer rendering, and opt-in iOS voice-chat audio-session lifecycle configuration; real-device video display validation, LiveKit E2E media validation, route/interruption audio recovery, and production runtime pacing remain incomplete.",
             "Production H.264 now uses real VideoToolbox encode output for publish smoke coverage, opt-in VideoToolbox decode output for subscribe smoke coverage, and UIKit/AppKit VideoView rendering for decoded frames, but production readiness still requires real-device display validation, hardware acceleration verification where the OS exposes that signal, and explicit fallback behavior instead of relying on a pure Swift codec implementation.",
-            "SCTP data channel support includes packet-level DCEP/DataPacket planning, manager-assigned stream routing, queued local publish flushing, inbound DataPacket-to-RoomEvent plumbing, publisher SDP data-channel negotiation, subscriber-side data-channel receive-loop plumbing, OpenSSL DTLS application-data transport coverage, default Room shared-media DTLS/SRTP demux binding, deterministic packet fragmentation/reassembly envelopes, fragmented-packet retransmission scheduling on the DTLS-backed packet transport, opt-in standards-shaped SCTP association bootstrap with DATA/SACK exchange, fragmented DATA reassembly, duplicate DATA TSN suppression, contiguous cumulative SACK tracking, recovery reset that reopens LiveKit data channels after association restart, and separately gated two-client LiveKit DataPacket publish/receive smoke over that standards-shaped association transport, but full standards-compliant SCTP association state, congestion control, promotion of live DataPacket coverage into the default integration gate, LiveKit-validated data-channel recovery, and E2E hardening are incomplete.",
+            "SCTP data channel support includes packet-level DCEP/DataPacket planning, manager-assigned stream routing, queued local publish flushing, inbound DataPacket-to-RoomEvent plumbing, publisher SDP data-channel negotiation, subscriber-side data-channel receive-loop plumbing, OpenSSL DTLS application-data transport coverage, default Room shared-media DTLS/SRTP demux binding, deterministic packet fragmentation/reassembly envelopes, fragmented-packet retransmission scheduling on the DTLS-backed packet transport, opt-in standards-shaped SCTP association bootstrap with DATA/SACK exchange, fragmented DATA reassembly, duplicate DATA TSN suppression, contiguous cumulative SACK tracking, recovery reset that reopens LiveKit data channels after association restart, and default-gated two-client LiveKit DataPacket publish/receive smoke over that standards-shaped association transport, but full standards-compliant SCTP association state, congestion control, LiveKit-validated data-channel recovery, and E2E hardening are incomplete.",
             "Signal reconnect resets stale peer negotiation state, restarts local ICE credentials, rebuilds retained subscriber answer and publisher offer SDP with fresh ICE credentials, sends SyncState for retained subscription/local media/data publication state, re-sends local ICE trickle/final-trickle when media startup is configured, preserves publisher offer track state for later publish/unpublish re-offers, clears stale local media/data publication state for server/SFU unpublish responses, and resets injected publisher data channels for post-reconnect DCEP reopen in unit tests, but live media recovery and LiveKit integration hardening are incomplete.",
             "General production video meetings require the new audio-session primitives to be validated with meeting-grade capture/playout, echo cancellation, route changes, Bluetooth behavior, interruptions, background/foreground handling, and timing on real iOS devices.",
             "A default subscriber RTP receive pipeline now integrates jitter buffering with bounded NACK/PLI feedback, scheduled RTCP Receiver Reports with DLSR timing from observed RTP/Sender Report state, REMB bitrate-feedback packet planning/sending, deterministic RTCP receiver-report bandwidth estimation, adaptive video quality recommendations, publisher RTCP receiver-report ingestion, H.264 encoder bitrate/FPS recommendation application, manual subscriber quality preset signaling, opt-in automatic subscriber adaptive track-settings dispatch, publisher active video-layer UpdateVideoLayers signaling, single-layer H.264 AddTrack high-quality metadata, and camera publish frame backpressure primitives, but general production video meetings still require full packet-loss recovery, TWCC/full REMB interop or equivalent congestion control, default-on LiveKit-validated subscriber adaptation policy, complete encoder control policy, actual multi-encoder simulcast/SVC media production, and weak-network E2E validation.",

Tests/LiveKitNativeIntegrationTests/IntegrationOptInTests.swift

@@ -158,13 +158,6 @@ final class IntegrationOptInTests: XCTestCase {
     }
 
     func testTwoLiveKitClientsReceiveDataTrackSubscriberHandles() async throws {
-        guard ProcessInfo.processInfo.environment["LIVEKIT_NATIVE_RUN_DATA_TRACK_INTEGRATION"] == "1" else {
-            throw XCTSkip(
-                "Live data-track subscriber handles require the DTLS-backed SCTP data channel transport, " +
-                "which remains a separate production-readiness blocker."
-            )
-        }
-
         let harness = try LiveKitIntegrationHarness.load()
         let roomName = harness.roomName(suffix: "data-track")
         let firstIdentity = "swift-native-data-sub"
@@ -201,13 +194,6 @@ final class IntegrationOptInTests: XCTestCase {
     }
 
     func testTwoLiveKitClientsPublishAndReceiveDataPacketOverStandardsSCTP() async throws {
-        guard ProcessInfo.processInfo.environment["LIVEKIT_NATIVE_RUN_DATA_TRACK_INTEGRATION"] == "1" else {
-            throw XCTSkip(
-                "Live data-packet publish/receive requires standards-shaped DTLS-backed SCTP validation, " +
-                "which remains a separate production-readiness blocker."
-            )
-        }
-
         let harness = try LiveKitIntegrationHarness.load()
         let roomName = harness.roomName(suffix: "data-packet")
         let subscriberIdentity = "swift-native-data-packet-sub"

Tests/LiveKitNativeTests/ProductionReadinessTests.swift

@@ -9,9 +9,9 @@ final class ProductionReadinessTests: XCTestCase {
         XCTAssertFalse(readiness.isProductionReady)
         XCTAssertFalse(readiness.blockers.isEmpty)
         XCTAssertTrue(readiness.blockers.contains { $0.contains("DTLS-SRTP") })
-        XCTAssertTrue(readiness.blockers.contains { $0.contains("LiveKit DataPacket publish/receive smoke") })
+        XCTAssertTrue(readiness.blockers.contains { $0.contains("default-gated two-client LiveKit DataPacket publish/receive smoke") })
         XCTAssertTrue(readiness.blockers.contains { $0.contains("full standards-compliant SCTP association state") })
-        XCTAssertTrue(readiness.blockers.contains { $0.contains("promotion of live DataPacket coverage") })
+        XCTAssertFalse(readiness.blockers.contains { $0.contains("promotion of live DataPacket coverage") })
     }
 
     func testAssertProductionReadyFailsUntilBlockersAreCleared() {

docs/STATUS.md

@@ -65,11 +65,11 @@ messages without replacing the default Room data-channel path yet. The
 association transport also suppresses duplicate DATA TSNs and tracks contiguous
 cumulative SACK state. The shared media/data session binder and package-internal
 Room live-media startup helper can now select that association transport in
-opt-in unit tests, and the separately gated LiveKit integration harness validates
-a two-client reliable `DataPacket` publish/receive path over the
-standards-shaped SCTP association transport. The public default Room path remains
-on the existing packet-envelope transport until the remaining standards-compliant
-SCTP hardening is complete.
+opt-in unit tests, and the LiveKit integration harness validates a default-gated
+two-client reliable `DataPacket` publish/receive path over the standards-shaped
+SCTP association transport. The public default Room path remains on the existing
+packet-envelope transport until the remaining standards-compliant SCTP hardening
+is complete.
 SCTP data-channel recovery can now reset LiveKit channels after association
 restart, reopen DCEP on the next publish, and Room reconnect responses reset
 injected publisher data channels and receive loops before post-reconnect publish.
@@ -79,8 +79,8 @@ datagram path in unit tests, and public default `Room` initialization now
 selects that combined startup binder for live media/data transport construction.
 Full standards-compliant SCTP association
 receive-pump integration, congestion control, LiveKit-validated data-channel
-recovery, promotion of the separately gated live data-packet smoke into the
-default integration gate, and E2E hardening remain open.
+recovery, hardening the default-gated live data-packet smoke once standards SCTP
+is fully complete, and E2E hardening remain open.
 Server/SFU `TrackUnpublishedResponse` cleanup for local media publications also
 clears local publication state and cached publisher offer reconnect state so
 resume reconnects and later publisher offers do not replay removed media.
@@ -267,7 +267,9 @@ The old binary WebRTC dependency path has been removed from the package model.
 - Release-readiness scripts:
   - `scripts/check_release_readiness.sh`
   - `scripts/check_release_size.sh`
-  - strict production mode through `REQUIRE_PRODUCTION_READY=1`
+  - strict production mode through `REQUIRE_PRODUCTION_READY=1`, with tests,
+    benchmarks, the size gate, Apple platform builds, and LiveKit integration
+    variables required
 - `LocalParticipant` has local video publication state for camera tracks,
   including idempotent `setCamera(enabled:)`, `publish(videoTrack:)`, and
   `unpublish(publication:)` behavior.
@@ -892,8 +894,8 @@ The following checks passed after the latest implementation pass:
   - 7 live tests skipped by opt-in guard without LiveKit environment variables
 - `LIVEKIT_NATIVE_RUN_INTEGRATION=1 swift test --filter LiveMediaStartupIntegrationTests --jobs 1`
   - 2 live OpenSSL DTLS-SRTP media startup tests passed against local LiveKit
-- `LIVEKIT_NATIVE_RUN_INTEGRATION=1 LIVEKIT_NATIVE_RUN_DATA_TRACK_INTEGRATION=1 swift test --filter IntegrationOptInTests/testTwoLiveKitClientsPublishAndReceiveDataPacketOverStandardsSCTP --jobs 1`
-  - separately gated standards-shaped SCTP DataPacket live smoke passed against local LiveKit
+- `LIVEKIT_NATIVE_RUN_INTEGRATION=1 swift test --filter IntegrationOptInTests/testTwoLiveKitClientsPublishAndReceiveDataPacketOverStandardsSCTP --jobs 1`
+  - default-gated standards-shaped SCTP DataPacket live smoke passed against local LiveKit
 - `LIVEKIT_NATIVE_RELEASE_RUN_TESTS=0 LIVEKIT_NATIVE_RELEASE_RUN_BENCHMARKS=0 LIVEKIT_NATIVE_RELEASE_RUN_SIZE_GATE=0 scripts/check_release_readiness.sh`
   - release-shape check passed with tests, benchmarks, and size gate disabled
 - `swift build --target LiveKitNativeWebRTC --jobs 1 --disable-index-store -debug-info-format none`
@@ -906,6 +908,8 @@ The following checks passed after the latest implementation pass:
 - Release gates:
   - `scripts/check_release_readiness.sh` validates package shape, dependency
     guard, tests, benchmark smoke, and size gate in non-strict mode
+  - strict production mode also rejects disabled tests, benchmark smoke, size
+    gate, Apple platform builds, or missing LiveKit integration variables
   - The release-shape check passes with tests, benchmarks, and size gate
     disabled through `LIVEKIT_NATIVE_RELEASE_RUN_TESTS=0`,
     `LIVEKIT_NATIVE_RELEASE_RUN_BENCHMARKS=0`, and
@@ -1036,13 +1040,13 @@ The following checks passed after the latest implementation pass:
 
 - Expand the current opt-in LiveKit integration harness beyond one-client
   connect/disconnect, two-client participant join/leave, generated `lknative-`
-  room prefixes, short-lived room-scoped tokens, the separately gated
-  two-client data-track subscriber-handle signaling and standards-shaped SCTP
-  data-packet publish/receive tests, and live OpenSSL DTLS-SRTP
-  publisher/subscriber media startup.
-- Harden the separately gated data packet publish/receive test beyond the
-  current standards-shaped SCTP live smoke, then move it into the default live
-  integration gate once the standards-compliant SCTP blocker is closed.
+  room prefixes, short-lived room-scoped tokens, the two-client data-track
+  subscriber-handle signaling and standards-shaped SCTP data-packet
+  publish/receive tests, and live OpenSSL DTLS-SRTP publisher/subscriber media
+  startup.
+- Harden the default-gated data packet publish/receive test beyond the current
+  standards-shaped SCTP live smoke once the standards-compliant SCTP blocker is
+  closed.
 - Full RTP/RTCP publish/subscribe media validation beyond startup and one H.264
   RTP send attempt.
 - Reconnect integration test.
@@ -1123,5 +1127,7 @@ For an actual production tag gate, use:
 REQUIRE_PRODUCTION_READY=1 scripts/check_release_readiness.sh
 ```
 
-Strict production mode also requires the opt-in LiveKit integration variables
-so a production tag cannot pass with the live server tests skipped.
+Strict production mode also requires tests, benchmark smoke, the size gate,
+Apple platform builds, and the opt-in LiveKit integration variables so a
+production tag cannot pass with any release gate disabled or live server tests
+skipped.