Scope ABI-stability guidance to SDK-facing WSLCCompat.idl (#40906)
* Scope ABI-stability guidance to SDK-facing WSLCCompat.idl Only WSLCCompat.idl (the WSLC SDK-facing layer) and the public plugin API require a backward-compatible ABI. The other in-box COM interfaces (IWSLCSession in wslc.idl, wslservice.idl, etc.) ship in lockstep with their only clients and have their proxy/stubs regenerated each build, so appending methods is fine. Stops the review bot from flagging method additions to in-box interfaces. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Include method removal as an ABI break in stable-surface guidance Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Use 'internal, non-stable' terminology; document it in wslservice.idl Replace the confusing 'in-box' term with 'internal, non-stable' in the ABI guidance, and add a matching note to wslservice.idl (mirroring wslc.idl) so the stability boundary is documented at the source. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Ben Hillis <benhill@ntdev.microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>