Verify the RingCentral Matter communications fix against Sam-only dummy records and identify the remaining blocker.
Automated Apex tests passed: LitifyRingCentralContextControllerTest and RingCentralSmsNotificationServiceTest, 10 tests, run 707UV00002ADmdQ.
Static LWC verification passed via verify-ringcentral-panel-static.mjs.
RingCentral SMS sync unit tests passed via npm test.
Live Salesforce readback found 8 SAIL_SMS_Message__c rows for the dummy Matter and Intake only. Live RingCentral messages 3556486131052 outbound and 3556534448052 inbound are both attached to dummy Matter a0LUV00000H4LP32AN with Party__c null.
Browser QA on dummy Matter a0LUV00000H4LP32AN passed for recipient selector, renamed Salesforce labels, SMS mode, message bubbles, live inbound/outbound message visibility, and no Salesforce-controlled Dialpad label. Screenshot evidence is in salesforce-metadata/tmp/ringcentral-sam-qa-20260527/browser-qa/.
The iframe itself still shows RingCentral demo/default behavior because the configured Salesforce label RingCentral_Embeddable_Client_Id is 40vRKrMiQIsaowVS0lBnSK. RingCentral OAuth authorize returns 403 invalid_client OAU-113: No redirect URI is registered for this client application.
The local launchd SMS sync jobs are present but failing with status 126 for hot, warm, and nightly. Manual targeted sync works; production scheduler repair is still pending.
Create or repair the dedicated RingCentral Embeddable OAuth app, register the embeddable redirect URI, update the Salesforce custom label with the valid client ID, dry-run deploy/readback, then re-run the same Sam-only browser QA. After that, repair launchd in a safe Sam-only mode before enabling broad production sync.