Superseded status note, 2026-06-01

This page is now historical. The Nick launch blocker described below was closed by Nick Attorney Hub Agentforce deployed and verified - 2026-06-01. Live cleanup verification also found Nick_Attorney_Hub_Agent Bot metadata in LITIFY_ORG. Treat older timeout, missing Bot, or unpublished wording below as stale context, not a current blocker.

Session objective

Continue equipping Nick's Attorney Hub Agent and related Agentforce surface, improve testability, and keep pushing toward deployable Agentforce readiness.

What shipped

• Validated Nick_Attorney_Hub_Agent with sf agent validate authoring-bundle --api-name Nick_Attorney_Hub_Agent --target-org LITIFY_ORG --json. Result: success true.
• Started simulated and live Agentforce preview sessions for Nick_Attorney_Hub_Agent.
• Live preview answered realistic prompts against Nick data for open matters, since-2024 archive search, report/dashboard advice, insurance knowledge, and document draft prep.
• Added scripts/run-nick-agentforce-qa.mjs, a repeatable QA runner that executes the five Apex smoke files and returns only pass/fail, summaries, and counts, avoiding raw matter-row dumps in normal QA logs.
• Committed and pushed e7a056e Add Nick Agentforce QA runner to branch codex/nick-agentforce-hub-2026-05-29.

QA evidence

• node --check scripts/run-nick-agentforce-qa.mjs: passed.
• git diff --check -- scripts/run-nick-agentforce-qa.mjs: passed.
• node scripts/run-nick-agentforce-qa.mjs --org LITIFY_ORG: passed.
• QA runner results included: open matter search found 5, archive search found 1 and 5 in its sample filters, report/dashboard advisor returned 2 and 3 items, insurance knowledge returned 5 Nick rows and 5 all-team missing coverage rows, document draft prep returned 3 rows.
• sf org list metadata --metadata-type Bot --target-org LITIFY_ORG --json still lists only Litify_Matter_Summary_Agent and Litify_Conflict_Check_Agent, so Nick Bot metadata is not created yet.

Current blocker

Publishing the validated authoring bundle with sf agent publish authoring-bundle --api-name Nick_Attorney_Hub_Agent --target-org LITIFY_ORG --skip-retrieve --json failed with ETIMEDOUT against https://test.api.salesforce.com/einstein/ai-agent/v1.1/authoring/agents. This appears to be the same external Agentforce authoring endpoint issue seen before, not an Agent Script validation failure.

Suggested next steps

A future agent can rerun the new QA script first, then retry sf agent publish authoring-bundle when Salesforce's Agentforce authoring endpoint is responding. If publish succeeds, inspect Bot metadata, then decide whether activation is appropriate based on user-facing readiness and permission assignments. Continue avoiding broad git staging because the worktree has many unrelated changes.