Retire the visible Risk Radar terminology in the Litify attorney hub/team dashboard experience and preserve a durable memory that the term should not be used in future visible hub labels.
Updated user-facing labels, headings, descriptions, aria labels, dashboard titles, and template copy from Risk Radar to Needs Attention across the attorney hub source. Internal component/API names such as RiskRadarController, dashboard file names, and facet identifiers were intentionally left alone to avoid unnecessary Salesforce metadata risk.
Created a durable memory note at /Users/samaguiar/.codex/memories/extensions/ad_hoc/notes/2026-05-28T21-42-46-0400-retire-risk-radar.md so future agents know Risk Radar is retired visible language.
Deployed the label-only update to LITIFY_ORG using quick deploy from the validated package.
Committed and pushed source control on branch codex/attorney-hubs-all-from-mdt-2026-05-28.
Salesforce validation deploy ID: 0AfUV000001Xtd30AC. Result: succeeded, 50/50 components validated, 47/47 specified tests completed, 0 component errors, 0 test errors.
Live quick deploy ID: 0AfUV000001XtgH0AS. Result: succeeded, 50/50 components deployed, 0 component errors.
Live FlexiPage Tooling sweep checked 16 pages: attorney hubs for Abigail, Austin, Jimmy, Jon, Nick, Terry, Trent; team dashboards for Abigail, Austin, Jimmy, Jon, Nick, Payton, Terry, Trent; and SAIL_Team_Dashboard_Template. Result: no Risk Radar phrase found, Needs Attention found on all 16.
Live dashboard metadata retrieve to /tmp/litify-live-dashboard-risk-rename-2026-05-29 checked all eight team dashboard titles/descriptions. Result: Abigail, Austin, Jimmy, Jon, Nick, Payton, Terry, and Trent dashboard title/description lines all say Needs Attention.
Source sweep command against active hub classes, dashboards, flexipages, and LWCs found no remaining visible phrase match for Risk Radar|Risk radar|risk radar.
git diff --check and git diff --cached --check both passed.
Commit: 0df952fbb905415ce1c7a5c6e25aa625545e6196, message fix: rename risk radar labels.
This session is complete. A next agent can focus on broader rendered QA of the Needs Attention tabs and mobile workflows, especially because internal API names still contain RiskRadar by design. That is not a user-facing issue, but it is worth knowing so search results do not look surprising.
A useful follow-up would be to visually open a representative hub on mobile width, click the More tab menu, and confirm Needs Attention is discoverable, readable, and not buried in a way that hurts attorney or case-manager workflow. If deeper cleanup is considered later, rename internal metadata only with a full Salesforce impact plan because Apex classes, LWC imports, FlexiPage facets, and dashboard file identities could all be touched.
Reason for ending: requested terminology change has been deployed, verified, committed, pushed, and recorded.