Publish: M153, the sender slice, and what the rollover cost Branch selection had M152 as the chosen stable milestone, which it stopped being on 2026-09-19, and gains a section on what a rollover does to a project mid-flight. Troubleshooting gains the three M153 failure modes, none of which was findable from its symptom: the Windows SDK pin mismatch, disk exhaustion presenting as a linker crash that says nothing about disk, and an Android archive that builds clean and is then rejected by its consumer over bytecode level. Two of those entries say what not to do, because both were tried. Consuming the artifacts gains how to check that bytecode level, and the Mac Catalyst slice writing PrivacyInfo.xcprivacy one directory too deep. The Interop ABI page catches up with the sender parameter and capture format work, including the measurement that contradicted the issue describing it: scale_resolution_down_by survives a capturer that ignores adaptation, because the encoder scales too, so outbound-rtp frameWidth is no evidence about the source. max_framerate is the one only the source can apply.
Document the single webrtc_branch input The chromium_milestone input is gone; milestone and branch named the same thing. Updates Branch selection, Running a build, Home, Troubleshooting and Repository layout to match. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Document the build workflows and branch selection Nine pages covering how a build is dispatched, how the WebRTC branch is resolved from the Chromium dashboard, what each of the eight workflows does, the static-to-shared library patch, how the artifacts feed into WebRTCme, and the failures seen in practice. Source lives in wiki/ in the main repository. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>