Objective

Sam flagged that the visible Agent Query: A Resolution Cases 150+ Days card was in the wrong location and style. The goal was to remove that uncommon query pattern from the resource-card board and make the Agentforce section teach practical use cases instead.

Accomplished

• Removed Agent Query as a visible resource board type in attorneyHubNickTeamResources.
• Added grouped Agentforce use-case question tiles: daily case work, hub improvements, insurance knowledge, and draft prep.
• Updated Apex getResources to exclude active Agent Query records from the hub payload, so the existing live All Teams record remains available for rollback/history but no longer displays in Nick's hub.
• Removed legacy Agent Query seed cards from fallback resources.
• Normalized future Agent Query save attempts into Team Template so another awkward agent card is not recreated from the add-resource UI.
• Added regression tests proving seed cards do not include Agent Query and legacy saves normalize away from that type.
• Deployed to LITIFY_ORG.
• Pushed commit c23e3c9 Refine Nick Agentforce guidance cards to branch codex/nick-agentforce-hub-2026-05-29, PR #9.

QA Evidence

• Live Salesforce preflight: LITIFY_ORG connected as sam@kylawoffice.com.
• Live SOQL before fix found one active offending record: Agent Query: A Resolution Cases 150+ Days, Team All Teams.
• git diff --check: passed.
• Validation deploy 0AfUV000001Y3Cb0AK: succeeded, 3 components, 10 tests, 0 failures.
• Production deploy 0AfUV000001Y3ED0A0: succeeded, 3 components, 10 tests, 0 failures.
• Live anonymous Apex smoke after deploy: NICK_RESOURCE_COUNT=13, AGENT_QUERY_COUNT=0, 2 SOQL queries, 0 DML.

What Is Still Pending

• Agentforce publish remains blocked by the same external Salesforce authoring endpoint timeout seen earlier at https://test.api.salesforce.com/einstein/ai-agent/v1.1/authoring/agents. The metadata and hub actions are deployed, but the final Agentforce publish retry should run when that endpoint is responsive.