Summary

Second slice of the native WebRTC camera streaming plan (docs/adr/0001-native-webrtc-session-library.md), stacked on #7137 — the base branch is the foundation PR and will be retargeted to main once it merges. The diff here is only the renderer and the debug entry point.

• :webrtc-compose (new module): WebRtcVideo composable rendering a CameraPlayer through a SurfaceViewRenderer that shares the peer connection factory's EGL context, so the hardware decoder and the view use the same context. The composable only binds the sink to the lifecycle (attach on START, detach on STOP/dispose); starting and stopping the session stays with its owner (a ViewModel), which is what lets the session survive configuration changes — rotation rebinds the renderer without renegotiating. Overlay slot API for the connecting state (shown until the first rendered frame, driven by RendererEvents) and the failed state (for a later HLS-fallback UI). The renderer is injectable internally, so the sink lifecycle and overlay logic are covered by JVM unit tests without native libwebrtc.
• :app: a developer-settings debug screen (Settings → Developer tools → WebRTC camera player) to exercise the native player against a camera entity of the active server before any dashboard integration exists — this is the manual test harness for the camera/codec matrix, in particular two-way-audio-capable cameras on plain-HTTP LANs later. The session is owned by the ViewModel (released in onCleared). A Hilt module provides the process-wide libwebrtc factory.

Next slices per the ADR: the external-bus protocol (webrtc/play / webrtc/state / webrtc/stop with a capability flag in the external auth handshake, paired with a frontend PR), then capability gating + HLS fallback through the shared CameraPlayer seam.

Checklist

• New or updated tests have been added to cover the changes following the testing guidelines.
• The code follows the project's code style and best_practices.
• The changes have been thoroughly tested, and edge cases have been considered.
• Changes are backward compatible whenever feasible. Any breaking changes are documented in the changelog for users and/or in the code for developers depending on the relevance.

Any other notes

• Stacked on Add native WebRTC session foundation (core engine + HA signaling) #7137; do not merge before it. The only user-visible surface is the developer-settings screen — no dashboard behavior changes.
• Verified locally: :webrtc-compose unit tests, :app compilation, lint (no new issues), ktlintCheck, and lockfiles regenerated via ./gradlew alldependencies --write-locks.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TxHn9ySi8aRFvvmfcPRgVu

Generated by Claude Code