Windows interop builds; correct the exception guidance The ABI page prescribed try/catch, which cannot compile under WebRTC's -fno-exceptions and is unnecessary anyway. Also records the keep-both decision for webrtc.dll and WebRtcInterop.dll, and gives Windows a partial tier 3 in the figure. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add Interop ABI The C contract between WebRtcInterop.dll and the Windows binding: conventions, ownership rule, threading, and the twenty-three functions of slice one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Mac Catalyst now has its own workflow Documents the split: two Apple workflows sharing one toolchain, differing only in arch list, and the need to pin webrtc_branch across both. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Give Mac Catalyst the column instead of macOS Catalyst is what WebRTCme ships and it rides the iOS xcframework, so it now appears as a first-class column in the figure and tables. Native macOS is reduced to a note: built, unconsumed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Correct the macOS framing: built, but not consumed Mac Catalyst is served by the iOS xcframework, so libwebrtc.dylib has no consumer and its missing camera path is not a gap worth closing. The workflows are kept as an Apple-silicon build check. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add the layer matrix figure as light and dark SVGs Referenced from Platform layers via <picture> so it follows the reader's theme. Generated by tools/make_platform_diagram.py in the main repository. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add a mermaid layer diagram to Platform layers Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add Prebuilt distributions Lists the other projects that build WebRTC natively, what platforms each covers, and how they relate to this repository. Cross-linked from Platform layers and Repository layout. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add Platform layers Records what each artifact actually contains: the three-layer model, a capability matrix across all six platforms, who compiles each one, and the three consequences -- no H.264 on desktop, no camera capture on macOS, and screen capture being desktop-only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>