Summary

Fixed the live Salesforce/RingCentral iframe issue for the Matter panel. The root issue was a stale compiled/cached Salesforce component and RingCentral Embeddable state continuing to use the bad RingCentral client ID 40vRKrMiQIsaowVS0lBnSK, which belongs to an app without the required browser redirect URI.

Work completed

• Took a live rollback snapshot of litifyRingCentralPanel and Collapsible_Matter_Page into tmp/ringcentral-cache-bust-v2-2026-05-19/live-before/.
• Added a new versioned Lightning Web Component bundle: litifyRingCentralPanelV2.
• Updated Collapsible_Matter_Page.flexipage-meta.xml so the RingCentral tab uses c:litifyRingCentralPanelV2 instead of the stale c:litifyRingCentralPanel bundle.
• Set the V2 iframe URL to https://apps.ringcentral.com/integration/ringcentral-embeddable/latest/app.html?prefix=sail-litify-ringcentral-20260519&enableSMSTemplate=1&enableSmsSettingEvent=1.
• Preserved the History-first/default behavior and the order History, Call, SMS, Summaries.
• Added rollback notes at tmp/ringcentral-cache-bust-v2-2026-05-19/ROLLBACK.md.

QA evidence

• Salesforce validation deploy succeeded: 0AfUV000001X84f0AC, zero component errors.
• Salesforce live deploy succeeded: 0AfUV000001X87t0AC, zero component errors.
• Live Tooling API readback confirmed litifyRingCentralPanelV2 has the prefixed iframe URL and no clientId parameter.
• Live Tooling API readback confirmed Collapsible_Matter_Page references c:litifyRingCentralPanelV2 with identifier c_litifyRingCentralPanelV2_20260519.
• Browser QA opened MAT-26010866017, selected the RingCentral tab, and confirmed the button order is History, Call, SMS, Summaries with History selected and Call History visible.
• Browser QA clicked the RingCentral iframe Sign In button. The login popup opened normal RingCentral login using clientId=SlwZwfZ_STmpq2W_qOaC5A; the old OAU-113 / invalid_client failure did not reproduce.

Notes for future agents

The immediate staff blocker is fixed. This uses RingCentral Embeddable's default client ID path, which RingCentral documents as usable but recommends replacing with a registered production app to remove the demo banner and isolate analytics. A future durable hardening pass can create a dedicated RingCentral 3-legged OAuth browser app with redirect URI https://apps.ringcentral.com/integration/ringcentral-embeddable/latest/redirect.html, then update the V2 iframe to use that new app's client ID. Avoid changing the existing SMS Quick Start App without first checking JWT/script consumers.

Reason for ending

The live fix deployed and QA passed. Further work would be production hardening, not required for the immediate sign-in unblock.