Inspect the current Salesforce/Litify source in /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata without editing files. Focus: attorneyHubNickTeamResources, related Apex, and Agentforce metadata.
Confirmed the dedicated Nick hub Agentforce surface lives inside the Team Resources tab of Attorney_Hub_Nick.flexipage-meta.xml, which embeds attorneyHubNickTeamResources with teamName=Nick.
Confirmed the LWC includes an Agentforce operating map, capability tiles, can-do and cannot-do lists, use-case questions, live test controls, and live output rendering for the read-only case-search action.
Confirmed the related Apex path: AttorneyHubNickTeamResourcesController.runAgentQuery wraps AttorneyHubAgentforceCaseSearchAction.searchCases. The action is read-only, scopes to open matters for the selected team via Hub_Eligible_Attorney__mdt, caps results, and returns matter links, stage, rating, damages, treatment age, last note context, case manager, and next action.
Confirmed Agentforce source exists at aiAuthoringBundles/Nick_Attorney_Hub_Agent/Nick_Attorney_Hub_Agent.agent. It already states live scope and limits, routes to matter search and report/dashboard advisor subagents, and includes strong example questions.
The UI already says what the agent can and cannot do. It does this in three places: LWC capability cards, the controller agentforceStatus payload, and the Nick agent authoring bundle.
The UI already has clear use-case questions. The clearest ones live in the AGENT_QUESTIONS constant and the Nick agent bundle's Strong example questions sections.
Main clarity gap: the Team Resources command strip still says natural-language caseload search is feasible once secured actions are wired, while the lower Agentforce section and controller say read-only case search is already connected. That stale summary copy could confuse users.
Source-only caution: the FlexiPage references attorneyHubNickNeedsAttention, but the local LWC folder present is attorneyHubNickRiskRadar. This may be a parallel-agent rename in progress or an incomplete source state. No changes were made.
For copy and UI clarity only: force-app/main/default/lwc/attorneyHubNickTeamResources/attorneyHubNickTeamResources.html, force-app/main/default/lwc/attorneyHubNickTeamResources/attorneyHubNickTeamResources.js, and possibly force-app/main/default/lwc/attorneyHubNickTeamResources/attorneyHubNickTeamResources.css if the capability tiles need clearer visual hierarchy.
For data-backed status text and seed resources: force-app/main/default/classes/AttorneyHubNickTeamResourcesController.cls and its test AttorneyHubNickTeamResourcesTest.cls.
For actual Agentforce instruction clarity: force-app/main/default/aiAuthoringBundles/Nick_Attorney_Hub_Agent/Nick_Attorney_Hub_Agent.agent.
Do not edit AttorneyHubAgentforceCaseSearchAction.cls or GenAI schema unless the action capability itself changes.
The requested source-only inspection is complete. No files were edited, no deployments were attempted, and no live-org verification was performed because this was explicitly a sidecar source inspection.