Current status

Batch 5 hygiene note, 2026-05-17: Active source of truth for the RingCentral parallel QA, RingSense linkage, and SMS Magic staging checkpoint. True staff-session rendered QA and the guarded RingSense association improvement remain real unresolved blockers. Do not deploy SMS Magic UI retirement until staff-session RingCentral QA passes. Indexed in the SAIL Knowledge Base Hygiene Hub - 2026-05-12.

Objective

Sam agreed that A, B, and C all made sense to run in parallel for the RingCentral/Litify/SMS Magic project.

The lanes were:

• A: rendered normal-user/browser QA for the live RingCentral tab;
• B: RingSense remaining unlinked Task analysis;
• C: check-only SMS Magic staff-facing UI retirement staging.

A. Rendered QA

Read-only QA completed as far as browser/auth allowed. No Salesforce records, metadata, settings, or packages were changed.

True normal-user rendered QA is still blocked. The browser path could not complete a true normal-user session, and the Salesforce Login As attempt hit an internal/incomplete setup path.

Admin-authenticated rendered QA on Matter a0LUV00000BBjTJ2A1 mostly passed:

• RingCentral tab visible;
• component renders;
• Communications Timeline visible;
• iframe loads from apps.ringcentral.com;
• no current CSP/console errors observed;
• iframe has allow="microphone";
• Call/Text/Open Dialer controls visible.

Warning observed: RingCentral widget reported the default RingCentral client id is deprecated.